smoke.py shouldn't print a traceback on regular test failures

XMLWordPrintableJSON

    • Type: Improvement
    • Resolution: Done
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: Testing Infrastructure
    • None
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      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.

            Assignee:
            Unassigned
            Reporter:
            Michael O'Brien
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: