Add JUnit output to the test runner - #11197
Conversation
|
this feels pretty intrusive for something used downstream, I expect it will be hard to maintain. Did you look at alternative ways to do this? |
The idea is to serialize test results into a standardized format and it is opt-in only. This can be use for CI statistics yes, but just generally for automation in CI or locally. Unfortunately, overriding the pytest flags like |
24463c5 to
85344da
Compare
|
@ThomasRaoux I tried re-writing this to be a simpler and less intrusive. Still remains opt-in only, but uses uuid in the file names to avoid outputs overwriting each other. |
This PR was authored with the help of Codex Sol 5.6
--junit-dirsupport topython -m triton._test_runner suiteMotivation
Downstream CI systems need machine-readable test results from Triton's
source-owned test runner. Supplying JUnit paths inside the runner keeps test
selection, parallelism, and report partitioning under the same ownership and
prevents concurrent pytest subprocesses from overwriting one another.
JUnit output remains opt-in. Existing invocations behave unchanged unless
--junit-dirorTRITON_TEST_JUNIT_DIRis provided.Testing
python -m pytest -q python/test/unit/runtime/test_driver.pypre-commit run --from-ref github/main --to-ref HEADReferences: