[ci] Update exist-xqts-runner to 2.0.0-RC4 - #6651
Merged
Merged
Conversation
RC4 includes the fix for eXist-db/exist-xqts-runner#74: the runner now serializes each test set's JUnit output exactly once, after all of its test cases have completed. RC3 could rewrite result files mid-run and record a nondeterministic subset of test cases (~40 tests of variance between identical runs), which showed up as noise in the XQTS comparison and triggered its recording-drift warning. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01XqsCRdPehXB5zK1xcNFKEo
Contributor
📊 XQTS result comparisonComparison of this run against Warning Runner JAR build SHA or sha256 differs between the previous and current XQTS runs. Test deltas may include runner-side effects unrelated to this PR. See #6326. Warning 519 test cases were recorded in only one of the two runs (0 only in the previous run, 519 only in the current run). The runner's JUnit output is not fully deterministic (see eXist-db/exist-xqts-runner#74), so totals and per-category deltas include recording noise; the newly passing/failing lists count only tests recorded in both runs.
Relative to 🔴 Newly failing tests (1)
⚪ Recorded only in this run (519)
Runtime: 329.2s (-99.27s vs |
duncdrum
approved these changes
Aug 19, 2026
reinhapa
approved these changes
Aug 19, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description:
Bumps the
exist-xqts-runner_2.13dependency inexist-xqts/pom.xmlfrom 2.0.0-RC3 to 2.0.0-RC4.RC4 includes the fix for the runner's nondeterministic JUnit output: RC3 could serialize a test set's result file while cases were still pending and rewrite it repeatedly mid-run, so each run recorded a slightly different subset of test cases (~40 tests of variance between runs of the same commit). That variance showed up as noise in the XQTS comparison step and triggered its recording-drift warning. With RC4, each test set is serialized exactly once after all of its cases complete — two full local runs against the same commit produced identical recorded test sets (0 presence diffs across 31,752 cases).
RC4 is published to the eXist-db GitHub Packages Maven repository, which CI already resolves via the
maven-github-settingsaction and thegithub-xqts-runnerrepository declared inexist-parent.Reference:
Type of tests:
No code changes — dependency version bump only. Verified locally that 2.0.0-RC4 resolves from GitHub Packages; the XQTS CI workflow on this PR exercises the new runner end-to-end.
🤖 Generated with Claude Code
https://claude.ai/code/session_01XqsCRdPehXB5zK1xcNFKEo