-
Notifications
You must be signed in to change notification settings - Fork 12.9k
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
Revert #46694 (Temporarily use the old Travis image) #46924
Conversation
Travis is green. Though maybe we could wait a few more days before merging, to see whether those two commands will be folded into the official image. |
This seems good, but I looked up the address suggested since I know very little about IPv6. http://silmor.de/ipv6.address.php and https://en.wikipedia.org/wiki/IPv6_address suggest Instead, can we use the link-local address? I.e. r=me once that's done. |
(I'd merge rather than waiting since I suspect they're not going to make ad-hoc changes like this when they'll be shorter-staffed due to xmas) |
5a3696f
to
0ea0218
Compare
@bors r=aidanhs rollup |
📌 Commit 0ea0218 has been approved by |
@bors r- Needs to limit those docker commands to Linux. |
0ea0218
to
8d76e28
Compare
@bors r=aidanhs |
📌 Commit 8d76e28 has been approved by |
@bors rollup- This PR caused Details: https://travis-ci.org/rust-lang/rust/builds/320656619 |
Revert #46694 (Temporarily use the old Travis image) This PR reverts #46694, and applies the solution recommended in travis-ci/travis-ci#8891 (comment). r? @aidanhs
☀️ Test successful - status-appveyor, status-travis |
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.
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
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 PR reverts #46694, and applies the solution recommended in travis-ci/travis-ci#8891 (comment).
r? @aidanhs