-
Notifications
You must be signed in to change notification settings - Fork 12.6k
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
Valgrind tests fail when compiled dynamically #31968
Labels
A-testsuite
Area: The testsuite used to check the correctness of rustc
C-bug
Category: This is a bug.
T-bootstrap
Relevant to the bootstrap subteam: Rust's build system (x.py and src/bootstrap)
Comments
All the failures seem to be within platform’s dynamic loader. Here’s a few things to try:
|
Any news/changes on this one ? |
Mark-Simulacrum
added
the
A-testsuite
Area: The testsuite used to check the correctness of rustc
label
May 24, 2017
jonas-schievink
added
T-bootstrap
Relevant to the bootstrap subteam: Rust's build system (x.py and src/bootstrap)
and removed
T-bootstrap
Relevant to the bootstrap subteam: Rust's build system (x.py and src/bootstrap)
A-build
labels
Apr 21, 2019
Centril
added a commit
to Centril/rust
that referenced
this issue
Sep 5, 2019
…xcrichton Remove no-prefer-dynamic from valgrind tests This seems to be working locally. Resolves rust-lang#31968
Centril
added a commit
to Centril/rust
that referenced
this issue
Sep 6, 2019
…xcrichton Remove no-prefer-dynamic from valgrind tests This seems to be working locally. Resolves rust-lang#31968
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
A-testsuite
Area: The testsuite used to check the correctness of rustc
C-bug
Category: This is a bug.
T-bootstrap
Relevant to the bootstrap subteam: Rust's build system (x.py and src/bootstrap)
Right now on our bots we're basically in a state where if valgrind rpass tests are compiled dynamically they will all fail, but when compiled statically they will pass. I'm not really sure what's going on unfortunately, but this is either a bug in valgrind or a bug with us, and we should know precisely what it is to ensure something more sinister isn't lurking.
Some links:
The text was updated successfully, but these errors were encountered: