Follow up to #46924, fix massive spurious failure when starting docker #47000
Conversation
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.
kennytm
added
the
S-waiting-on-author
|
@bors try |
|
⌛ Trying commit 472a3c1 with merge 5ddec7adfa1883fd5f1db3984809cefb6cc2932b... |
|
@bors r- try- retry |
kennytm
changed the title
|
The docker has successfully been built on the @bors r+ |
|
📌 Commit 472a3c1 has been approved by |
|
⌛ Testing commit 472a3c1 with merge a555a3f87cad81e0aef4f08f9096bc3601c29e26... |
|
@bors r- retry |
kennytm
added
S-waiting-on-review
|
@bors r+ p=10 |
|
📌 Commit 472a3c1 has been approved by |
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
|
💔 Test failed - status-appveyor |
|
@bors retry 3 hour timeout. |
|
⌛ Testing commit 472a3c1 with merge d21e176607e046614b1f2e661a0a98c8139ce87f... |
|
💔 Test failed - status-travis |
|
@bors retry sccache segfault?! |
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
|
☀️ Test successful - status-appveyor, status-travis |
|
Reported sccache segfault, though I don't know if it was sccache's fault or if it was 'just' some failure cascading (mozilla/sccache#210) |
|
FWIW, we've had the lookForDIEsToKeep llvm-dsymutil crashes on Firefox. See https://bugzilla.mozilla.org/show_bug.cgi?id=1381043 and https://bugs.llvm.org/show_bug.cgi?id=33873 . It's fixed in llvm upstream, but the root cause in rustc probably still exists (it was obviously a llvm bug that it led to a crash, but the root cause was that rustc produces bad DWARF data). |
It seems using
fe80::/64causesdocker startto fail with "Address already in use". Try to change to a unique local address range instead.fe80::/64is a link-local address (similar to169.254.0.0/16in IPv4). Let's try to use a random "private network" address to see whether that fixes things.cc #47002
r? @aidanhs