New issue
Advanced search Search tips

Issue 819873 link

Starred by 2 users

Issue metadata

Status: Duplicate
Merged: issue 820376
Owner:
Closed: Mar 2018
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 1
Type: Bug



Sign in to add a comment

"SettingsAccessibilityTest.EDIT_DICTIONARY_p_as_heading" is flaky

Project Member Reported by chromium...@appspot.gserviceaccount.com, Mar 8 2018

Issue description

"SettingsAccessibilityTest.EDIT_DICTIONARY_p_as_heading" is flaky.

This issue was created automatically by the chromium-try-flakes app. Please find the right owner to fix the respective test/step and assign this issue to them. If the step/test is infrastructure-related, please add Infra-Troopers label and change issue status to Untriaged. When done, please remove the issue from Sheriff Bug Queue by removing the Sheriff-Chromium label.

We have detected 3 recent flakes. List of all flakes can be found at https://chromium-try-flakes.appspot.com/all_flake_occurrences?key=ahVzfmNocm9taXVtLXRyeS1mbGFrZXNyQQsSBUZsYWtlIjZTZXR0aW5nc0FjY2Vzc2liaWxpdHlUZXN0LkVESVRfRElDVElPTkFSWV9wX2FzX2hlYWRpbmcM.

Flaky tests should be disabled within 30 minutes unless culprit CL is found and reverted. Please see more details here: https://sites.google.com/a/chromium.org/dev/developers/tree-sheriffs/sheriffing-bug-queues#triaging-auto-filed-flakiness-bugs
 
Cc: rmcilroy@chromium.org machenb...@chromium.org
Labels: OS-Chrome
Owner: leszeks@chromium.org
Status: Assigned (was: Untriaged)
Essentially, linux-chromeos-rel is broken because of this.
https://ci.chromium.org/buildbot/tryserver.chromium.chromiumos/linux-chromeos-rel/75489
https://ci.chromium.org/buildbot/tryserver.chromium.chromiumos/linux-chromeos-rel/75504
https://ci.chromium.org/buildbot/tryserver.chromium.chromiumos/linux-chromeos-rel/75508
https://ci.chromium.org/buildbot/tryserver.chromium.chromiumos/linux-chromeos-rel/75514
https://ci.chromium.org/buildbot/tryserver.chromium.chromiumos/linux-chromeos-rel/75515
https://ci.chromium.org/buildbot/tryserver.chromium.chromiumos/linux-chromeos-rel/75519
https://ci.chromium.org/buildbot/tryserver.chromium.chromiumos/linux-chromeos-rel/75521
https://ci.chromium.org/buildbot/tryserver.chromium.chromiumos/linux-chromeos-rel/75542

[8873:8873:0308/134241.007285:INFO:CONSOLE(1225)] "Running TestCase SettingsAccessibilityTest.EDIT_DICTIONARY_p_as_heading", source: test_api.js (1225)


#
# Fatal error in ../../v8/src/objects.cc, line 12169
# Debug check failed: IsInterpreted().
#
#
#
#FailureMessage Object: 0x7ffdab091b60#0 0x0000041fb9bc base::debug::StackTrace::StackTrace()
#1 0x00000792fcab gin::(anonymous namespace)::PrintStackTrace()
#2 0x0000077ca9e8 V8_Fatal()
#3 0x0000077ca745 v8::base::(anonymous namespace)::DefaultDcheckHandler()
#4 0x000003baf99f v8::internal::JSFunction::MarkForOptimization()
#5 0x000003cafa27 v8::internal::RuntimeProfiler::Optimize()
#6 0x000003cb0776 v8::internal::RuntimeProfiler::MarkCandidatesForOptimization()
#7 0x0000039a194f v8::internal::StackGuard::HandleInterrupts()
#8 0x000003d18680 v8::internal::__RT_impl_Runtime_Interrupt()
#9 0x2c4fc9d054a4 <unknown>
[8873:8998:0308/134242.151330:ERROR:crash_handler_host_linux.cc(432)] Failed to write crash dump for pid 8981
Cannot upload crash dump: failed to open
Failed to save crash dump: failed to open
BrowserTestBase received signal: Terminated. Backtrace:
#0 0x0000041fb9bc base::debug::StackTrace::StackTrace()
#1 0x00000483ef52 content::(anonymous namespace)::DumpStackTraceSignalHandler()
#2 0x7ff89356ccb0 <unknown>
#3 0x7ff893634693 epoll_wait
#4 0x000004f56dcd epoll_dispatch
#5 0x000004f548bc event_base_loop
#6 0x000004220522 base::MessagePumpLibevent::Run()
#7 0x00000421d839 base::MessageLoop::Run()
#8 0x0000042487b9 base::RunLoop::Run()
#9 0x0000048752d3 content::RunMessageLoop()
#10 0x0000091099f3 WebUITestHandler::RunJavaScriptTestWithResult()
#11 0x000004310bd1 WebUIBrowserTest::RunJavascriptUsingHandler()
#12 0x000004310f53 WebUIBrowserTest::RunJavascriptTestF()
#13 0x0000018aa9c1 SettingsAccessibilityTest_EDIT_DICTIONARY_p_as_heading_Test::RunTestOnMainThread()
#14 0x00000483ecb2 content::BrowserTestBase::ProxyRunTestOnMainThreadLoop()
#15 0x000004352fc0 ChromeBrowserMainParts::PreMainMessageLoopRunImpl()
#16 0x000004351d7a ChromeBrowserMainParts::PreMainMessageLoopRun()
#17 0x0000019cab1a chromeos::ChromeBrowserMainPartsChromeos::PreMainMessageLoopRun()
#18 0x000002a26301 content::BrowserMainLoop::PreMainMessageLoopRun()
#19 0x000002e60365 content::StartupTaskRunner::RunAllTasksNow()
#20 0x000002a24aed content::BrowserMainLoop::CreateStartupTasks()
#21 0x000002a28ef3 content::BrowserMainRunnerImpl::Initialize()
#22 0x000002a22562 content::BrowserMain()
#23 0x0000041c7f1e content::ContentMainRunnerImpl::Run()
#24 0x0000062543a4 service_manager::Main()
#25 0x0000041c6544 content::ContentMain()
#26 0x00000483e83f content::BrowserTestBase::SetUp()
#27 0x00000430b54f InProcessBrowserTest::SetUp()
#28 0x000001d694c1 testing::Test::Run()
#29 0x000001d6a090 testing::TestInfo::Run()
#30 0x000001d6a577 testing::TestCase::Run()
#31 0x000001d75597 testing::internal::UnitTestImpl::RunAllTests()
#32 0x000001d7511e testing::UnitTest::Run()
#33 0x00000431fa92 base::TestSuite::Run()
#34 0x0000041ef7a5 ChromeTestSuiteRunner::RunTestSuite()
#35 0x000004871ad8 content::LaunchTests()
#36 0x0000041efc64 LaunchChromeTests()
#37 0x0000041ef73e main
#38 0x7ff893557f45 __libc_start_main
#39 0x0000005cf3ea _start
[595/806] SettingsAccessibilityTest.EDIT_DICTIONARY_p_as_heading (TIMED OUT)

I believe this is caused by https://chromium-review.googlesource.com/951490
Can it be reverted?
Issue 820259 has been merged into this issue.
Components: Blink>JavaScript
Labels: Stability
Labels: -Sheriff-Chromium
Project Member

Comment 6 by chromium...@appspot.gserviceaccount.com, Mar 9 2018

Labels: Sheriff-Chromium
Detected 36 new flakes for test/step "SettingsAccessibilityTest.EDIT_DICTIONARY_p_as_heading". To see the actual flakes, please visit https://chromium-try-flakes.appspot.com/all_flake_occurrences?key=ahVzfmNocm9taXVtLXRyeS1mbGFrZXNyQQsSBUZsYWtlIjZTZXR0aW5nc0FjY2Vzc2liaWxpdHlUZXN0LkVESVRfRElDVElPTkFSWV9wX2FzX2hlYWRpbmcM. This message was posted automatically by the chromium-try-flakes app. Since flakiness is ongoing, the issue was moved back into Sheriff Bug Queue (unless already there).
Reverted, I'll take a look. This is your classic "this should never happen" check...
Mergedinto: 820376
Status: Duplicate (was: Assigned)

Sign in to add a comment