test: remove brittle CI configuration and script tests - #11185
Merged
Merged
Conversation
vicancy
force-pushed
the
codex/relax-ci-workflow-assertions
branch
from
September 24, 2026 23:48
9f6ab34 to
8609756
Compare
vicancy
changed the title
vicancy
force-pushed
the
codex/relax-ci-workflow-assertions
branch
from
September 24, 2026 23:55
8609756 to
8e3828f
Compare
vicancy
changed the title
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
1 participant
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.
Routine workflow edits, including the Action upgrade in #11182, fail compatibility tests that lock configuration and implementation details. Remove assertions about workflow/documentation text, command ordering, request counts, GitHub output delimiters, and tests that extract PowerShell statements by internal variable names or control-flow structure.
Retain report validation, archive/provenance, and CLI behavior tests. Log export and HTTP selection tests now use sample log paths instead of extracting script assignments. Actual package installation and distribution verification remain in CI.
Validation:
node --test test/compatibility/report.test.mjs— all 43 remaining tests passed.