rusackas opened a new pull request, #45757:
URL: https://github.com/apache/superset/pull/45757

   ### SUMMARY
   The `Python unit tests` step already runs on pytest-xdist, but the two 
"Python 100% coverage" gates that follow it re-run `tests/unit_tests/sql` and 
`tests/unit_tests/semantic_layers` serially. On the last few master runs that 
step took about 213 seconds on a runner whose other three cores sat idle.
   
   This gives both gates the same `-n auto --dist loadfile` settings as the 
main step. pytest-cov combines the per-worker coverage data before 
`--cov-fail-under=100` is evaluated, so the gate semantics are unchanged: each 
subtree still has to be fully covered by its own tests.
   
   Runner minutes saved per unit-test run should be roughly two and a half 
minutes; I'll post the measured step time once CI has run it.
   
   ### BEFORE/AFTER SCREENSHOTS OR ANIMATED GIF
   N/A
   
   ### TESTING INSTRUCTIONS
   CI: the `Python-Unit` workflow's "Python 100% coverage unit tests" step 
still passes, faster.
   
   ### ADDITIONAL INFORMATION
   - [ ] Has associated issue:
   - [ ] Required feature flags:
   - [ ] Changes UI
   - [ ] Includes DB Migration (follow approval process in 
[SIP-59](https://github.com/apache/superset/issues/13351))
     - [ ] Migration is atomic, supports rollback & is backwards-compatible
     - [ ] Confirm DB migration upgrade and downgrade tested
     - [ ] Runtime estimates and downtime expectations provided
   - [ ] Introduces new feature or API
   - [ ] Removes existing feature or API
   
   🤖 Generated with [Claude Code](https://claude.com/claude-code)
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to