[SERVER-14684] smoke.py shouldn't print a traceback on regular test failures Created: 25/Jul/14  Updated: 22/Jun/15  Resolved: 22/Jun/15

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

Type: Improvement Priority: Major - P3
Reporter: Michael O'Brien Assignee: Unassigned
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Participants:

 Description   

When smoke.py finishes running, it prints output like:

 [2014/07/25 04:28:18.703] 150 tests succeeded
 [2014/07/25 04:28:18.703] 18 tests didn't get run
 [2014/07/25 04:28:18.703] The following tests failed (with exit code):
 [2014/07/25 04:28:18.703] /data/mci/shell/src/jstests/sharding/mongos_rs_shard_failure_tolerance.js	253
 [2014/07/25 04:28:18.711] Traceback (most recent call last):
 [2014/07/25 04:28:18.711]   File "buildscripts/smoke.py", line 1311, in <module>
 [2014/07/25 04:28:18.711]     main()
 [2014/07/25 04:28:18.711]   File "buildscripts/smoke.py", line 1308, in main
 [2014/07/25 04:28:18.711]     report()
 [2014/07/25 04:28:18.711]   File "buildscripts/smoke.py", line 823, in report
 [2014/07/25 04:28:18.711]     raise Exception("Test failures")
 [2014/07/25 04:28:18.711] Exception: Test failures
 [2014/07/25 04:28:18.713] Command failed: exit status 1

The python traceback portion of this is noisy and irrelevant, and distracts from the useful bits when looking at MCI logs.



 Comments   
Comment by Ian Whalen (Inactive) [ 22/Jun/15 ]

max.hirschhorn@10gen.com still an issue w/ resmoke?

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