[SERVER-48951] Create a resmoke option that better manages output for reproducing runs locally Created: 18/Jun/20  Updated: 29/Oct/23  Resolved: 24/Jul/20

Status: Closed
Project: Core Server
Component/s: Testing Infrastructure
Affects Version/s: None
Fix Version/s: 4.7.0

Type: Improvement Priority: Major - P3
Reporter: Daniel Gottlieb (Inactive) Assignee: Daniel Gottlieb (Inactive)
Resolution: Fixed Votes: 1
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Backwards Compatibility: Fully Compatible
Sprint: STM 2020-06-29, STM 2020-07-13, STM 2020-07-27, STM 2020-08-10
Participants:
Story Points: 3

 Description   

Resmoke will dump all output into either stdout or a log file. When people are running things locally, they often want:

  • To save all the detailed output into a log file for perusal
  • A way to know that the run may have hit an error condition
  • A way to know that the set of tests is making progress

Many people use a series of mrlog, greps, tee and output redirection to achieve this, e.g:

resmoke run --suite sample_suite | mrlog | tee output_file.log | egrep "invariant|fassert|BACKTRACE|failed to load|..."

Additionally, many people that craft those for individual reproduction attempts, haven't yet realized that saving it as a shell alias/function/script would be useful in the future.

The goal of this ticket is to provide a useful starting point for accomplishing the bullet points using the current keywords that MongoDB tests generate.



 Comments   
Comment by Githook User [ 23/Jul/20 ]

Author:

{'name': 'Daniel Gottlieb', 'email': 'daniel.gottlieb@mongodb.com', 'username': 'dgottlieb'}

Message: SERVER-48951: Add usability options for resmoke output.

--mrlog will pipe all stdout through mrlog.

--userFriendlyOutput=<file> will `tee` all output to <file>. It will filter
stdout with a grep to highlight test progress and possible failures.
Branch: master
https://github.com/mongodb/mongo/commit/19dd40b181c0043cf8989cc216195c5b01472c35

Generated at Thu Feb 08 05:18:31 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.