Uh oh!
There was an error while loading. Please reload this page.
appveyor: Upgrade to gcc for mingw 6.3.0 - #41420
Conversation
rust-highfive
commented
Apr 20, 2017
r? @brson (rust_highfive has picked a reviewer for you, use r? to override) |
shepmaster
commented
Apr 21, 2017
Thanks for the PR, @alexcrichton! We'll rustle up a review from @brson for you! |
TimNN
commented
Apr 22, 2017
@alexcrichton: Can you upload the respective posix threads versions as well? |
alexcrichton
commented
Apr 24, 2017
@TimNN already done :) I actually thought we had already upgraded and when I got around to actually making a PR I noticed I didn't have to... We should have win32/pthread 6.2.0/6.3.0 all uploaded |
bors
commented
Apr 25, 2017
☔ The latest upstream changes (presumably #40123) made this pull request unmergeable. Please resolve the merge conflicts. |
alexcrichton
commented
Apr 25, 2017
Updated |
petrochenkov
commented
Apr 25, 2017
@bors r+ |
bors
commented
Apr 25, 2017
📌 Commit 3b33913 has been approved by |
alexcrichton
commented
Apr 25, 2017
@bors: p=1 (hopefully fixing a lot of spurious failures with this) |
…enkov appveyor: Upgrade to gcc for mingw 6.3.0 This commit sort of brings back rust-lang#40777 by upgrading back to 6.3.0. While investigating rust-lang#40546 it was discovered that 6.3.0 appears to not spurious fail in the same way that 6.2.0 does (which we're currently using). The workaround for rust-lang#40184 contained in rust-lang#40777 did not work so this commit also contains a different workaround for the gdb issue. We will not download the 6.2.0 version of gdb and use that instead of the default version that comes with 6.3.0. I'm going to optimistically say... Closesrust-lang#40546
bors
commented
Apr 25, 2017
bors
commented
Apr 25, 2017
💔 Test failed - status-appveyor |
Mark-Simulacrum
commented
Apr 25, 2017
Non-spurious failure. @alexcrichton said on IRC that they probably forgot to upload artifacts. |
alexcrichton
commented
Apr 25, 2017
@bors: r=petrochenkov |
bors
commented
Apr 25, 2017
📌 Commit d7d2e5c has been approved by |
bors
commented
Apr 25, 2017
⌛ Testing commit d7d2e5c with merge 690233d... |
bors
commented
Apr 25, 2017
💔 Test failed - status-appveyor |
alexcrichton
commented
Apr 26, 2017
@bors: r=petrochenkov |
bors
commented
Apr 26, 2017
📌 Commit e239e47 has been approved by |
bors
commented
Apr 26, 2017
⌛ Testing commit e239e47 with merge e28a4f6... |
bors
commented
Apr 26, 2017
💔 Test failed - status-appveyor |
Mark-Simulacrum
commented
Apr 26, 2017
Legitimate failure: |
This commit sort of brings back rust-lang#40777 by upgrading back to 6.3.0. While investigating rust-lang#40546 it was discovered that 6.3.0 appears to not spurious fail in the same way that 6.2.0 does (which we're currently using). The workaround for rust-lang#40184 contained in rust-lang#40777 did not work so this commit also contains a different workaround for the gdb issue. We will not download the 6.2.0 version of gdb and use that instead of the default version that comes with 6.3.0. I'm going to optimistically say... Closesrust-lang#40546
alexcrichton
commented
Apr 26, 2017
@bors: r=petrochenkov I sure wish there was like an |
bors
commented
Apr 26, 2017
📌 Commit d1db74b has been approved by |
bors
commented
Apr 26, 2017
appveyor: Upgrade to gcc for mingw 6.3.0 This commit sort of brings back #40777 by upgrading back to 6.3.0. While investigating #40546 it was discovered that 6.3.0 appears to not spurious fail in the same way that 6.2.0 does (which we're currently using). The workaround for #40184 contained in #40777 did not work so this commit also contains a different workaround for the gdb issue. We will not download the 6.2.0 version of gdb and use that instead of the default version that comes with 6.3.0. I'm going to optimistically say... Closes#40546
alexcrichton
commented
Apr 26, 2017
Homu's having trouble, but tests passed, so merging |
This commit sort of brings back #40777 by upgrading back to 6.3.0. While
investigating #40546 it was discovered that 6.3.0 appears to not spurious
fail in the same way that 6.2.0 does (which we're currently using). The
workaround for #40184 contained in #40777 did not work so this commit also
contains a different workaround for the gdb issue. We will not download the
6.2.0 version of gdb and use that instead of the default version that comes with
6.3.0.
I'm going to optimistically say...
Closes#40546