Issue metadata
Sign in to add a comment
|
ZeroconfPrinterDetectorTest.ZeroconfPrinterDetectorStartObservers flaky on ChromeOS ASAN |
||||||||||||||||||||||
Issue description3 of the last 5 failures at https://build.chromium.org/p/chromium.memory/builders/Linux%20Chromium%20OS%20ASan%20LSan%20Tests%20(1) have been this test https://build.chromium.org/p/chromium.memory/builders/Linux%20Chromium%20OS%20ASan%20LSan%20Tests%20%281%29/builds/24311 https://build.chromium.org/p/chromium.memory/builders/Linux%20Chromium%20OS%20ASan%20LSan%20Tests%20%281%29/builds/24309 https://build.chromium.org/p/chromium.memory/builders/Linux%20Chromium%20OS%20ASan%20LSan%20Tests%20%281%29/builds/24307 hunted back a few more cycles and didn't notice anything suspicious errors like [ RUN ] ZeroconfPrinterDetectorTest.ZeroconfPrinterDetectorStartObservers [16925:16925:1022/180222.208971:2247101837:FATAL:message_loop.h(506)] Check failed: MessageLoop::TYPE_IO == loop->type() (3 vs. 1) #0 0x000000a75791 (/b/s/w/ir/out/Release/unit_tests+0xa75790) #1 0x000011d11c2c (/b/s/w/ir/out/Release/unit_tests+0x11d11c2b) #2 0x000011d68c5f (/b/s/w/ir/out/Release/unit_tests+0x11d68c5e) #3 0x000007e091b0 (/b/s/w/ir/out/Release/unit_tests+0x7e091af) etc.
,
Dec 15 2017
,
Jan 24 2018
The following change removes the offending test file so I'm marking this bug as obsolete. https://chromium-review.googlesource.com/c/chromium/src/+/871660 |
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by bugdroid1@chromium.org
, Oct 23 2017