[SERVER-57679] Extract compile and lint failures into "tests" tab in EVG Created: 28/Oct/20 Updated: 09/Nov/23 |
|
| Status: | Backlog |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Minor - P4 |
| Reporter: | Judah Schvimer | Assignee: | [DO NOT ASSIGN] Backlog - DevProd Correctness |
| Resolution: | Unresolved | Votes: | 1 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Assigned Teams: |
Correctness
|
||||
| Participants: | |||||
| Description |
|
Sifting through the "task logs" when a compile or lint failure happens in EVG to find the actual failure can be a minor pain. It would be a time saver to surface these failures more clearly in evergreen. |
| Comments |
| Comment by Ryan Egesdahl (Inactive) [ 07/Jul/21 ] |
|
For the linter, I think this is very doable. We would have to modernize the logging a bit and set the logger up appropriately, but I think it would only take a couple of days to do that. Compile logging is a somewhat different story, though, and it involves adding an entirely new logging feature to our build process. We may be able to use a fairly method I found to set this up in SConstruct, but I am not entirely sure it won't affect other things like `ninja` and such. If not, it's going to require a much larger effort to do. I'll give both a good try and see how far I get. |
| Comment by Robert Guo (Inactive) [ 08/Jun/21 ] |
|
+1 for this feature. I think it'll have to be on SDP though since compile and lint go through SCons. You'd need to log the output to a file, presumably by a first-class logger and not redirecting existing output to a log file. Then you can generate report.json file based on SCons' exit code per Maria's wiki page link. The 3 timing-related fields can be filled with dummy values if we want the simplest solution. cc acm |
| Comment by Maria van Keulen [ 08/Jun/21 ] |
|
Thanks for this request judah.schvimer. I think this might be feasible by leveraging Evergreen's attach.results command in the mongodb-mongo-* YAML to attach some 'test' logs to the compile/lint task failure. I'd like to pass this back to a team that contributes to the mongodb-mongo-* codebase, if this is something that the team would like to proceed with. |