-
Notifications
You must be signed in to change notification settings - Fork 2.2k
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
Fix bug in logfile parsing #42706
base: develop
Are you sure you want to change the base?
Fix bug in logfile parsing #42706
Conversation
Rebased for updated audit and style checks. Can you please post a reproducer of the kind of issue that is solved by this PR? |
1295244
to
4863ba2
Compare
@wdconinc I've just added a test case with a sample string. On my system, I get that sample string from gcc without any customization to GCC_COLORS etc. As a larger example, when I break some template-heavy code and try building it, I get the following raw output (copied from vim, so ^[ is an escape key):
Spack's current output file give me lines like so
|
Spack occasionally parses escape sequences incorrectly, leading to confusing chunks of missing text. This replaces the magic code with a more comprehensible regex that aligns with ANSI standards.