-
-
Notifications
You must be signed in to change notification settings - Fork 37.1k
Alpine 3.8 cluster failures #22308
Copy link
Copy link
Closed
Labels
buildIssues and PRs related to Node.js builds or CI infrastructure.Issues and PRs related to Node.js builds or CI infrastructure.clusterIssues and PRs related to the cluster subsystem.Issues and PRs related to the cluster subsystem.flaky-testIssues and PRs involving tests that fail intermittently in CI.Issues and PRs involving tests that fail intermittently in CI.
Description
Activity
Metadata
Metadata
Assignees
Labels
buildIssues and PRs related to Node.js builds or CI infrastructure.Issues and PRs related to Node.js builds or CI infrastructure.clusterIssues and PRs related to the cluster subsystem.Issues and PRs related to the cluster subsystem.flaky-testIssues and PRs involving tests that fail intermittently in CI.Issues and PRs involving tests that fail intermittently in CI.
I just added Alpine 3.8 to CI and removed 3.6 in the process, shifting
alpine-last-latest-x64to Alpine 3.7 and givingalpine-latest-x64to Alpine 3.8. It tested well on my local machine across our major branches, but now it's enabled in CI we're getting consistent errors with on all test runs:What should we do with this? Do I remove it from CI for now or can someone spend some time investigating?
The Dockerfile is here minus the template strings which you can easily stub out to set this up locally if you want to give that a go. I'm not sure what the difference is with my local machine but perhaps I wasn't testing it on the latest
masterand there's something new or perhaps there's a Docker differential.