-
Notifications
You must be signed in to change notification settings - Fork 12.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Tracking issues for spurious failures related to IPv6 problems in Travis CI's new 2017-Q4 image #47002
Labels
A-spurious
Area: Spurious failures in builds (spuriously == for no apparent reason)
C-tracking-issue
Category: A tracking issue for an RFC or an unstable feature.
T-infra
Relevant to the infrastructure team, which will review and decide on the PR/issue.
Comments
kennytm
added
A-spurious
Area: Spurious failures in builds (spuriously == for no apparent reason)
C-tracking-issue
Category: A tracking issue for an RFC or an unstable feature.
T-infra
Relevant to the infrastructure team, which will review and decide on the PR/issue.
labels
Dec 25, 2017
This was referenced Dec 25, 2017
bors
added a commit
that referenced
this issue
Dec 25, 2017
Follow up to #46924, fix massive spurious failure when starting docker It seems using `fe80::/64` causes `docker start` to fail with "Address already in use". Try to change to a unique local address range instead. `fe80::/64` is a link-local address (similar to `169.254.0.0/16` in IPv4). Let's try to use a random "private network" address to see whether that fixes things. cc #47002 r? @aidanhs
This was referenced Dec 25, 2017
bors
added a commit
that referenced
this issue
Dec 26, 2017
Follow up to #46924, fix massive spurious failure when starting docker It seems using `fe80::/64` causes `docker start` to fail with "Address already in use". Try to change to a unique local address range instead. `fe80::/64` is a link-local address (similar to `169.254.0.0/16` in IPv4). Let's try to use a random "private network" address to see whether that fixes things. cc #47002 r? @aidanhs
Since we are not seeing any more spurious errors related to this image for over a month, I consider the image is now stable and am closing this issue. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
A-spurious
Area: Spurious failures in builds (spuriously == for no apparent reason)
C-tracking-issue
Category: A tracking issue for an RFC or an unstable feature.
T-infra
Relevant to the infrastructure team, which will review and decide on the PR/issue.
Upstream issue: travis-ci/travis-ci#8891.
1.
Network tests related to IPv6 are failingError first happens in #46692. Fixed in #44694 by using the older Travis image instead.
2.
Docker failed to start due to "Address already in use"The old image is reverted in #46924. It was still going well for ~5.5 hours (2 more PRs) after the PR is merged, but when bors try #46941, the jobs all immediately fail with
The failure is extremely quick and rapidly burnt out the entire tree. This has been fixed by #47000.
The text was updated successfully, but these errors were encountered: