Closed
Bug 1374480
Opened 7 years ago
Closed 7 years ago
Intermittent /service-workers/service-worker/fetch-event-redirect.https.html | 'object' object is not iterable
Categories
(Core :: DOM: Service Workers, defect, P5)
Core
DOM: Service Workers
Tracking
()
RESOLVED
INCOMPLETE
People
(Reporter: intermittent-bug-filer, Unassigned)
Details
(Keywords: bulk-close-intermittents, intermittent-failure)
Filed by: wkocher [at] mozilla.com https://treeherder.mozilla.org/logviewer.html#?job_id=108210502&repo=mozilla-inbound https://queue.taskcluster.net/v1/task/RagX4yMtRiSIc6rkcBNtIQ/runs/0/artifacts/public/logs/live_backing.log
Comment 1•7 years ago
|
||
Joel, are the automation errors expected? [task 2017-06-19T14:46:00.003301Z] 14:46:00 ERROR - Lost marionette connection before starting test [task 2017-06-19T14:46:00.004336Z] 14:46:00 INFO - TEST-UNEXPECTED-ERROR | /service-workers/service-worker/fetch-event-redirect.https.html | 'object' object is not iterable [task 2017-06-19T14:46:00.004827Z] 14:46:00 INFO - Traceback (most recent call last): [task 2017-06-19T14:46:00.004922Z] 14:46:00 INFO - File "/home/worker/workspace/build/tests/web-platform/tests/tools/wptrunner/wptrunner/executors/base.py", line 145, in run_test [task 2017-06-19T14:46:00.005859Z] 14:46:00 INFO - result = self.do_test(test) [task 2017-06-19T14:46:00.006726Z] 14:46:00 INFO - File "/home/worker/workspace/build/tests/web-platform/tests/tools/wptrunner/wptrunner/executors/executormarionette.py", line 440, in do_test [task 2017-06-19T14:46:00.007063Z] 14:46:00 INFO - timeout).run() [task 2017-06-19T14:46:00.007096Z] 14:46:00 INFO - TypeError: 'object' object is not iterable
Flags: needinfo?(jmaher)
Comment 2•7 years ago
|
||
I assume that is a by product of the test, but maybe the test failure is a byproduct of the harness. I am not sure, lets ask :jgraham who is the mastermind of wpt.
Flags: needinfo?(jmaher) → needinfo?(james)
Comment 3•7 years ago
|
||
The "Lost marionette connection before starting test" indicates a crash that wasn't detected, probably because it happened after we last called mozcrash. The handling of that is broken, which explains the next error (maybe I should set the status to crash, although it will end up associated with the wrong test since it happens before the current test is even loaded).
Flags: needinfo?(james)
Comment hidden (Intermittent Failures Robot) |
Updated•7 years ago
|
Priority: -- → P5
Updated•7 years ago
|
Status: NEW → RESOLVED
Closed: 7 years ago
Keywords: bulk-close-intermittents
Resolution: --- → INCOMPLETE
You need to log in
before you can comment on or make changes to this bug.
Description
•