cat the entire config.log
#142
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
|
Welcome @dpaoliello! It looks like this is your first PR to tikv/jemallocator 🎉 |
dpaoliello
force-pushed
the
cat
branch
2 times, most recently
from
e4620c5 to
50a60f0
Compare
|
That will be too long for general terminal. I think we should distinguish between CI and regular build, perhaps via some environment flag? |
|
The common way is to check |
Signed-off-by: Daniel Paoliello <[email protected]>
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.
We recently hit a build error in the Rust compiler when trying to bump
ccthat came fromjemalloc-syswhile callingconfigure, but since the build script only shows the last 100 lines, we couldn't see the actual error in the build log: rust-lang/rust#146186 (comment)This change replaces
tail 100withcatso that the entireconfigurelog is printed in the build output.