valgrind: update suppressions and move interesting tests #29699
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
(rust_highfive has picked a reviewer for you, use r? to override) |
|
🙀 |
|
Heh, what's up with bors? |
|
@alexcrichton ah, sorry the commits are not rendering in the correct order on this branch. @bors is correct that 269a811 is the one you want. |
|
@bors: r+ 269a811 |
|
⌛ Testing commit 269a811 with merge 26b3204... |
|
💔 Test failed - auto-win-msvc-64-opt |
|
@bors: retry On Mon, Nov 9, 2015 at 11:02 AM, bors [email protected] wrote:
|
|
⌛ Testing commit 269a811 with merge 4afa9d9... |
bors
added a commit
that referenced
this pull request
Nov 10, 2015
Quite a bit of cruft in the valgrind suppressions. I started from a clean slate and found a few unique failures; this commit also moves the tests "fixed" by these suppressions into run-pass-valgrind.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Quite a bit of cruft in the valgrind suppressions. I started from a clean slate and found a few unique failures; this commit also moves the tests "fixed" by these suppressions into run-pass-valgrind.