Closed
Bug 1442790
Opened 8 years ago
Closed 8 years ago
test-verify may fail: "No checks run."
Categories
(Testing :: General, defect, P5)
Tracking
(firefox62 fixed)
RESOLVED
FIXED
mozilla62
| Tracking | Status | |
|---|---|---|
| firefox62 | --- | fixed |
People
(Reporter: gbrown, Assigned: jmaher)
References
Details
(Keywords: intermittent-failure, Whiteboard: [stockwell unknown])
Attachments
(1 file)
|
7.87 KB,
patch
|
ahal
:
review+
|
Details | Diff | Splinter Review |
In the case addressed by bug 1423771, where a modified file is in a reftest manifest, but the file is not a test file, and the reftest harness avoids the "No tests to run" error, structured logging may still complain "No checks run."
https://treeherder.mozilla.org/logviewer.html#?job_id=165592716&repo=try&lineNumber=5464
Comment 1•8 years ago
|
||
Geoff, hi. OS X tier2 failure log: https://treeherder.mozilla.org/logviewer.html#?job_id=165878348&repo=mozilla-inbound&lineNumber=18702
| Reporter | ||
Updated•8 years ago
|
Assignee: gbrown → nobody
| Comment hidden (Intermittent Failures Robot) |
| Comment hidden (Intermittent Failures Robot) |
| Comment hidden (Intermittent Failures Robot) |
| Assignee | ||
Comment 7•8 years ago
|
||
here is a good view of TV failures:
https://treeherder.mozilla.org/#/jobs?repo=mozilla-inbound&revision=59a49b12b26846302393edfbd20b5e72ef6b1d85&filter-searchStr=tv
the android ones are annotated here, but the jobs are failing because tests are taking too long to run. Should we have fewer tests/chunk on android? It seems like we are not confusing the state of previous failures anymore.
Flags: needinfo?(gbrown)
| Assignee | ||
Comment 8•8 years ago
|
||
I also noticed in that run the TVw jobs, specifically win10 opt, we fail properly on /css/vendor-imports/mozilla/mozilla-central-reftests/shapes1/shape-outside-polygon-032.html, but TV summary shows:
11:32:56 INFO - ### /css/vendor-imports/mozilla/mozilla-central-reftests/shapes1/shape-outside-polygon-032.html ###
11:32:56 INFO - | Subtest | Results | Messages |
11:32:56 INFO - |---------|---------|----------|
11:32:56 INFO - | | FAIL | |
11:32:56 INFO -
11:32:56 INFO - ::: Running tests in a loop 10 times : PASS
11:32:56 INFO - ::: Running tests in a loop with restarts 5 times : PASS
11:32:56 INFO - ::: Running tests in a loop 10 times with flags chaos_mode_flags=3 : PASS
11:32:56 INFO - ::: Running tests in a loop with restarts 5 times with flags chaos_mode_flags=3 : PASS
11:32:56 INFO - :::
11:32:56 INFO - ::: Test verification PASS
11:32:56 INFO - :::
11:32:56 INFO - Return code: 0
11:32:56 WARNING - # TBPL WARNING #
11:32:56 WARNING - setting return code to 1
11:32:56 WARNING - TinderboxPrint: Per-test run of ...\shape-outside-polygon-032.html<br/>: WARNING
but the next test (last test) yields what looks to be success, yet a tbpl warning:
11:34:08 INFO - ### /css/css-syntax/unicode-range-selector.html ###
11:34:08 INFO - | Subtest | Results | Messages |
11:34:08 INFO - |--------------------------------------------------------------------------|---------|----------|
11:34:08 INFO - | | OK | |
11:34:08 INFO - | `Unicode range is not a token, and doesn't cause confusion in selectors` | PASS | |
11:34:08 INFO -
11:34:08 INFO - ::: Running tests in a loop 10 times : PASS
11:34:08 INFO - ::: Running tests in a loop with restarts 5 times : PASS
11:34:08 INFO - ::: Running tests in a loop 10 times with flags chaos_mode_flags=3 : PASS
11:34:08 INFO - ::: Running tests in a loop with restarts 5 times with flags chaos_mode_flags=3 : PASS
11:34:08 INFO - :::
11:34:08 INFO - ::: Test verification PASS
11:34:08 INFO - :::
11:34:08 INFO - Return code: 0
11:34:08 WARNING - # TBPL WARNING #
11:34:08 WARNING - TinderboxPrint: Per-test run of ...\unicode-range-selector.html<br/>: WARNING
it seems like there is more we can do here, I just need more data or other opinions:)
| Comment hidden (Intermittent Failures Robot) |
| Comment hidden (Intermittent Failures Robot) |
| Assignee | ||
Updated•8 years ago
|
Whiteboard: [stockwell needswork]
| Reporter | ||
Updated•8 years ago
|
Flags: needinfo?(gbrown)
Keywords: intermittent-failure
| Reporter | ||
Comment 11•8 years ago
|
||
I'm seeing some things I don't expect - will try to look into this today.
Flags: needinfo?(gbrown)
| Reporter | ||
Comment 12•8 years ago
|
||
https://treeherder.mozilla.org/logviewer.html#?job_id=178010731&repo=autoland
Running command: ['/builds/worker/workspace/build/venv/bin/python', '-u', '/builds/worker/workspace/build/tests/mochitest/runtestsremote.py', ... '--verify-max-time=900', '--verify', u'dom/animation/test/chrome/test_running_on_compositor.html'
...
[task 2018-05-11T07:29:07.073Z] 07:29:07 INFO - 1 INFO TEST-START | dom/animation/test/chrome/test_running_on_compositor.html
...
[task 2018-05-11T07:48:05.001Z] 07:48:05 INFO - SUITE-END | took 365s
[task 2018-05-11T07:48:05.001Z] 07:48:05 INFO - ::: Test verification is taking too long: Giving up!
[task 2018-05-11T07:48:05.001Z] 07:48:05 INFO - ::: So far, all checks passed, but not all checks were run.
[task 2018-05-11T07:48:05.001Z] 07:48:05 INFO - SUITE-START | Running 1 tests
[task 2018-05-11T07:48:05.002Z] 07:48:05 INFO - :::
[task 2018-05-11T07:48:05.002Z] 07:48:05 INFO - ::: Test verification summary for:
[task 2018-05-11T07:48:05.003Z] 07:48:05 INFO - :::
[task 2018-05-11T07:48:05.003Z] 07:48:05 INFO - ::: dom/animation/test/chrome/test_running_on_compositor.html
[task 2018-05-11T07:48:05.003Z] 07:48:05 INFO - :::
[task 2018-05-11T07:48:05.003Z] 07:48:05 INFO - ::: 1. Run each test 10 times in one browser. : Pass
[task 2018-05-11T07:48:05.003Z] 07:48:05 INFO - ::: 2. Run each test 5 times in a new browser each time. : Pass
[task 2018-05-11T07:48:05.004Z] 07:48:05 INFO - ::: 3. Run each test 10 times in one browser, in chaos mode. : Pass
[task 2018-05-11T07:48:05.004Z] 07:48:05 INFO - ::: 4. Run each test 5 times in a new browser each time, in chaos mode. : not run / incomplete
[task 2018-05-11T07:48:05.004Z] 07:48:05 INFO - :::
[task 2018-05-11T07:48:05.005Z] 07:48:05 INFO - ::: Test verification PASSED
...
[task 2018-05-11T07:48:06.103Z] 07:48:06 INFO - SUITE-END | took 1s
[task 2018-05-11T07:48:06.105Z] 07:48:06 INFO - Return code: 0
[task 2018-05-11T07:48:06.106Z] 07:48:06 INFO - TinderboxPrint: mochitest-chrome<br/>6439/0/0
[task 2018-05-11T07:48:06.106Z] 07:48:06 INFO - ##### mochitest-chrome log ends
[task 2018-05-11T07:48:06.106Z] 07:48:06 INFO - # TBPL SUCCESS #
[task 2018-05-11T07:48:06.107Z] 07:48:06 INFO - TinderboxPrint: Per-test run of .../test_running_on_compositor.html<br/>: SUCCESS
Good: A long-running test exceeded the 15 minute max time. Verification passed.
Next test:
[task 2018-05-11T08:06:24.774Z] 08:06:24 INFO - :::
[task 2018-05-11T08:06:24.774Z] 08:06:24 INFO - ::: Test verification summary for:
[task 2018-05-11T08:06:24.774Z] 08:06:24 INFO - :::
[task 2018-05-11T08:06:24.775Z] 08:06:24 INFO - ::: dom/animation/test/chrome/test_animation_properties.html
[task 2018-05-11T08:06:24.775Z] 08:06:24 INFO - :::
[task 2018-05-11T08:06:24.775Z] 08:06:24 INFO - ::: 1. Run each test 10 times in one browser. : Pass
[task 2018-05-11T08:06:24.776Z] 08:06:24 INFO - ::: 2. Run each test 5 times in a new browser each time. : Pass
[task 2018-05-11T08:06:24.776Z] 08:06:24 INFO - ::: 3. Run each test 10 times in one browser, in chaos mode. : Pass
[task 2018-05-11T08:06:24.776Z] 08:06:24 INFO - ::: 4. Run each test 5 times in a new browser each time, in chaos mode. : Pass
[task 2018-05-11T08:06:24.777Z] 08:06:24 INFO - :::
[task 2018-05-11T08:06:24.777Z] 08:06:24 INFO - ::: Test verification PASSED
[task 2018-05-11T08:06:24.777Z] 08:06:24 INFO - :::
...
[task 2018-05-11T08:06:26.100Z] 08:06:26 INFO - SUITE-END | took 1s
[task 2018-05-11T08:06:26.111Z] 08:06:26 INFO - Return code: 0
[task 2018-05-11T08:06:26.112Z] 08:06:26 INFO - TinderboxPrint: mochitest-chrome<br/>5964/0/0
[task 2018-05-11T08:06:26.112Z] 08:06:26 INFO - ##### mochitest-chrome log ends
[task 2018-05-11T08:06:26.112Z] 08:06:26 INFO - # TBPL FAILURE #
[task 2018-05-11T08:06:26.112Z] 08:06:26 WARNING - setting return code to 2
[task 2018-05-11T08:06:26.113Z] 08:06:26 INFO - TinderboxPrint: Per-test run of .../test_animation_properties.html<br/>: FAILURE
I don't understand the TBPL_FAILURE -- I don't see a reason for it.
Next test:
[task 2018-05-11T08:25:31.271Z] 08:25:31 INFO - :::
[task 2018-05-11T08:25:31.271Z] 08:25:31 INFO - ::: Test verification summary for:
[task 2018-05-11T08:25:31.272Z] 08:25:31 INFO - :::
[task 2018-05-11T08:25:31.272Z] 08:25:31 INFO - ::: dom/animation/test/chrome/test_animation_observers_sync.html
[task 2018-05-11T08:25:31.272Z] 08:25:31 INFO - :::
[task 2018-05-11T08:25:31.272Z] 08:25:31 INFO - ::: 1. Run each test 10 times in one browser. : Pass
[task 2018-05-11T08:25:31.273Z] 08:25:31 INFO - ::: 2. Run each test 5 times in a new browser each time. : Pass
[task 2018-05-11T08:25:31.273Z] 08:25:31 INFO - ::: 3. Run each test 10 times in one browser, in chaos mode. : Pass
[task 2018-05-11T08:25:31.274Z] 08:25:31 INFO - ::: 4. Run each test 5 times in a new browser each time, in chaos mode. : Pass
[task 2018-05-11T08:25:31.274Z] 08:25:31 INFO - :::
[task 2018-05-11T08:25:31.274Z] 08:25:31 INFO - ::: Test verification PASSED
[task 2018-05-11T08:25:31.274Z] 08:25:31 INFO - :::
...
[task 2018-05-11T08:25:32.604Z] 08:25:32 INFO - SUITE-END | took 1s
[task 2018-05-11T08:25:32.615Z] 08:25:32 INFO - Return code: 0
[task 2018-05-11T08:25:32.615Z] 08:25:32 INFO - TinderboxPrint: mochitest-chrome<br/>15194/0/0
[task 2018-05-11T08:25:32.615Z] 08:25:32 INFO - ##### mochitest-chrome log ends
[task 2018-05-11T08:25:32.615Z] 08:25:32 INFO - # TBPL FAILURE #
[task 2018-05-11T08:25:32.616Z] 08:25:32 INFO - TinderboxPrint: Per-test run of .../test_animation_observers_sync.html<br/>: FAILURE
Ditto.
Trying to reproduce and debug....
| Reporter | ||
Comment 13•8 years ago
|
||
Also meant to note: "No checks run" is not in this log. It seems like most of the recent failures are mis-stars.
| Reporter | ||
Comment 14•8 years ago
|
||
I think comment 12 and the spike of failures between May 8 and May 12 were addressed by bug 1460666. Android TV with the same tests as comment 12 no longer fails:
https://treeherder.mozilla.org/#/jobs?repo=try&revision=4204109940341027eb20f27d9ef237d4be93bb57
| Reporter | ||
Comment 15•8 years ago
|
||
(In reply to Joel Maher ( :jmaher ) (UTC-4) from comment #7)
> here is a good view of TV failures:
> https://treeherder.mozilla.org/#/jobs?repo=mozilla-
> inbound&revision=59a49b12b26846302393edfbd20b5e72ef6b1d85&filter-searchStr=tv
>
> the android ones are annotated here, but the jobs are failing because tests
> are taking too long to run. Should we have fewer tests/chunk on android?
> It seems like we are not confusing the state of previous failures anymore.
I do not think jobs are or were failing because tests are taking too long to run. When you see
[task 2018-05-11T07:48:05.001Z] 07:48:05 INFO - ::: Test verification is taking too long: Giving up!
[task 2018-05-11T07:48:05.001Z] 07:48:05 INFO - ::: So far, all checks passed, but not all checks were run.
[task 2018-05-11T07:48:05.001Z] 07:48:05 INFO - SUITE-START | Running 1 tests
[task 2018-05-11T07:48:05.002Z] 07:48:05 INFO - :::
[task 2018-05-11T07:48:05.002Z] 07:48:05 INFO - ::: Test verification summary for:
[task 2018-05-11T07:48:05.003Z] 07:48:05 INFO - :::
[task 2018-05-11T07:48:05.003Z] 07:48:05 INFO - ::: dom/animation/test/chrome/test_running_on_compositor.html
[task 2018-05-11T07:48:05.003Z] 07:48:05 INFO - :::
[task 2018-05-11T07:48:05.003Z] 07:48:05 INFO - ::: 1. Run each test 10 times in one browser. : Pass
[task 2018-05-11T07:48:05.003Z] 07:48:05 INFO - ::: 2. Run each test 5 times in a new browser each time. : Pass
[task 2018-05-11T07:48:05.004Z] 07:48:05 INFO - ::: 3. Run each test 10 times in one browser, in chaos mode. : Pass
[task 2018-05-11T07:48:05.004Z] 07:48:05 INFO - ::: 4. Run each test 5 times in a new browser each time, in chaos mode. : not run / incomplete
The harness per-test max-verify-time has been exceeded and the harness explicitly passes, and I expect to see
[task 2018-05-11T07:48:05.005Z] 07:48:05 INFO - ::: Test verification PASSED
Flags: needinfo?(gbrown)
| Comment hidden (Intermittent Failures Robot) |
| Assignee | ||
Comment 17•8 years ago
|
||
ok, let me fix the no checks are run failures, and assume that all is well :)
| Assignee | ||
Comment 18•8 years ago
|
||
a try push:
https://treeherder.mozilla.org/#/jobs?repo=try&revision=c0f5f4abdbdda0a5c1fb31ca9b767058d6ee6d9e
and what we saw before (look at windows):
https://treeherder.mozilla.org/#/jobs?repo=try&revision=fa2bbaad71d7615303d1abcf9bf1d104241c8f87
Comment 19•8 years ago
|
||
Comment on attachment 8980592 [details] [diff] [review]
ignore failures of "no tests run" in per-test mode
Review of attachment 8980592 [details] [diff] [review]:
-----------------------------------------------------------------
I can't say I understand how this fixes the problem, but the code looks good, so nominal r+ from me.
::: testing/mozharness/mozharness/mozilla/structuredlog.py
@@ +127,5 @@
> + RunSummary = namedtuple("RunSummary",
> + ("unexpected_statuses",
> + "expected_statuses",
> + "log_level_counts",
> + "action_counts"))
nit: indentation is off here.
Attachment #8980592 -
Flags: review?(ahal) → review+
Comment 20•8 years ago
|
||
Pushed by jmaher@mozilla.com:
https://hg.mozilla.org/integration/mozilla-inbound/rev/baf00899e3d1
fix test-verify to not fail on: 'No checks run.'. r=ahal
Comment 21•8 years ago
|
||
| bugherder | ||
Status: ASSIGNED → RESOLVED
Closed: 8 years ago
status-firefox62:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → mozilla62
You need to log in
before you can comment on or make changes to this bug.
Description
•