[SERVER-18840] resmoke should indicate status of test in abbreviated log output during run, before logging everything at the end Created: 05/Jun/15  Updated: 07/Jan/19  Resolved: 07/Jan/19

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

Type: Improvement Priority: Major - P3
Reporter: Michael O'Brien Assignee: Jonathan Abrahams
Resolution: Done Votes: 0
Labels: techdebt, tig-resmoke
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Backwards Compatibility: Fully Compatible
Sprint: DAG 2019-01-14
Participants:
Story Points: 1

 Description   

When resmoke is running a batch of tests and logging to buildlogger, after each test finishes it prints a line like:

 [2015/05/20 13:12:36.365] [executor:js_test:job0] sync_passive.js ran in 138.85 seconds.

It would be helpful to indicate here if the test passed/failed, so if a suite is running in evergreen but hasn't finished yet, i can eyeball if the suite is going to fail by looking at the logs.



 Comments   
Comment by Githook User [ 07/Jan/19 ]

Author:

{'username': 'hptabster', 'email': 'jonathan@mongodb.com', 'name': 'Jonathan Abrahams'}

Message: SERVER-18840 resmoke should indicate status of test in abbreviated log output during run, before logging everything at the end
Branch: master
https://github.com/mongodb/mongo/commit/428ca4fcc799c43bf1b030798705ed98a5608d51

Comment by David Bradford (Inactive) [ 06/Nov/18 ]

We should ensure that any changes to the messages will not impact extraction tools.

Comment by Michael O'Brien [ 06/Jun/15 ]

To avoid that confusion, perhaps the log output could say something like "sync_passive.js ran with no failed assertions" to distinguish that situation from a failure caused by a mongod crash.

Comment by Max Hirschhorn [ 06/Jun/15 ]

One thing about recording this information in the logs when displaying how long the test took to run is that we may later mark the test as having "failed" if the mongod crashed as a result of running the test. I'm not sure if saying the test succeeded and then displaying it as failing in the Evergreen UI would be confusing.

Generated at Thu Feb 08 03:48:54 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.