[SERVER-54718] Reduce verbosity of SCons logging output Created: 22/Feb/21 Updated: 29/Oct/23 Resolved: 11/Mar/21 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Build |
| Affects Version/s: | None |
| Fix Version/s: | 4.9.0 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Geert Bosch | Assignee: | Andrew Morrow (Inactive) |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Backwards Compatibility: | Fully Compatible |
| Operating System: | ALL |
| Sprint: | Dev Platform 2021-03-22 |
| Participants: |
| Description |
|
Excessive logging of lines like results in clang-tidy log files where only 10 lines out of 10K lines contain the actual actionable error info. |
| Comments |
| Comment by Githook User [ 11/Mar/21 ] |
|
Author: {'name': 'Andrew Morrow', 'email': 'acm@mongodb.com', 'username': 'acmorrow'}Message: |
| Comment by Andrew Morrow (Inactive) [ 23/Feb/21 ] |
|
Geert's issue is the output caused by --debug=time which we have on by default. For the Node objects produced for the compilation_database.json target, that information isn't useful. We can, probably, make use of --debug=time controllable via an expansion and disable it for the clang-tidy task, which is where it was causing issues. Longer term, it would be better if the output of --debug=time could be redirected to a file, like the cache debugging state can. |