Closed Bug 1918405 Opened 1 year ago Closed 1 year ago

Figure out why some test failures from bug 1916311 only happened after merge on central, rather than on autoland and try.

Categories

(Core :: CSS Parsing and Computation, task, P3)

Product:
Core
Component:
CSS Parsing and Computation
Type:
task

Tracking

()

Status:
RESOLVED WORKSFORME

People

(Reporter: emilio, Assigned: emilio)

References

(Blocks 1 open bug)

Details

(Whiteboard: [viewtransitions:m1])

Still a mystery to me.

Whiteboard: [viewtransitions:m1]
See Also: → 1926731

The reason is that if something is an expected timeout we don't run it by default / treat it as "backlog". A bit unfortunate but understandable from a resource usage perspective I guess. Would be nice to be able to override it. Joel do you know? :)

Flags: needinfo?(jmaher)
Assignee: nobody → emilio
Status: NEW → RESOLVED
Closed: 1 year ago
Resolution: --- → FIXED
Resolution: FIXED → WORKSFORME

you can run those on try. If these are perma fail in backlog, then it is 1 of 2 things:

  1. the test shouldn't be expected: TIMEOUT
  2. the test is TIMEOUT when run in the full set of tests, but normal in the subset of backlog tests. In this case we should investigate what other tests are running in the same directory (we reboot between directories in the tree of tests) to figure out what is causing the side effect for future tests.
Flags: needinfo?(jmaher)
You need to log in before you can comment on or make changes to this bug.