Skip to content
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

Merged
merged 2 commits into from
Dec 31, 2015

Conversation

tamird
Copy link
Contributor

@tamird tamird commented Dec 13, 2015

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

@alexcrichton
Copy link
Member

@bors: r+ 952348e39e18aee1f98cccc6ebd596911c0d822d

Hey if it gets past the bots that sounds good to me. Thanks!

@bors
Copy link
Contributor

bors commented Dec 14, 2015

⌛ Testing commit 952348e with merge e0836e9...

@bors
Copy link
Contributor

bors commented Dec 14, 2015

💔 Test failed - auto-mac-32-opt

@tamird
Copy link
Contributor Author

tamird commented Dec 14, 2015

Needs a retry

@pnkfelix
Copy link
Member

@bors retry

@tamird
Copy link
Contributor Author

tamird commented Dec 16, 2015

Can I get another retry? bors seems to have dropped this.

@alexcrichton
Copy link
Member

@bors: retry

@pnkfelix
Copy link
Member

@bors force retry

(Is force still a thing?)

update: ((oh wait, it is in the queue, maybe that was unnecessary...))

@Manishearth
Copy link
Member

@tamird
Copy link
Contributor Author

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.

bors added a commit that referenced this pull request Dec 18, 2015
@alexcrichton
Copy link
Member

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
Copy link
Contributor Author

tamird commented Dec 18, 2015

It's sketchy, but it works (I think). We do have special OS X suppressions,
but otherwise things should be workable with 3.11.
On Dec 18, 2015 12:23, "Alex Crichton" notifications@github.com wrote:

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?


Reply to this email directly or view it on GitHub
#30365 (comment).

@alexcrichton
Copy link
Member

Unfortunately it's actually pretty nontrivial to upgrade valgrind right now on the OSX bots, can this land without doing that?

@tamird
Copy link
Contributor Author

tamird commented Dec 18, 2015

I suppose if we disabled run-pass-valgrind/exit-flushes.rs on OS X, then we could land this. Does that sound worth it?

@alexcrichton
Copy link
Member

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
Copy link
Contributor Author

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
Copy link
Member

@bors: r+ 3f054b3ad53e7c97423f8002de56b9464f7051ed

@tamird
Copy link
Contributor Author

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
wrote:

Error message looks legit:

failures:

---- [run-pass-valgrind] run-pass-valgrind/osx-frameworks.rs stdout ----

error: test run failed!
status: exit code: 100
command: /usr/local/bin/valgrind --error-exitcode=100 --fair-sched=try --quiet --soname-synonyms=somalloc=NONE --suppressions=/Users/rustbuild/src/rust-buildbot/slave/auto-mac-64-nopt-t/build/src/etc/x86.supp --suppressions=/Users/rustbuild/src/rust-buildbot/slave/auto-mac-64-nopt-t/build/src/etc/apple-darwin.supp --tool=memcheck --leak-check=full x86_64-apple-darwin/test/run-pass-valgrind/osx-frameworks.stage2-x86_64-apple-darwin

stdout:


stderr:

==42057== 1,040 bytes in 1 blocks are possibly lost in loss record 337 of 352
==42057== at 0x6DDC: malloc_zone_malloc (in /usr/local/Cellar/valgrind/3.10.0/lib/valgrind/vgpreload_memcheck-amd64-darwin.so)
==42057== by 0xA5C293: NXCreateMapTableFromZone (in /usr/lib/libobjc.A.dylib)
==42057== by 0xA6FD40: nonMetaClasses() (in /usr/lib/libobjc.A.dylib)
==42057== by 0xA61537: objc_registerClassPair (in /usr/lib/libobjc.A.dylib)
==42057== by 0x96A68: __CFMakeNSBlockClasses (in /System/Library/Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation)
==42057== by 0x7E98E: __CFInitialize (in /System/Library/Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation)
==42057== by 0x7FFF5FC13255: ImageLoaderMachO::doImageInit(ImageLoader::LinkContext const&) (in /usr/lib/dyld)
==42057== by 0x7FFF5FC13756: ImageLoaderMachO::doInitialization(ImageLoader::LinkContext const&) (in /usr/lib/dyld)
==42057== by 0x7FFF5FC1006D: ImageLoader::recursiveInitialization(ImageLoader::LinkContext const&, unsigned int, ImageLoader::InitializerTimingList&) (in /usr/lib/dyld)
==42057== by 0x7FFF5FC0FFC3: ImageLoader::recursiveInitialization(ImageLoader::LinkContext const&, unsigned int, ImageLoader::InitializerTimingList&) (in /usr/lib/dyld)
==42057== by 0x7FFF5FC0FEB9: ImageLoader::runInitializers(ImageLoader::LinkContext const&, ImageLoader::InitializerTimingList&) (in /usr/lib/dyld)
==42057== by 0x7FFF5FC01FBF: dyld::initializeMainExecutable() (in /usr/lib/dyld)
==42057==


thread '[run-pass-valgrind] run-pass-valgrind/osx-frameworks.rs' panicked at 'explicit panic', /Users/rustbuild/src/rust-buildbot/slave/auto-mac-64-nopt-t/build/src/compiletest/runtest.rs:1505


Reply to this email directly or view it on GitHub
#30365 (comment).

@pnkfelix
Copy link
Member

@bors r+ c1e12e8

@bors
Copy link
Contributor

bors commented Dec 24, 2015

🙀 c1e12e8 is not a valid commit SHA. Please try again with c1e12e0.

@pnkfelix
Copy link
Member

@bors r+ c1e12e0

@bors
Copy link
Contributor

bors commented Dec 25, 2015

⌛ Testing commit c1e12e0 with merge 7d7856b...

@bors
Copy link
Contributor

bors commented Dec 25, 2015

⛄ The build was interrupted to prioritize another pull request.

@bors
Copy link
Contributor

bors commented Dec 25, 2015

⌛ Testing commit c1e12e0 with merge 8367140...

@bors
Copy link
Contributor

bors commented Dec 25, 2015

💔 Test failed - auto-mac-64-nopt-t

@tamird
Copy link
Contributor Author

tamird commented Dec 25, 2015

Tidy error. Fixed.

On Fri, Dec 25, 2015 at 8:54 AM, bors notifications@github.com wrote:

[image: 💔] Test failed - auto-mac-64-nopt-t
http://buildbot.rust-lang.org/builders/auto-mac-64-nopt-t/builds/7544


Reply to this email directly or view it on GitHub
#30365 (comment).

@tamird
Copy link
Contributor Author

tamird commented Dec 28, 2015

ping @pnkfelix

@pnkfelix
Copy link
Member

@bors r+ a3d81c6

@bors
Copy link
Contributor

bors commented Dec 30, 2015

⌛ Testing commit a3d81c6 with merge 302010d...

@bors
Copy link
Contributor

bors commented Dec 30, 2015

💔 Test failed - auto-linux-64-opt

@pnkfelix
Copy link
Member

@bors retry

@bors
Copy link
Contributor

bors commented Dec 30, 2015

⌛ Testing commit a3d81c6 with merge 09f7c10...

@bors
Copy link
Contributor

bors commented Dec 30, 2015

💔 Test failed - auto-linux-64-opt

@tamird
Copy link
Contributor Author

tamird commented Dec 30, 2015

Needs another retry :(

nagisa added a commit to nagisa/rust that referenced this pull request Dec 31, 2015
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
bors added a commit that referenced this pull request Dec 31, 2015
@bors bors merged commit a3d81c6 into rust-lang:master Dec 31, 2015
@tamird tamird deleted the update-valgrind branch January 1, 2016 00:46
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants