Closed Bug 1785395 Opened 4 years ago Closed 1 year ago

Intermittent /acid/acid2/reftest.html | single tracking bug

Categories

(Testing :: web-platform-tests, defect, P3)

Default
defect

Tracking

(firefox-esr128 unaffected, firefox137 unaffected, firefox138 unaffected, firefox139 wontfix)

RESOLVED INCOMPLETE
Tracking Status
firefox-esr128 --- unaffected
firefox137 --- unaffected
firefox138 --- unaffected
firefox139 --- wontfix

People

(Reporter: jmaher, Unassigned)

References

Details

(Keywords: intermittent-failure, intermittent-testcase)

Attachments

(1 obsolete file)

No description provided.

Additional information about this bug failures and frequency patterns can be found by running: ./mach test-info failure-report --bug 1785395

Status: NEW → RESOLVED
Closed: 3 years ago
Resolution: --- → INCOMPLETE
Status: RESOLVED → REOPENED
Resolution: INCOMPLETE → ---
Status: REOPENED → RESOLVED
Closed: 3 years ago3 years ago
Resolution: --- → INCOMPLETE
Status: RESOLVED → REOPENED
Resolution: INCOMPLETE → ---
Status: REOPENED → RESOLVED
Closed: 3 years ago2 years ago
Resolution: --- → INCOMPLETE
Status: RESOLVED → REOPENED
Resolution: INCOMPLETE → ---
Attachment #9385083 - Attachment is obsolete: true
Status: REOPENED → RESOLVED
Closed: 2 years ago2 years ago
Resolution: --- → INCOMPLETE
Status: RESOLVED → REOPENED
Resolution: INCOMPLETE → ---
Status: REOPENED → RESOLVED
Closed: 2 years ago1 year ago
Resolution: --- → INCOMPLETE
Status: RESOLVED → REOPENED
Resolution: INCOMPLETE → ---
Status: REOPENED → RESOLVED
Closed: 1 year ago1 year ago
Resolution: --- → INCOMPLETE
Status: RESOLVED → REOPENED
Resolution: INCOMPLETE → ---

Something may have regressed here that's worth worrying about...

We have only three reports of test failures for the whole year (which are in fact just unexpected assertion-failures), and then starting on 4/11, we've got multiple failures (not assertion failures, but actual rendering failures) per day.

This isn't platform-specific, either - previous comments show that we've got failures on Android, Linux, and Windows. They all seem to be on slower configurations, though -- either debug or opt-with-ASAN.

The first commit on 4/11 with a reftest failure is autoland 303fc19db920e2b98df3b0e4e345a10550bada6b, with failure log here

In all of the failures, the acid2 smiley-face's eyes are missing in the testcase's reftest snapshot, and that stripe of the face (where the eyes should be) is either orange-red (as in this log) or just blank yellow. (as in this log).

(In reply to Daniel Holbert [:dholbert] from comment #54)

The first commit on 4/11 with a reftest failure is autoland 303fc19db920e2b98df3b0e4e345a10550bada6b, with failure log here

Aha -- looking at TreeHerder leading up to that commit, it seems someone has already done backfills to previous cycles there (the jobs called "Wr6-303fc19db92-bk"), and it looks a lot like the test failures start on the push for bug 1954597. I'll spin off a dedicated bug for this regression, marked as blocking this intermittent and regressed-by bug 1954597.

Depends on: 1961008
Keywords: regression
Regressed by: 1954597

Set release status flags based on info from the regressing bug 1954597

:nika, since you are the author of the regressor, bug 1954597, could you take a look?

For more information, please visit BugBot documentation.

This is an existing failure. There is already another bug (bug 1961008), which has been created to track the recent regression. Let's remove the regressed by here, and track the work in the other bug.

Flags: needinfo?(nika)
No longer regressed by: 1954597
Status: REOPENED → RESOLVED
Closed: 1 year ago1 year ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: