Repository navigation
JCU: CI: bump cypress-io/github-action to v7.4.4 (fixes 'Socket closed before the connection was established') - #1658
Merged
Conversation
Backport of #1656 (dtq-dev). v7.1.9 still bundles got@11, which on the runner's Node >= 24.20 turns a refused connection during wait-on into a fatal 'Socket closed before the connection was established' instead of retrying (cypress-io/github-action#1873). Every scheduled run of customer/jcu currently fails this way before any Cypress test starts. v7.4.4 migrated to got@16; the action inputs we use are unchanged.
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.
Change set
Bumps
cypress-io/github-actionfrom@v7.1.9to@v7.4.4in.github/workflows/build.yml. One line, no other changes.Backport
dtq-dev, merged 2026-10-23), which bumped@v6→@v7.4.4. customer/jcu was already on@v7.1.9, so the hunk differs but the target version is the same.browser,start,wait-onandwait-on-timeoutexist unchanged in v7.4.4'saction.yml. The action runs on the runner's bundled Node, so the Node 20/22 matrix,setup-nodeand the Cypress version frompackage.jsonare not affected.Run e2e tests (integration tests)step must get pastwait-onand actually start Cypress. Because the bug is intermittent, one green run proves v7.4.4 works with our inputs, not that the flake is gone; a few scheduled runs on customer/jcu after merge will show that.Problem
Every one of the last 10 scheduled Build runs on
customer/jcufails inRun e2e tests (integration tests)about a second after it starts, before any Cypress test runs:#1657 (
tests (20.x)andtests (22.x)) fails the same way for the same reason.Cause
Upstream bug cypress-io/github-action#1873: the action's
wait-onusesgot@11, and on Node ≥ 24.20 (the runner's bundled Node, v24.21.0 on runner 2.338.0) a refused connection while SSR is still starting is raised as a fatal error instead of being retried. Fixed in v7.4.4 ("migrate from got@11 to got@16"). See #1656 for the full analysis.Test evidence
No local test applies to a workflow file. Evidence is the CI run of this PR (see Manual test scenario).