`npm run create_dist` on macOS produces excessive output with repeated lines
See original GitHub issueDescription
From slack:
A recent macos build log has >200k lines weighing 42M. 115k of those lines (that’s 30M!) are almost identical:
Brave Browser Nightly Framework.dSYM/Contents/Resources/DWARF/Brave Browser Nightly Framework: the DIE at offset X has a DW_AT_specification attribute referring to the DIE at offset Y, which was not marked as a declaration
If the root cause can’t be addressed, just suppressing the message would be good enough. If there is no switch to suppress, perhaps we could patch it away?
Steps to Reproduce
- Run
npm run create_dist
on macOS (or better yet, just look at https://ci.brave.com/job/brave-browser-build-macos-x64/)
Actual result:
Repeated lines that don’t help and make console output too large to be usable.
Expected result:
No repeated messages, a smaller log.
Reproduces how often:
Easily reproduced.
Brave version (brave://version info)
n/a
Version/Channel Information:
- Can you reproduce this issue with the current release? yes
- Can you reproduce this issue with the beta channel? yes
- Can you reproduce this issue with the nightly channel? yes
Other Additional Information:
- Does the issue resolve itself when disabling Brave Shields? n/a
- Does the issue resolve itself when disabling Brave Rewards? n/a
- Is the issue reproducible on the latest version of Chrome? ?
Miscellaneous Information:
Issue Analytics
- State:
- Created 2 years ago
- Comments:34 (10 by maintainers)
Top Results From Across the Web
How to suppress output when running npm scripts
All scripts: You can fix this by suppressing the output of npm overall, by setting the log level to silent in a couple...
Read more >[BUG] npm audit fix doesn't work · Issue #3472 · npm/cli - GitHub
In my project, when running npm audit , one of the reported vulnerable packages is listed with the message “fix available via npm...
Read more >npm-run-all
A CLI tool to run multiple npm-scripts in parallel or sequential. ⤴️ Motivation. Simplify. The official npm run-script command cannot run ...
Read more >After upgrade to Big Sur git stopped working - Apple Developer
After upgrade to Big Sur git stopped working and it keeps prompting to install CLT. According to Xcode-select, see output below CLT is...
Read more >Why npm Scripts? - CSS-Tricks
You will see the same output as running the node-sass command directly in the command line. Any time we create an npm script...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Ah, that’s why I couldn’t find it in GitHub.
I don’t have a patch, sorry. But I did notice that the message is printed here https://chromium.googlesource.com/breakpad/breakpad/+/master/src/common/dwarf_cu_to_module.cc#769 and there’s a few other links to sources and discussion in the slack thread.
@mherrmann I believe @wknapik has a working patch, it just needs to be applied to chromium and submitted to upstream