Slightly better error matching when parsing spack logs#5236
Merged
tgamblin merged 1 commit intospack:developfrom Aug 30, 2017
Merged
Slightly better error matching when parsing spack logs#5236tgamblin merged 1 commit intospack:developfrom
tgamblin merged 1 commit intospack:developfrom
Conversation
Member
|
The build didn't fail because of this, though, right? |
tgamblin
approved these changes
Aug 29, 2017
Contributor
Author
|
@tgamblin No, a different reason. |
1 task
2 tasks
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
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.
When compiling llvm I got warnings that spack thought were errors. Things like this:
The problem is that matching "error:" should really check that it is a word.
I think adding
\bshould fix it, but have not tested it, and there may be a better way to do this.