-
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
mk: actually run valgrind on x86_64-apple-darwin #30365
Conversation
@bors: r+ 952348e39e18aee1f98cccc6ebd596911c0d822d Hey if it gets past the bots that sounds good to me. Thanks! |
⌛ Testing commit 952348e with merge e0836e9... |
💔 Test failed - auto-mac-32-opt |
Needs a retry |
@bors retry |
Can I get another retry? bors seems to have dropped this. |
@bors: retry |
@bors force retry (Is force still a thing?) update: ((oh wait, it is in the queue, maybe that was unnecessary...)) |
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. |
952348e
to
b9689f4
Compare
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? |
It's sketchy, but it works (I think). We do have special OS X suppressions,
|
Unfortunately it's actually pretty nontrivial to upgrade valgrind right now on the OSX bots, can this land without doing that? |
I suppose if we disabled |
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...) |
b9689f4
to
3f054b3
Compare
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! |
@bors: r+ 3f054b3ad53e7c97423f8002de56b9464f7051ed |
Updated to suppress this one. On Sun, Dec 20, 2015 at 7:40 AM, Felix S Klock II notifications@github.com
|
@bors r+ c1e12e8 |
🙀 |
@bors r+ c1e12e0 |
⌛ Testing commit c1e12e0 with merge 7d7856b... |
⛄ The build was interrupted to prioritize another pull request. |
⌛ Testing commit c1e12e0 with merge 8367140... |
💔 Test failed - auto-mac-64-nopt-t |
c1e12e0
to
a3d81c6
Compare
Tidy error. Fixed. On Fri, Dec 25, 2015 at 8:54 AM, bors notifications@github.com wrote:
|
ping @pnkfelix |
⌛ Testing commit a3d81c6 with merge 302010d... |
💔 Test failed - auto-linux-64-opt |
@bors retry |
⌛ Testing commit a3d81c6 with merge 09f7c10... |
💔 Test failed - auto-linux-64-opt |
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
darwin
is reallyapple-darwin
, the valgrind-rpass tests were not actually being run with valgrind on mac before. Also, theHOST
check was completely wrong.r? @alexcrichton