ForceMaximizeOnFirstRunTest tests failing / timing out on Linux Chromium OS ASan LSan Tests (1) |
||||
Issue descriptionExample run: https://ci.chromium.org/p/chromium/builders/luci.chromium.ci/Linux%20Chromium%20OS%20ASan%20LSan%20Tests%20%281%29/29886 Stack trace: [29071:29071:1031/124827.377801:FATAL:web_contents_observer_sanity_checker.cc(314)] Check failed: is_loading_. #0 0x0000010077a1 (/b/s/w/ir/out/Release/browser_tests+0x10077a0) #1 0x000012af61ff (/b/s/w/ir/out/Release/browser_tests+0x12af61fe) #2 0x00001289a470 (/b/s/w/ir/out/Release/browser_tests+0x1289a46f) #3 0x00001441ec20 (/b/s/w/ir/out/Release/browser_tests+0x1441ec1f) #4 0x00000c3ef503 (/b/s/w/ir/out/Release/browser_tests+0xc3ef502) #5 0x00000c40df24 (/b/s/w/ir/out/Release/browser_tests+0xc40df23) Flakiness dashboard: https://screenshot.googleplex.com/RpDODoxJosQ
,
Nov 2
Adding OWNERs. Please have a look. The test does not fail now, because it succeeds on retries. But this is still worth looking into.
,
Nov 22
Reassigning to the author of the test.
,
Jan 11
This issue has an owner, a component and a priority, but is still listed as untriaged or unconfirmed. By definition, this bug is triaged. Changing status to "assigned". Please reach out to me if you disagree with how I've done this. |
||||
►
Sign in to add a comment |
||||
Comment 1 by tbansal@chromium.org
, Oct 31