Daniel Hiltgen 72ff5b9d8c log: warn if user overrides detected (#13088) ... Many failed GPU discovery issues recently can be traced to incorrect override settings. This extra logging should help quickly spot these and guide users to try unsetting them first.		2025-11-14 14:36:28 -08:00
..
cpu_linux.go	Use runners for GPU discovery (#12090)	2025-10-01 15:12:32 -07:00
cpu_linux_test.go	DRY out the runner lifecycle code (#12540)	2025-10-23 11:20:02 -07:00
cpu_windows.go	win: revert CPU discovery logic to 0.12.3 (#12969)	2025-11-05 10:32:38 -08:00
cpu_windows_test.go	Use runners for GPU discovery (#12090)	2025-10-01 15:12:32 -07:00
gpu.go	log: instrument CPU discovery timing (#12960)	2025-11-04 16:23:37 -08:00
gpu_darwin.go	Use runners for GPU discovery (#12090)	2025-10-01 15:12:32 -07:00
gpu_info_darwin.h	Rename gpu package discover (#7143)	2024-10-16 17:45:00 -07:00
gpu_info_darwin.m	Rename gpu package discover (#7143)	2024-10-16 17:45:00 -07:00
runner.go	log: warn if user overrides detected (#13088)	2025-11-14 14:36:28 -08:00
runner_test.go	app: add code for macOS and Windows apps under 'app' (#12933)	2025-11-04 11:40:17 -08:00
types.go	discovery: only retry AMD GPUs (#12894)	2025-11-04 15:33:46 -08:00