Skip to content

fix(kms): unsupported cases must not fail a plain lane run - #121

Merged
majinghe merged 1 commit into
mainfrom
fix/kms-unsupported-not-lane-failure
Oct 31, 2026
Merged

majinghe merged 1 commit into
mainfrom
fix/kms-unsupported-not-lane-failure

Conversation

@majinghe

Copy link
Copy Markdown
Collaborator

Chain 40796474356: every kms topology printed PASS=42/43 FAIL=0 UNSUPPORTED=6/7 and the driver still exited 1, invalidating the lane.

#113's validation migration added

if [ "${UNSUPPORTED}" -gt 0 ] || [ "${cleanup_status}" != PASS ]; then overall_fail=1; fi

so the 6-7 environment-gated skips per topology (rc-restart exit-7 gating and friends — the lane's long-standing shape, 39 aggregated UNSUPPORTED in every green historical run) flipped the driver to failure.

Keep teardown failures fatal in every mode; treat UNSUPPORTED as incomplete only when actually running as a validation case (VALIDATION_CASE set), which is where #113's strictness belongs.

#113's validation migration made any UNSUPPORTED topology result set
overall_fail, so every kms topology exited 1 despite PASS=42/43 FAIL=0
(6-7 rc-restart-gated skips per topology are the expected lane shape).
Keep teardown failures fatal everywhere; treat UNSUPPORTED as
incomplete only in validation mode.
@majinghe
majinghe merged commit c940a3e into main Oct 31, 2026
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant