Closed Bug 904574 Opened 8 years ago Closed 8 years ago

Crashes during gtests output the failure lines with the testname as 'firefox' which breaks TBPL bug suggestions

Categories

(Testing :: General, defect)

defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED
mozilla26

People

(Reporter: emorley, Assigned: emorley)

References

Details

Attachments

(2 files)

eg:
https://tbpl.mozilla.org/php/getParsedLog.php?id=26483522&tree=Mozilla-Central#error0

{
Summary

PROCESS-CRASH | firefox | application crashed [@ libxul.so + 0x1831918]
gtests TEST-UNEXPECTED-FAIL | firefox | test crashed
make[1]: *** [check] Error 1
make: *** [check] Error 2
}

TBPL then quicksearches roughly "ALL firefox keywords:intermittent-failure", which leads to many false positives.

We should:
1) Use a more specific test name (even a generic "gtest", if we can't extract the exact currently running test.
2) Not double print the crash line, since mozcrash already outputs the PROCESS-CRASH line.
Blocks: 844852
Summary: Crashes during gtest output the failure lines with the testname as 'firefox' which breaks TBPL bug suggestions → Crashes during gtests output the failure lines with the testname as 'firefox' which breaks TBPL bug suggestions
Blocks: 904227
* s/firefox/gtests/
* Removes duplicate crash line
Attachment #789559 - Flags: review?(bgirard)
rungtests.py:8: 'tempfile' imported but unused
rungtests.py:8: 'shutil' imported but unused
rungtests.py:11: 'contextmanager' imported but unused
Attachment #789563 - Flags: review?(bgirard)
Comment on attachment 789559 [details] [diff] [review]
Make crash log output compatible with TBPL

Review of attachment 789559 [details] [diff] [review]:
-----------------------------------------------------------------

::: testing/gtest/rungtests.py
@@ +31,5 @@
>          Return True if the program exits with a zero status, False otherwise.
>          """
>          self.xre_path = xre_path
>          env = self.build_environment()
> +        log.info("Running gtests")

Let's keep gtest singular to avoid confusion. (a few instance below)
Would gtest-<basename> be better? Then again I have no plans on introducing multiple gtest run so this is likely fine.
Attachment #789559 - Flags: review?(bgirard) → review+
Attachment #789563 - Flags: review?(bgirard) → review+
(In reply to Benoit Girard (:BenWa) from comment #3)
> Let's keep gtest singular to avoid confusion. (a few instance below)
> Would gtest-<basename> be better? Then again I have no plans on introducing
> multiple gtest run so this is likely fine.

Singular wfm :-)

We don't add app suffix/prefixes to other psuedo test names (eg 'leakcheck'), so I think we should stick to 'gtest' for now - can always change if we add another.
Would you also like to s/gtests/gtest/ in this existing line?
> log = mozlog.getLogger('gtests')

(results in the logger prefix eg: "gtests TEST-UNEXPECTED-FAIL | firefox | test failed with return code %d")
Yes please.
https://hg.mozilla.org/mozilla-central/rev/a7ceae74e71a
https://hg.mozilla.org/mozilla-central/rev/925bd252ae58
Status: ASSIGNED → RESOLVED
Closed: 8 years ago
Flags: in-testsuite-
Resolution: --- → FIXED
Target Milestone: --- → mozilla26
You need to log in before you can comment on or make changes to this bug.