Open
Bug 1777369
Opened 3 years ago
Updated 3 years ago
gtest sometimes hangs after all tests are complete
Categories
(Testing :: GTest, defect, P3)
Tracking
(Not tracked)
NEW
People
(Reporter: gbrown, Unassigned)
References
(Blocks 1 open bug)
Details
https://treeherder.mozilla.org/logviewer?job_id=382733678&repo=autoland&lineNumber=379198
[task 2022-06-28T09:39:32.470Z] 09:39:32 INFO - TEST-PASS | SrtpParamInit/TransportSrtpParameterTest.TestSrtpCiphersMismatchCombinations/2 | test completed (time: 221ms)
[task 2022-06-28T09:39:32.470Z] 09:39:32 INFO - TEST-PASS | GTest unit test: passed
[task 2022-06-28T09:39:32.470Z] 09:39:32 INFO - Passed: 6990
[task 2022-06-28T09:39:32.470Z] 09:39:32 INFO - Failed: 0
[task 2022-06-28T09:43:56.842Z] 09:43:56 INFO - gtest INFO | gtest | process wait complete, returncode=-15
[task 2022-06-28T09:43:56.842Z] 09:43:56 WARNING - gtest TEST-UNEXPECTED-FAIL | gtest | timed out after 300 seconds without output
[task 2022-06-28T09:43:56.842Z] 09:43:56 INFO - gtest INFO | rungtests.py exits with code 1
[task 2022-06-28T09:43:56.903Z] 09:43:56 ERROR - Return code: 1
See bug 1115253 for many other failures (but note that there are various failures/causes collected in that bug).
![]() |
Reporter | |
Comment 1•3 years ago
|
||
On successful runs, there is no delay after tests complete.
Comment 2•3 years ago
|
||
The severity field is not set for this bug.
:ahal, could you have a look please?
For more information, please visit auto_nag documentation.
Flags: needinfo?(ahal)
Comment 3•3 years ago
|
||
Priority will depend on frequency of failure, which we likely don't have if bug 1115253 is a catch-all.
Severity: -- → S3
Flags: needinfo?(ahal)
Priority: -- → P3
You need to log in
before you can comment on or make changes to this bug.
Description
•