layout/generic/crashtests/1816574.html has assertions when running layout/generic/crashtests standalone
Categories
(Core :: Layout: Columns, defect)
Tracking
()
People
(Reporter: jmaher, Unassigned)
Details
there are no assertions for this test, but when we run crashtests with only the manifest layout/generic/crashtests/crashtests.list, we get assertions:
https://treeherder.mozilla.org/jobs?repo=try&tier=1%2C2%2C3&revision=46fb9ab22a81c82b181efd19ad39bb3543f30594&selectedTaskRun=RpcDBIJDSqCJWiJn3xngCQ.0
14 on desktop, 2 on android. I am going to mark these as expected assertions to move forward on some scheduling changes, but I wanted to get a bug on file in case this is unexpected.
given this, I assume a test which is run from a manifest before layout/generic/crashtests results in leaving the web browser in a state which this test ends up depending on to have zero assertions.
|
Reporter | |
Comment 1•2 years ago
|
||
this will be adjusted in bug 1911702.
|
||
Comment 2•2 years ago
|
||
Thanks for filing this bug.
I tried to reproduce this bug locally on my macbook. When running ./mach crashtest layout/generic/crashtests/1816574.html, there is no assertion. However, when running with headless mode via ./mach crashtest --headless layout/generic/crashtests/1816574.html, I see the following assertion.
###!!! ASSERTION: Shouldn't be incomplete if availableBSize is UNCONSTRAINED.: 'aReflowInput.AvailableBSize() != NS_UNCONSTRAINEDSIZE'
Description
•