[PR] Publish ADO test results from the test step instead of per-project tasks [lucenenet]

["paulirwin (via GitHub)" <gi...@apache.org>]

paulirwin opened a new pull request, #1446:
URL: https://github.com/apache/lucenenet/pull/1446

   - [X] You've read the [Contributor Guide](https://github.com/apache/lucenenet/blob/master/CONTRIBUTING.md) and [Code of Conduct](https://www.apache.org/foundation/policies/conduct.html).
   - [ ] You've included unit or integration tests for your change, where applicable.
   - [ ] You've included inline docs for your change, where applicable.
   - [ ] There's an open issue for the PR that you are making. If you'd like to propose a change, please [open an issue](https://github.com/apache/lucenenet/issues/new/choose) to discuss the change or find an existing issue.
   
   Publish ADO test results from the test step instead of per-project tasks
   
   ## Description
   
   Each Azure DevOps test job ran 123 tasks after the tests finished: for each of 41 test project slots, two PowerShell steps to parse TestResults.trx and dotnet-test-error.log, and one PublishTestResults@2 task. Almost all of that time is task startup (about 5 minutes per Windows job, 4 on macOS), not work: all 41 TRX files total 14 MB.
   
   The dotnet test step now parses each project's results itself, using the same XmlReader/stderr logic and accumulating the same variables the final "fail the job" step reads (TotalFailures, HostCrashed, CrashedRuns, StdOutFailure, StdOutFailureRuns, StdErrFailure, StdErrFailureRuns). It publishes each TRX as its own test run, with the same per-project title, by emitting the agent's "results.publish" logging command, which is the same mechanism PublishTestResults@2 uses under the hood. The agent runs the uploads asynchronously and waits for them at the end of the step.
   
   By default (`publishTestResultsInline: 'true'`) each project is handled as soon as its background job finishes, so publishing overlaps with the projects still running. Set it to 'false' to handle everything after the last project.
   
   The per-project templates publish-test-results.yml and publish-test-results-for-test-projects.yml are removed. New test projects no longer need a block added there; result directories are enumerated.
   
   Verified in Azure DevOps with two runs, saving over 10 minutes per run (61min previous recent best time, 50-52min now).
   
   AI: created with Claude Code (Fable 5 and 5.1)


-- 
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: dev-unsubscribe@lucenenet.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org

Re: [PR] Publish ADO test results from the test step instead of per-project tasks [lucenenet]

["paulirwin (via GitHub)" <gi...@apache.org>]

paulirwin merged PR #1446:
URL: https://github.com/apache/lucenenet/pull/1446


-- 
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: dev-unsubscribe@lucenenet.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org