Closed Bug 1369957 Opened 7 years ago Closed 4 years ago

Intermittent test_reftests_with_caret.html | reftest comparison: == bug956530-1.html bug956530-1-ref.html

Categories

(Core :: Layout, defect, P3)

defect

Tracking

()

RESOLVED FIXED
mozilla75
Tracking Status
firefox75 --- fixed

People

(Reporter: intermittent-bug-filer, Assigned: masayuki)

Details

(Keywords: intermittent-failure, Whiteboard: [stockwell unknown])

Attachments

(1 file)

Summary: Intermittent layout/base/tests/test_reftests_with_caret.html | reftest comparison: == http://mochi.test:8888/tests/layout/base/tests/bug956530-1.html http://mochi.test:8888/tests/layout/base/tests/bug956530-1-ref.html → Intermittent test_reftests_with_caret.html | reftest comparison: == bug956530-1.html bug956530-1-ref.html
this fails primiarily on stylo builds, 19 times in the last week so far:
https://brasstacks.mozilla.com/orangefactor/index.html?display=Bug&bugid=1369957

while this isn't a high frequency failure, we should ensure the right people know about this.

:xidorn, could you help set a priority for working on this?
Flags: needinfo?(xidorn+moz)
This doesn't seem to be related to stylo at all for the data above.

I believe it seems to happen more often on stylo simply because we don't have SETA data for stylo builds, and thus this test runs more frequently on stylo builds then other builds.

Looking at TreeHerder, it seems all mochitests are run on every push for stylo builds, while only a portion of them are usually run for normal builds.
Flags: needinfo?(xidorn+moz)
Whiteboard: [stockwell unknown]

Perhaps, I got the reason.

Assignee: nobody → masayuki
Status: NEW → ASSIGNED
Priority: -- → P3

Currently, bug956530-1.html calls finish() from onfocus of the <input>
element. But the event listener attribute runs multiple times because the
test explicitly sets focus at least twice. So, the test finishes immediately
after first focus event unexpectedly. If the snapshot is compared
immediately after clicking in the <body> which is scheduled next to the
setTimout called by first finish(), the result becomes non-selected
snapshot. That's the reason of the intermittent failure.

Status: ASSIGNED → RESOLVED
Closed: 4 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla75
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: