[zingo]

Use eight pytest workers to reduce the sequential test runtime. Report the 20 slowest test phases to help identify bottlenecks.

Compared with a main run from earlier the same day:
Windows job	Main:       sequential	      PR: 8 workers	    Improvement
Debug Python tests	      60m 45s	        14m 52s	        4.1× faster
Editable Python tests	  60m 04s	        14m 33s	        4.1× faster
Entire Debug job	   1h 51m	         1h 02m	            49 minutes saved
Entire editable job    1h 51m	         1h 03m	            49 minutes saved

Both versions reported 2,348 passed, 104 skipped and the same single failure, so the improvement isn’t from dropping tests. Native build times were similar.

Authored with assistance from OpenAI Codex.

cc @digantdesai @freddan80 @per @oscarandersson8218 @mansnils @Sebastian-Larsson @robell @rascani

[pytorch-bot]

🔗 Helpful Links

🧪 See artifacts and rendered test results at hud.pytorch.org/pr/pytorch/executorch/24895

• 📄 Preview Python docs built from this PR

Note: Links to docs will display an error until the docs builds have been completed.

❌ 4 New Failures

As of commit 7b062d7 with merge base b3b565b ():

NEW FAILURES - The following jobs have failed:

• Apple / build-benchmark-app / macos-job (gh)
  RuntimeError: Command bash /Users/runner/work/_temp/exec_script failed with exit code 141
• Apple / build-demo-ios / macos-job (gh)
  RuntimeError: Command bash /Users/runner/work/_temp/exec_script failed with exit code 141
• Apple / build-frameworks-ios / macos-job (gh)
  RuntimeError: Command bash /Users/runner/work/_temp/exec_script failed with exit code 141
• trunk / test-coreml-delegate / macos-job (gh)
  RuntimeError: Command bash /Users/runner/work/_temp/exec_script failed with exit code 141

This comment was automatically generated by Dr. CI and updates every 15 minutes.

[zingo]

@digantdesai or @rascani here is small CI speedup that might be nice to get in.