Repository navigation
Run the conformance suite at release-v5.3.4 in CI - #361
Merged
cicnavi merged 4 commits intoNov 4, 2026
Merged
Conversation
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## master #361 +/- ##
============================================
+ Coverage 53.99% 54.01% +0.01%
Complexity 1512 1512
============================================
Files 141 141
Lines 6078 6080 +2
============================================
+ Hits 3282 3284 +2
Misses 2796 2796 ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
ioigoume
force-pushed
the
ci/use-latest-conformance-suite
branch
from
October 8, 2026 16:30
f059093 to
1f9ef82
Compare
add failure diagnostic logging
…for back-channel logout client endpoints in conformance testing fixtures.
ioigoume
force-pushed
the
ci/use-latest-conformance-suite
branch
from
October 8, 2026 16:54
cc85c32 to
a669d3d
Compare
Following the suite's latest release at run time lets a new release turn CI red with no change here, and makes the same commit pass or fail depending on when it runs. The suite had eight releases between August and October 2026. Pin it instead, as wip-version-7 does, so moving to a new release is a deliberate commit. This removes the step resolving the latest release and the jq install. The runner image already has jq. The failure dump now uses the step from wip-version-7, which shows the last 2000 lines of the OP's log rather than 100 lines per container. The /api/log part is gone: it printed nothing in a failed run. The local instructions in docs/5-oidc-conformance.md name the same release. Assisted-by: Claude Code (claude-opus-5-5, implementation)
Collaborator
|
Thanks for this! I pushed a commit on top: the suite is now pinned at release-v5.3.4 instead of following latest, so a new suite release can't turn CI red with no change on our side. The version moves in deliberate commits, as on wip-version-7. Your host rename stays as it was, and the failure dump now uses the same OP log step as wip-version-7. |
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.
No description provided.