MemoryTracingBrowserTest.TestMemoryInfra is flaky due to excessive output |
||||
Issue description
MemoryTracingBrowserTest.TestMemoryInfra passes but is marked as failing on the Linux Chromium OS ASan LSan bot, because it's producing too much output. I will disable the test.
From logs:
SUMMARY: AddressSanitizer: 226605 byte(s) leaked in 1201 allocation(s).
-----------------------------------------------------
Suppressions used:
count bytes template
2 288 libfontconfig
-----------------------------------------------------
[9747:9747:0129/101639.184518:INFO:chrome_cryptauth_service.cc(239)] Refresh token not yet available; waiting before starting CryptAuth managers.
[9747:9747:0129/101639.322598:WARNING:url_request_context_getter.cc(43)] URLRequestContextGetter leaking due to no owning thread.
[9747:9747:0129/101639.322682:WARNING:url_request_context_getter.cc(43)] URLRequestContextGetter leaking due to no owning thread.
[ OK ] MemoryTracingBrowserTest.TestMemoryInfra (11204 ms)
[841/841] MemoryTracingBrowserTest.TestMemoryInfra (12070 ms)
1 test produced excessive output:
MemoryTracingBrowserTest.TestMemoryInfra (../../chrome/test/base/memory_tracing_browsertest.cc:117)
Example failures:
https://ci.chromium.org/buildbot/chromium.memory/Linux%20Chromium%20OS%20ASan%20LSan%20Tests%20%281%29/25920
https://ci.chromium.org/buildbot/chromium.memory/Linux%20Chromium%20OS%20ASan%20LSan%20Tests%20%281%29/25919
,
Feb 6 2018
@ssid@ can you PTAL at this disable for the loss of test coverage?
,
Feb 14 2018
Is it ok to disable only on lsan bots using "#if defined(LEAK_SANITIZER)" ? The output is because of leak stack traces. The test should not output much without lsan enabled.
,
Feb 14 2018
It should be okay. I only saw it on that one bot when I was sheriff.
,
Feb 17 2018
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/ffd709bfcc3e5c1d1a698d02cc021a15c9dcd52b commit ffd709bfcc3e5c1d1a698d02cc021a15c9dcd52b Author: Siddhartha <ssid@chromium.org> Date: Sat Feb 17 01:28:52 2018 Disable MemoryTracingBrowserTest.TestMemoryInfra only on lsan bots The test produces too much output due to leaks in html parser. https://crbug.com/804853 BUG=806988 TBR=bsep@chromium.org Change-Id: I12b45a16bd25e320021dc495e6031924ba1ac3a5 Reviewed-on: https://chromium-review.googlesource.com/924462 Commit-Queue: Siddhartha S <ssid@chromium.org> Reviewed-by: Siddhartha S <ssid@chromium.org> Cr-Commit-Position: refs/heads/master@{#537497} [modify] https://crrev.com/ffd709bfcc3e5c1d1a698d02cc021a15c9dcd52b/chrome/test/base/memory_tracing_browsertest.cc
,
Mar 19 2018
@ssid@ can you PTAL at this disable for the loss of test coverage? |
||||
►
Sign in to add a comment |
||||
Comment 1 by bugdroid1@chromium.org
, Jan 29 2018