add debuginfo to test --release
#43
Merged
Conversation
This file contains 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
|
Feel free to merge after fixing the merge conflicts |
japaric
force-pushed
the
test-release-debuginfo
branch
from
73529d8
to
c915534
Compare
|
bors r=jonas-schievink |
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.
executable build with
cargo test --releaseare built with thebenchprofile. By default, this profile is similar to the defaultreleaseprofile so it hasdebug = 0. The result is thatcargo test --releaseresults in (1) log messages having no location information and (2) knurling-rs/probe-run#9, which makes the process exit with nonzero exit code even when all test fails.this PR overrides the
benchprofile to match thereleaseprofile override. This fixes above issues.