Closed
Bug 1414141
Opened 7 years ago
Closed 7 years ago
Intermittent TEST-UNEXPECTED-TIMEOUT | /webdriver/tests/state/is_element_selected.py | expected OK
Categories
(Remote Protocol :: Marionette, defect, P5)
Tracking
(Not tracked)
RESOLVED
FIXED
mozilla59
People
(Reporter: intermittent-bug-filer, Assigned: whimboo)
References
Details
(Keywords: intermittent-failure)
Assignee | ||
Comment 1•7 years ago
|
||
Looks like the same issue as bug 1414144, and maybe others.
[task 2017-11-02T22:49:29.685Z] 22:49:29 INFO - PID 6070 | 1509662969677 Marionette DEBUG Received DOM event "DOMContentLoaded" for "about:neterror?e=dnsNotFound&u=http%3A//web-platform.test%3A8000/webdriver/tests/support/inline.py%3Fdoc%3D%253Cinput+id%253Dfoo%253E%26content-type%3Dtext%252Fhtml%253Bcharset%253Dutf-8&c=UTF-8&f=regular&d=Firefox%20can%E2%80%99t%20find%20the%20server%20at%20web-platform.test."
[task 2017-11-02T22:49:32.643Z] 22:49:32 INFO - STDOUT: FAILED
[task 2017-11-02T22:49:33.607Z] 22:49:33 INFO - PID 6070 | 1509662973597 Marionette INFO New connections will no longer be accepted
[task 2017-11-02T22:49:33.925Z] 22:49:33 INFO - PID 6070 | [Child 7387] WARNING: pipe error (16): Connection reset by peer: file /build/firefox-l1g98U/firefox-56.0+build6/ipc/chromium/src/chrome/common/ipc_channel_posix.cc, line 353
[task 2017-11-02T22:49:33.926Z] 22:49:33 INFO - PID 6070 | [Child 7387] WARNING: pipe error (3): Connection reset by peer: file /build/firefox-l1g98U/firefox-56.0+build6/ipc/chromium/src/chrome/common/ipc_channel_posix.cc, line 353
[task 2017-11-02T22:49:33.987Z] 22:49:33 INFO - STDOUT: tests/web-platform/tests/webdriver/tests/state/is_element_selected.py::test_handle_prompt_missing_value
[task 2017-11-02T22:49:33.995Z] 22:49:33 INFO - PID 6070 | 1509662973989 mozrunner::runner INFO Running command: "/builds/worker/workspace/build/application/firefox/firefox" "-marionette" "-profile" "/tmp/rust_mozprofile.fhX3yMuRMozr"
[task 2017-11-02T22:49:35.005Z] 22:49:35 INFO - PID 6070 | 1509662974998 Marionette INFO Enabled via --marionette
The actual failure message makes it hard to simply dupe the bug. James, what is the preferred way to make it still easy for sheriffs to star failures on Treeherder?
Flags: needinfo?(james)
Comment 2•7 years ago
|
||
I don't know, that's kind of a generic issue with the way that we present error information and handle starring that we don't make the proximate cause of the failures clear but only surface the eventual symptom.
Flags: needinfo?(james)
Comment hidden (Intermittent Failures Robot) |
Comment 4•7 years ago
|
||
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → INCOMPLETE
Assignee | ||
Comment 5•7 years ago
|
||
This happens again:
https://treeherder.mozilla.org/logviewer.html#?job_id=155120233&repo=autoland
The increase of failures yesterday is due to the landing of my patch on bug 1403923. A follow-up should hopefully land soon, which then will also fix this bug.
Why do we fail here? It's because the test exceeds the 25s default timeout for opt builds, and takes even way longer for debug builds. Via bug 1403923 the test requests a long timeout now.
Assignee | ||
Comment 6•7 years ago
|
||
This failure is gone now with the increased timeout via bug 1403923.
Assignee: nobody → hskupin
Status: REOPENED → RESOLVED
Closed: 7 years ago → 7 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla59
Comment hidden (Intermittent Failures Robot) |
Comment 8•2 years ago
|
||
Moving bug to Remote Protocol::Marionette component per bug 1815831.
Component: geckodriver → Marionette
Product: Testing → Remote Protocol
You need to log in
before you can comment on or make changes to this bug.
Description
•