Open Bug 1594135 Opened 6 years ago Updated 3 years ago

Assertions triggered during Reflow of one crashtest may be counted against the next test

Categories

(Testing :: Reftest, defect, P3)

Product:
Testing
Component:
Reftest
Version:
Version 3
Type:
defect

Tracking

(Not tracked)

People

(Reporter: gbrown, Unassigned)

References

Details

Noticed in bug 1584040: An assertion apparently triggered by one test affected the following test. An asserts-if had to be added to the following test to avoid intermittent failures.

(While I agree this situation is inconvenient, I don't personally expect there is any way to fully guard against it, short of running each test in a separate browser. dbaron asked for this follow-up to be filed.)

In this particular case, the assertion stack showed Reflow on the stack when this happens -- while there are some things that could reasonably be happening after the next document has loaded, Reflow shouldn't be one of them. (It's also why we load about:blank between tests in the harness.)

Summary: Assertions triggered by one crashtest may affect the next test → Assertions triggered during Reflow of one crashtest may be counted against the next test

The priority flag is not set for this bug.
:ahal, could you have a look please?

For more information, please visit auto_nag documentation.

Flags: needinfo?(ahal)
Flags: needinfo?(ahal)
Priority: -- → P3
Severity: normal normal → S3 S3
You need to log in before you can comment on or make changes to this bug.