AutoplayMetricsBrowserTest.RecordAutoplayAttemptUkm is flaky
Reported by
rkuk...@yandex-team.ru,
Sep 4
|
||||
Issue description
UserAgent: Mozilla/5.0 (Windows NT 10.0; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/67.0.3396.103 YaBrowser/18.7.0.2695 Yowser/2.5 Safari/537.36
Steps to reproduce the problem:
1. build chromium with enabled address sanitizer
2. run browser_tests.AutoplayMetricsBrowserTest.RecordAutoplayAttemptUkm in a loop
What is the expected behavior?
What went wrong?
out/Debug/browser_tests.exe --gtest_filter=AutoplayMetricsBrowserTest.RecordAutoplayAttemptUkm
IMPORTANT DEBUGGING NOTE: each test is run inside its own process.
For debugging a test inside a debugger, use the
--gtest_filter=<your_test_name> flag along with either
--single_process (to run the test in one launcher/browser process) or
--single-process (to do the above, and also run Chrome in single-process mode).
Using sharding settings from environment. This is shard 0/1
Using 1 parallel jobs.
Note: Google Test filter = AutoplayMetricsBrowserTest.RecordAutoplayAttemptUkm
[==========] Running 1 test from 1 test case.
[----------] Global test environment set-up.
[----------] 1 test from AutoplayMetricsBrowserTest, where TypeParam =
[ RUN ] AutoplayMetricsBrowserTest.RecordAutoplayAttemptUkm
[8244:15708:0904/163425.751:WARNING:discovery_network_list_win.cc(195)] Failed to open Wlan client handle: 1062
[8244:7972:0904/163425.824:WARNING:chrome_browser_main_win.cc(641)] Command line too long for RegisterApplicationRestart: --disable-gpu-process-for-dx12-vulkan-info-collection --gtest_also_run_disabled_tests --gtest_filter=AutoplayMetricsBrowserTest.RecordAutoplayAttemptUkm --single_process --test-launcher-output="C:\projects\tmp\scoped_dir12044_25820\results12044_13381\test_results.xml" --user-data-dir="C:\projects\tmp\scoped_dir12044_25820\d12044_31690" --disable-offline-auto-reload --no-first-run --no-default-browser-check --enable-logging=stderr --disable-default-apps --wm-window-animations-disabled --disable-component-update --test-type=browser --force-color-profile=srgb --disable-zero-browsers-open-for-tests --ipc-connection-timeout=90 --allow-file-access-from-files --dom-automation --log-gpu-control-list-decisions --disable-backgrounding-occluded-windows --disable-gl-drawing-for-tests --override-use-software-gl-for-tests --force-color-profile=srgb --disable-compositor-ukm-for-tests --enable-features=TestFeatureForBrowserTest1 --disable-features=NetworkPrediction,SpeculativePreconnect,TestFeatureForBrowserTest2 --disable-gpu-process-for-dx12-vulkan-info-collection --flag-switches-begin --flag-switches-end --restore-last-session about:blank
[8244:7972:0904/163426.412:WARNING:gaia_auth_fetcher.cc(924)] Could not reach Google Accounts servers: errno -11
[8244:7972:0904/163427.113:WARNING:render_frame_host_impl.cc(431)] InterfaceRequest was dropped, the document is no longer active: content.mojom.RendererAudioOutputStreamFactory
[8244:7972:0904/163427.114:WARNING:render_frame_host_impl.cc(431)] InterfaceRequest was dropped, the document is no longer active: resource_coordinator.mojom.FrameCoordinationUnit
[8244:6692:0904/163427.338:WARNING:embedded_test_server.cc(238)] Request not handled. Returning 404: /favicon.ico
[3148:10528:0904/163427.723:WARNING:owning_audio_manager_accessor.cc(80)] Out of process audio service initializing.
../../chrome/browser/media/autoplay_metrics_browsertest.cc(91): error: Expected equality of these values:
1u
Which is: 1
ukm_entries.size()
Which is: 0
Stack trace:
Backtrace:
testing::internal::UnitTestImpl::CurrentOsStackTraceExceptTop [0x00007FF6435DB0C4+214]
testing::internal::AssertHelper::operator= [0x00007FF6435DA045+265]
testing::internal::TestFactoryImpl<LocaleTestTraditionalChinese_TestStart_Test>::CreateTest [0x00007FF640C54FCD+6075]
content::BrowserTestBase::ProxyRunTestOnMainThreadLoop [0x00007FF64D3ACACB+1769]
ChromeBrowserMainParts::PreMainMessageLoopRunImpl [0x00007FF651A7D984+13052]
ChromeBrowserMainParts::PreMainMessageLoopRun [0x00007FF651A7A241+571]
content::BrowserMainLoop::PreMainMessageLoopRun [0x00007FF646A46AA9+385]
content::StartupTaskRunner::RunAllTasksNow [0x00007FF647D51879+129]
content::BrowserMainLoop::CreateStartupTasks [0x00007FF646A41EFC+2330]
content::BrowserMainRunnerImpl::Initialize [0x00007FF646A50492+572]
content::BrowserMain [0x00007FF646A3A4E1+533]
content::RunBrowserProcessMain [0x00007FF64C508B00+404]
content::ContentMainRunnerImpl::Run [0x00007FF64C50AA6B+2227]
service_manager::Main [0x00007FF64ED83979+4189]
content::ContentMain [0x00007FF64C50884D+265]
content::BrowserTestBase::SetUp [0x00007FF64D3ABB4F+5447]
InProcessBrowserTest::SetUp [0x00007FF64CAAA0A5+1903]
=================================================================
==8244==ERROR: AddressSanitizer: access-violation on unknown address 0x000000000000 (pc 0x7ff640c5504e bp 0x00567a4f9480 sp 0x00567a4f8580 T0)
==8244==The signal is caused by a READ memory access.
==8244==Hint: address points to the zero page.
==8244==*** WARNING: Failed to initialize DbgHelp! ***
==8244==*** Most likely this means that the app is already ***
==8244==*** using DbgHelp, possibly with incompatible flags. ***
==8244==*** Due to technical reasons, symbolization might crash ***
==8244==*** or produce wrong results. ***
#0 0x7ff640c5504d in testing::internal::TestFactoryImpl<LocaleTestTraditionalChinese_TestStart_Test>::CreateTest+0x183b (C:\projects\chromium\src\out\Debug\browser_tests.exe+0x1406c504d)
#1 0x7ff64d3acaca in content::BrowserTestBase::ProxyRunTestOnMainThreadLoop+0x6e8 (C:\projects\chromium\src\out\Debug\browser_tests.exe+0x14ce1caca)
#2 0x7ff651a7d983 in ChromeBrowserMainParts::PreMainMessageLoopRunImpl+0x32fb (C:\projects\chromium\src\out\Debug\browser_tests.exe+0x1514ed983)
#3 0x7ff651a7a240 in ChromeBrowserMainParts::PreMainMessageLoopRun+0x23a (C:\projects\chromium\src\out\Debug\browser_tests.exe+0x1514ea240)
#4 0x7ff646a46aa8 in content::BrowserMainLoop::PreMainMessageLoopRun+0x180 (C:\projects\chromium\src\out\Debug\browser_tests.exe+0x1464b6aa8)
#5 0x7ff647d51878 in content::StartupTaskRunner::RunAllTasksNow+0x80 (C:\projects\chromium\src\out\Debug\browser_tests.exe+0x1477c1878)
#6 0x7ff646a41efb in content::BrowserMainLoop::CreateStartupTasks+0x919 (C:\projects\chromium\src\out\Debug\browser_tests.exe+0x1464b1efb)
#7 0x7ff646a50491 in content::BrowserMainRunnerImpl::Initialize+0x23b (C:\projects\chromium\src\out\Debug\browser_tests.exe+0x1464c0491)
#8 0x7ff646a3a4e0 in content::BrowserMain+0x214 (C:\projects\chromium\src\out\Debug\browser_tests.exe+0x1464aa4e0)
#9 0x7ff64c508aff in content::RunBrowserProcessMain+0x193 (C:\projects\chromium\src\out\Debug\browser_tests.exe+0x14bf78aff)
#10 0x7ff64c50aa6a in content::ContentMainRunnerImpl::Run+0x8b2 (C:\projects\chromium\src\out\Debug\browser_tests.exe+0x14bf7aa6a)
#11 0x7ff64ed83978 in service_manager::Main+0x105c (C:\projects\chromium\src\out\Debug\browser_tests.exe+0x14e7f3978)
#12 0x7ff64c50884c in content::ContentMain+0x108 (C:\projects\chromium\src\out\Debug\browser_tests.exe+0x14bf7884c)
#13 0x7ff64d3abb4e in content::BrowserTestBase::SetUp+0x1546 (C:\projects\chromium\src\out\Debug\browser_tests.exe+0x14ce1bb4e)
#14 0x7ff64caaa0a4 in InProcessBrowserTest::SetUp+0x76e (C:\projects\chromium\src\out\Debug\browser_tests.exe+0x14c51a0a4)
#15 0x7ff6435eb1ae in testing::Test::Run+0xe6 (C:\projects\chromium\src\out\Debug\browser_tests.exe+0x14305b1ae)
#16 0x7ff6435ecd9a in testing::TestInfo::Run+0x306 (C:\projects\chromium\src\out\Debug\browser_tests.exe+0x14305cd9a)
#17 0x7ff6435ede39 in testing::TestCase::Run+0x417 (C:\projects\chromium\src\out\Debug\browser_tests.exe+0x14305de39)
#18 0x7ff643605dc1 in testing::internal::UnitTestImpl::RunAllTests+0x899 (C:\projects\chromium\src\out\Debug\browser_tests.exe+0x143075dc1)
#19 0x7ff643605309 in testing::UnitTest::Run+0x205 (C:\projects\chromium\src\out\Debug\browser_tests.exe+0x143075309)
#20 0x7ff64caf7cb1 in base::TestSuite::Run+0x1c7 (C:\projects\chromium\src\out\Debug\browser_tests.exe+0x14c567cb1)
#21 0x7ff660132865 in ChromeTestSuiteRunner::RunTestSuite+0x10b (C:\projects\chromium\src\out\Debug\browser_tests.exe+0x15fba2865)
#22 0x7ff64d4255de in content::LaunchTests+0x56f (C:\projects\chromium\src\out\Debug\browser_tests.exe+0x14ce955de)
#23 0x7ff660133611 in LaunchChromeTests+0x2d3 (C:\projects\chromium\src\out\Debug\browser_tests.exe+0x15fba3611)
#24 0x7ff660132685 in main+0x161 (C:\projects\chromium\src\out\Debug\browser_tests.exe+0x15fba2685)
#25 0x7ff66015f61f in __scrt_common_main_seh f:\dd\vctools\crt\vcstartup\src\startup\exe_common.inl:283
#26 0x7ffbd7f21fe3 in BaseThreadInitThunk+0x13 (C:\WINDOWS\System32\KERNEL32.DLL+0x180011fe3)
#27 0x7ffbdaa3cb30 in RtlUserThreadStart+0x20 (C:\WINDOWS\SYSTEM32\ntdll.dll+0x18006cb30)
AddressSanitizer can not provide additional info.
SUMMARY: AddressSanitizer: access-violation (C:\projects\chromium\src\out\Debug\browser_tests.exe+0x1406c504d) in testing::internal::TestFactoryImpl<LocaleTestTraditionalChinese_TestStart_Test>::CreateTest+0x183b
==8244==ABORTING
[1/1] AutoplayMetricsBrowserTest.RecordAutoplayAttemptUkm (CRASHED)
1 test crashed:
AutoplayMetricsBrowserTest.RecordAutoplayAttemptUkm (../../chrome/browser/media/autoplay_metrics_browsertest.cc:71)
Did this work before? No
Chrome version: dev Channel: n/a
OS Version: 10.0
Flash Version: Shockwave Flash 30.0 r0
,
Sep 4
,
Sep 6
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/ebe80ad0b059611dc1a7dbc48c827d27577f94c4 commit ebe80ad0b059611dc1a7dbc48c827d27577f94c4 Author: Roman Kuksin <rkuksin@yandex-team.ru> Date: Thu Sep 06 21:55:36 2018 Wait for ukm entry in TryAutoplay The test fails due to a race of UkmRecorder::AddEntry with DOMMessageQueue::Observe: https://cs.chromium.org/chromium/src/services/metrics/public/cpp/delegating_ukm_recorder.cc?q=src/services/metrics/public/cpp/delegating_ukm_recorder.cc&sq=package:chromium&g=0&l=137 Bug: 880217 Change-Id: Icf099c3eb1094d8a571dc6f87b152e3c838807dc Reviewed-on: https://chromium-review.googlesource.com/1204011 Reviewed-by: Tommi <tommi@chromium.org> Reviewed-by: Steven Holte <holte@chromium.org> Commit-Queue: Steven Holte <holte@chromium.org> Cr-Commit-Position: refs/heads/master@{#589317} [modify] https://crrev.com/ebe80ad0b059611dc1a7dbc48c827d27577f94c4/chrome/browser/media/autoplay_metrics_browsertest.cc [modify] https://crrev.com/ebe80ad0b059611dc1a7dbc48c827d27577f94c4/components/ukm/test_ukm_recorder.cc [modify] https://crrev.com/ebe80ad0b059611dc1a7dbc48c827d27577f94c4/components/ukm/test_ukm_recorder.h [modify] https://crrev.com/ebe80ad0b059611dc1a7dbc48c827d27577f94c4/components/ukm/ukm_recorder_impl.h
,
Sep 7
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/1783bb87618bd94cabf6e7d8206fcea52814e9b1 commit 1783bb87618bd94cabf6e7d8206fcea52814e9b1 Author: Yuki Shiino <yukishiino@chromium.org> Date: Fri Sep 07 03:38:42 2018 Revert "Wait for ukm entry in TryAutoplay" This reverts commit ebe80ad0b059611dc1a7dbc48c827d27577f94c4. Reason for revert: Suspicious to break MSan Tests. https://ci.chromium.org/p/chromium/builders/luci.chromium.ci/Linux%20MSan%20Tests/11452 Original change's description: > Wait for ukm entry in TryAutoplay > > The test fails due to a race of UkmRecorder::AddEntry with DOMMessageQueue::Observe: > https://cs.chromium.org/chromium/src/services/metrics/public/cpp/delegating_ukm_recorder.cc?q=src/services/metrics/public/cpp/delegating_ukm_recorder.cc&sq=package:chromium&g=0&l=137 > > Bug: 880217 > Change-Id: Icf099c3eb1094d8a571dc6f87b152e3c838807dc > Reviewed-on: https://chromium-review.googlesource.com/1204011 > Reviewed-by: Tommi <tommi@chromium.org> > Reviewed-by: Steven Holte <holte@chromium.org> > Commit-Queue: Steven Holte <holte@chromium.org> > Cr-Commit-Position: refs/heads/master@{#589317} TBR=tommi@chromium.org,holte@chromium.org,jochen@chromium.org,rkuksin@yandex-team.ru Change-Id: I2c930e1d9ac74bd63ab876f06e494824fd4524d2 No-Presubmit: true No-Tree-Checks: true No-Try: true Bug: 880217 Reviewed-on: https://chromium-review.googlesource.com/1212245 Reviewed-by: Yuki Shiino <yukishiino@chromium.org> Commit-Queue: Yuki Shiino <yukishiino@chromium.org> Cr-Commit-Position: refs/heads/master@{#589423} [modify] https://crrev.com/1783bb87618bd94cabf6e7d8206fcea52814e9b1/chrome/browser/media/autoplay_metrics_browsertest.cc [modify] https://crrev.com/1783bb87618bd94cabf6e7d8206fcea52814e9b1/components/ukm/test_ukm_recorder.cc [modify] https://crrev.com/1783bb87618bd94cabf6e7d8206fcea52814e9b1/components/ukm/test_ukm_recorder.h [modify] https://crrev.com/1783bb87618bd94cabf6e7d8206fcea52814e9b1/components/ukm/ukm_recorder_impl.h
,
Sep 7
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/31fba9dc3ef891a8a866f7472efc4c596abae32e commit 31fba9dc3ef891a8a866f7472efc4c596abae32e Author: Roman Kuksin <rkuksin@yandex-team.ru> Date: Fri Sep 07 12:55:14 2018 Reland "Wait for ukm entry in TryAutoplay" This is a reland of ebe80ad0b059611dc1a7dbc48c827d27577f94c4 Original change's description: > Wait for ukm entry in TryAutoplay > > The test fails due to a race of UkmRecorder::AddEntry with DOMMessageQueue::Observe: > https://cs.chromium.org/chromium/src/services/metrics/public/cpp/delegating_ukm_recorder.cc?q=src/services/metrics/public/cpp/delegating_ukm_recorder.cc&sq=package:chromium&g=0&l=137 > > Bug: 880217 > Change-Id: Icf099c3eb1094d8a571dc6f87b152e3c838807dc > Reviewed-on: https://chromium-review.googlesource.com/1204011 > Reviewed-by: Tommi <tommi@chromium.org> > Reviewed-by: Steven Holte <holte@chromium.org> > Commit-Queue: Steven Holte <holte@chromium.org> > Cr-Commit-Position: refs/heads/master@{#589317} Bug: 880217 Change-Id: I6c5cd4107f74f3102b6bd491323a6ab68f56f911 Reviewed-on: https://chromium-review.googlesource.com/1212802 Reviewed-by: Jochen Eisinger <jochen@chromium.org> Reviewed-by: Tommi <tommi@chromium.org> Commit-Queue: Tommi <tommi@chromium.org> Cr-Commit-Position: refs/heads/master@{#589499} [modify] https://crrev.com/31fba9dc3ef891a8a866f7472efc4c596abae32e/chrome/browser/media/autoplay_metrics_browsertest.cc [modify] https://crrev.com/31fba9dc3ef891a8a866f7472efc4c596abae32e/components/ukm/test_ukm_recorder.cc [modify] https://crrev.com/31fba9dc3ef891a8a866f7472efc4c596abae32e/components/ukm/test_ukm_recorder.h [modify] https://crrev.com/31fba9dc3ef891a8a866f7472efc4c596abae32e/components/ukm/ukm_recorder_impl.h
,
Sep 20
Is the issue fixed now?
,
Nov 27
|
||||
►
Sign in to add a comment |
||||
Comment 1 by dtapu...@chromium.org
, Sep 4