Uh oh!
There was an error while loading. Please reload this page.
mk: actually run valgrind on x86_64-apple-darwin - #30365
Conversation
alexcrichton
commented
Dec 13, 2015
@bors: r+ 952348e39e18aee1f98cccc6ebd596911c0d822d Hey if it gets past the bots that sounds good to me. Thanks! |
bors
commented
Dec 14, 2015
⌛ Testing commit 952348e with merge e0836e9... |
bors
commented
Dec 14, 2015
💔 Test failed - auto-mac-32-opt |
tamird
commented
Dec 14, 2015
Needs a retry |
pnkfelix
commented
Dec 14, 2015
@bors retry |
tamird
commented
Dec 16, 2015
Can I get another retry? bors seems to have dropped this. |
alexcrichton
commented
Dec 16, 2015
@bors: retry |
pnkfelix
commented
Dec 17, 2015
@bors force retry (Is force still a thing?) update: ((oh wait, it is in the queue, maybe that was unnecessary...)) |
tamird
commented
Dec 18, 2015
One of the failures is https://bugs.kde.org/show_bug.cgi?id=201216; can we get valgrind updated on the mac bots? This was fixed in 3.11 (see http://valgrind.org/docs/manual/dist.news.html). I've updated for the other failures. |
alexcrichton
commented
Dec 18, 2015
I'm actually not sure the mac bots will be guaranteed to actually run newer versions of valgrind, they're all running older OSX versions (e.g. 10.7 or 10.8). I've always thought that valgrind was a little sketchy on OSX? |
tamird
commented
Dec 18, 2015
It's sketchy, but it works (I think). We do have special OS X suppressions,
|
alexcrichton
commented
Dec 18, 2015
Unfortunately it's actually pretty nontrivial to upgrade valgrind right now on the OSX bots, can this land without doing that? |
tamird
commented
Dec 18, 2015
I suppose if we disabled |
alexcrichton
commented
Dec 18, 2015
Yeah I think that'd be fine. Hopefully when we move to macstadium it should be easy to upgrade to a new valgrind (and have macs that are consistently online...) |
tamird
commented
Dec 19, 2015
OK, done! I'll be offline for the next week or so; I'll circle back and address comments if this doesn't land by then. Happy holidays! |
alexcrichton
commented
Dec 19, 2015
@bors: r+ 3f054b3ad53e7c97423f8002de56b9464f7051ed |
tamird
commented
Dec 24, 2015
Updated to suppress this one. On Sun, Dec 20, 2015 at 7:40 AM, Felix S Klock II notifications@github.com
|
pnkfelix
commented
Dec 24, 2015
@bors r+ c1e12e8 |
bors
commented
Dec 24, 2015
🙀 |
pnkfelix
commented
Dec 24, 2015
@bors r+ c1e12e0 |
bors
commented
Dec 25, 2015
⌛ Testing commit c1e12e0 with merge 7d7856b... |
bors
commented
Dec 25, 2015
⛄ The build was interrupted to prioritize another pull request. |
bors
commented
Dec 25, 2015
⌛ Testing commit c1e12e0 with merge 8367140... |
bors
commented
Dec 25, 2015
💔 Test failed - auto-mac-64-nopt-t |
tamird
commented
Dec 25, 2015
Tidy error. Fixed. On Fri, Dec 25, 2015 at 8:54 AM, bors notifications@github.com wrote:
|
tamird
commented
Dec 28, 2015
ping @pnkfelix |
pnkfelix
commented
Dec 29, 2015
bors
commented
Dec 30, 2015
⌛ Testing commit a3d81c6 with merge 302010d... |
bors
commented
Dec 30, 2015
💔 Test failed - auto-linux-64-opt |
pnkfelix
commented
Dec 30, 2015
@bors retry |
bors
commented
Dec 30, 2015
⌛ Testing commit a3d81c6 with merge 09f7c10... |
bors
commented
Dec 30, 2015
💔 Test failed - auto-linux-64-opt |
tamird
commented
Dec 30, 2015
Needs another retry :( |
Since `darwin` is really `apple-darwin`, the valgrind-rpass tests were not actually being run with valgrind on mac before. Also, the `HOST` check was completely wrong. r? @alexcrichton
Since
darwinis reallyapple-darwin, the valgrind-rpass tests were not actually being run with valgrind on mac before. Also, theHOSTcheck was completely wrong.r? @alexcrichton