New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 635032 link

Starred by 4 users

Issue metadata

Status: Duplicate
Merged: issue 622387
Owner:
Closed: Oct 2016
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 1
Type: Bug
Team-Accessibility



Sign in to add a comment

"BackgroundTest.ActiveOrInactive" is flaky

Project Member Reported by chromium...@appspot.gserviceaccount.com, Aug 5 2016

Issue description

"BackgroundTest.ActiveOrInactive" 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 8 recent flakes. List of all flakes can be found at https://chromium-try-flakes.appspot.com/all_flake_occurrences?key=ahVzfmNocm9taXVtLXRyeS1mbGFrZXNyKgsSBUZsYWtlIh9CYWNrZ3JvdW5kVGVzdC5BY3RpdmVPckluYWN0aXZlDA.

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
 
Project Member

Comment 1 by chromium...@appspot.gserviceaccount.com, Aug 6 2016

Detected 3 new flakes for test/step "BackgroundTest.ActiveOrInactive". To see the actual flakes, please visit https://chromium-try-flakes.appspot.com/all_flake_occurrences?key=ahVzfmNocm9taXVtLXRyeS1mbGFrZXNyKgsSBUZsYWtlIh9CYWNrZ3JvdW5kVGVzdC5BY3RpdmVPckluYWN0aXZlDA. This message was posted automatically by the chromium-try-flakes app.
Project Member

Comment 2 by chromium...@appspot.gserviceaccount.com, Aug 7 2016

Detected 3 new flakes for test/step "BackgroundTest.ActiveOrInactive". To see the actual flakes, please visit https://chromium-try-flakes.appspot.com/all_flake_occurrences?key=ahVzfmNocm9taXVtLXRyeS1mbGFrZXNyKgsSBUZsYWtlIh9CYWNrZ3JvdW5kVGVzdC5BY3RpdmVPckluYWN0aXZlDA. This message was posted automatically by the chromium-try-flakes app.
Project Member

Comment 3 by chromium...@appspot.gserviceaccount.com, Aug 8 2016

Detected 6 new flakes for test/step "BackgroundTest.ActiveOrInactive". To see the actual flakes, please visit https://chromium-try-flakes.appspot.com/all_flake_occurrences?key=ahVzfmNocm9taXVtLXRyeS1mbGFrZXNyKgsSBUZsYWtlIh9CYWNrZ3JvdW5kVGVzdC5BY3RpdmVPckluYWN0aXZlDA. This message was posted automatically by the chromium-try-flakes app.
Components: -Tests>Flaky UI>Accessibility
Status: Available (was: Untriaged)
Cc: aboxhall@chromium.org enne@chromium.org
Components: Internals>Compositing
Owner: dmazz...@chromium.org
Status: Assigned (was: Available)
The primary bug looks like something in AX, but there's also some cc assert here. Not sure which is the root cause.

I don't know how to disable this kind of JS test, please disable it soon.

There's two different things in the logs here:

(once)
BrowserTestBase signal handler received SIGTERM. Backtrace:
#0 0x000001ecb16e base::debug::StackTrace::StackTrace()
#1 0x0000022d3b9a content::(anonymous namespace)::DumpStackTraceSignalHandler()
#2 0x7f06e90a50b0 <unknown>
#3 0x000003187cd3 cc::draw_property_utils::LayerShouldBeSkipped()
#4 0x000003187dd9 cc::draw_property_utils::FindLayersThatNeedUpdates()
#5 0x000003193e4b cc::LayerTreeHost::DoUpdateLayers()
#6 0x0000031939e6 cc::LayerTreeHost::UpdateLayers()
#7 0x0000031d05f1 cc::SingleThreadProxy::DoBeginMainFrame()
#8 0x0000031d122f cc::SingleThreadProxy::BeginMainFrame()
#9 0x000001f51119 base::debug::TaskAnnotator::RunTask()
#10 0x000001ee7785 base::MessageLoop::RunTask()
#11 0x000001ee7a78 base::MessageLoop::DeferOrRunPendingTask()
#12 0x000001ee7dbb base::MessageLoop::DoWork()
#13 0x000001ee9fe9 base::MessagePumpLibevent::Run()
#14 0x000001ee72cd base::MessageLoop::RunHandler()
#15 0x000001f07cf0 base::RunLoop::Run()
#16 0x0000022d7fcc content::RunThisRunLoop()
#17 0x0000022d839c content::MessageLoopRunner::Run()
#18 0x0000022d42fd content::(anonymous namespace)::ExecuteScriptHelper()
#19 0x0000022d46af content::ExecuteScriptAndExtractString()
#20 0x00000043f283 extensions::browsertest_util::ExecuteScriptInBackgroundPage()
#21 0x000000440710 ExtensionJSBrowserTest::RunJavascriptTestF()
#22 0x00000044f512 BackgroundTest_ActiveOrInactive_Test::RunTestOnMainThread()
#23 0x0000022d246b InProcessBrowserTest::RunTestOnMainThreadLoop()
#24 0x0000022d3987 content::BrowserTestBase::ProxyRunTestOnMainThreadLoop()
#25 0x000001f73dc4 ChromeBrowserMainParts::PreMainMessageLoopRunImpl()
#26 0x000001f72df5 ChromeBrowserMainParts::PreMainMessageLoopRun()
#27 0x000001adec45 chromeos::ChromeBrowserMainPartsChromeos::PreMainMessageLoopRun()
#28 0x0000008be115 content::BrowserMainLoop::PreMainMessageLoopRun()
#29 0x000000bfbd27 content::StartupTaskRunner::RunAllTasksNow()
#30 0x0000008bc984 content::BrowserMainLoop::CreateStartupTasks()
#31 0x0000008c0a4a content::BrowserMainRunnerImpl::Initialize()
#32 0x0000008ba127 content::BrowserMain()
#33 0x000001eb326e content::ContentMainRunnerImpl::Run()
#34 0x000001eb1c50 content::ContentMain()
#35 0x0000022d3375 content::BrowserTestBase::SetUp()
#36 0x0000022d1a1c InProcessBrowserTest::SetUp()
#37 0x0000022e2118 testing::Test::Run()
#38 0x0000022e2b63 testing::TestInfo::Run()
#39 0x0000022e2ff3 testing::TestCase::Run()
#40 0x0000022ea019 testing::internal::UnitTestImpl::RunAllTests()
#41 0x0000022e9c5e testing::UnitTest::Run()
#42 0x000005c35483 base::TestSuite::Run()
#43 0x0000022d123b ChromeTestSuiteRunner::RunTestSuite()
#44 0x0000022d508e content::LaunchTests()
#45 0x0000022cf531 main
#46 0x7f06e90907ed __libc_start_main
#47 0x00000043f151 <unknown>

and

(many times)
BrowserTestBase signal handler received SIGTERM. Backtrace:
#0 0x000001ecb16e base::debug::StackTrace::StackTrace()
#1 0x0000022d3b9a content::(anonymous namespace)::DumpStackTraceSignalHandler()
#2 0x7f3d8e8ca0b0 <unknown>
#3 0x7f3d8e987a03 epoll_wait
#4 0x0000022f7b48 epoll_dispatch
#5 0x0000022f56a1 event_base_loop
#6 0x000001ee9fb6 base::MessagePumpLibevent::Run()
#7 0x000001ee72cd base::MessageLoop::RunHandler()
#8 0x000001f07cf0 base::RunLoop::Run()
#9 0x0000022d7fcc content::RunThisRunLoop()
#10 0x0000022d839c content::MessageLoopRunner::Run()
#11 0x0000022d42fd content::(anonymous namespace)::ExecuteScriptHelper()
#12 0x0000022d46af content::ExecuteScriptAndExtractString()
#13 0x00000043f283 extensions::browsertest_util::ExecuteScriptInBackgroundPage()
#14 0x000000440710 ExtensionJSBrowserTest::RunJavascriptTestF()
#15 0x00000044f512 BackgroundTest_ActiveOrInactive_Test::RunTestOnMainThread()
#16 0x0000022d246b InProcessBrowserTest::RunTestOnMainThreadLoop()
#17 0x0000022d3987 content::BrowserTestBase::ProxyRunTestOnMainThreadLoop()
#18 0x000001f73dc4 ChromeBrowserMainParts::PreMainMessageLoopRunImpl()
#19 0x000001f72df5 ChromeBrowserMainParts::PreMainMessageLoopRun()
#20 0x000001adec45 chromeos::ChromeBrowserMainPartsChromeos::PreMainMessageLoopRun()
#21 0x0000008be115 content::BrowserMainLoop::PreMainMessageLoopRun()
#22 0x000000bfbd27 content::StartupTaskRunner::RunAllTasksNow()
#23 0x0000008bc984 content::BrowserMainLoop::CreateStartupTasks()
#24 0x0000008c0a4a content::BrowserMainRunnerImpl::Initialize()
#25 0x0000008ba127 content::BrowserMain()
#26 0x000001eb326e content::ContentMainRunnerImpl::Run()
#27 0x000001eb1c50 content::ContentMain()
#28 0x0000022d3375 content::BrowserTestBase::SetUp()
#29 0x0000022d1a1c InProcessBrowserTest::SetUp()
#30 0x0000022e2118 testing::Test::Run()
#31 0x0000022e2b63 testing::TestInfo::Run()
#32 0x0000022e2ff3 testing::TestCase::Run()
#33 0x0000022ea019 testing::internal::UnitTestImpl::RunAllTests()
#34 0x0000022e9c5e testing::UnitTest::Run()
#35 0x000005c35483 base::TestSuite::Run()
#36 0x0000022d123b ChromeTestSuiteRunner::RunTestSuite()
#37 0x0000022d508e content::LaunchTests()
#38 0x0000022cf531 main
#39 0x7f3d8e8b57ed __libc_start_main
#40 0x00000043f151 <unknown>
Labels: -Sheriff-Chromium

Comment 7 by enne@chromium.org, Aug 9 2016

Cc: jaydasika@chromium.org ajuma@chromium.org weiliangc@chromium.org

Comment 8 by roc...@chromium.org, Aug 10 2016

Cc: dtseng@chromium.org glevin@chromium.org dmazz...@chromium.org
 Issue 625681  has been merged into this issue.
Project Member

Comment 9 by chromium...@appspot.gserviceaccount.com, Aug 12 2016

Labels: Sheriff-Chromium
Detected 12 new flakes for test/step "BackgroundTest.ActiveOrInactive". To see the actual flakes, please visit https://chromium-try-flakes.appspot.com/all_flake_occurrences?key=ahVzfmNocm9taXVtLXRyeS1mbGFrZXNyKgsSBUZsYWtlIh9CYWNrZ3JvdW5kVGVzdC5BY3RpdmVPckluYWN0aXZlDA. 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).
Project Member

Comment 10 by chromium...@appspot.gserviceaccount.com, Aug 13 2016

Detected 9 new flakes for test/step "BackgroundTest.ActiveOrInactive". To see the actual flakes, please visit https://chromium-try-flakes.appspot.com/all_flake_occurrences?key=ahVzfmNocm9taXVtLXRyeS1mbGFrZXNyKgsSBUZsYWtlIh9CYWNrZ3JvdW5kVGVzdC5BY3RpdmVPckluYWN0aXZlDA. This message was posted automatically by the chromium-try-flakes app.
Labels: -Sheriff-Chromium
Tried to disable test, lets see how this goes.
Project Member

Comment 12 by bugdroid1@chromium.org, Aug 16 2016

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/ed7d3c4b27646172ae140e15825c82135fdf0e39

commit ed7d3c4b27646172ae140e15825c82135fdf0e39
Author: sashab <sashab@chromium.org>
Date: Tue Aug 16 02:20:20 2016

Disabled "BackgroundTest.ActiveOrInactive" due to flakiness

Added the DISABLED_ prefix which usually disables tests. Hopefully this
actually disables it, not sure if it works in JS tests.

TBR=aboxhall@chromium.org
BUG= 635032 
CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.linux:closure_compilation

Review-Url: https://codereview.chromium.org/2249963002
Cr-Commit-Position: refs/heads/master@{#412139}

[modify] https://crrev.com/ed7d3c4b27646172ae140e15825c82135fdf0e39/chrome/browser/resources/chromeos/chromevox/cvox2/background/background_test.extjs

Project Member

Comment 13 by chromium...@appspot.gserviceaccount.com, Aug 16 2016

Labels: Sheriff-Chromium
Detected 10 new flakes for test/step "BackgroundTest.ActiveOrInactive". To see the actual flakes, please visit https://chromium-try-flakes.appspot.com/all_flake_occurrences?key=ahVzfmNocm9taXVtLXRyeS1mbGFrZXNyKgsSBUZsYWtlIh9CYWNrZ3JvdW5kVGVzdC5BY3RpdmVPckluYWN0aXZlDA. 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).
Labels: -Sheriff-Chromium
Test disabled per https://codereview.chromium.org/2250363002/
Project Member

Comment 15 by chromium...@appspot.gserviceaccount.com, Aug 17 2016

Labels: Sheriff-Chromium
Detected 9 new flakes for test/step "BackgroundTest.ActiveOrInactive". To see the actual flakes, please visit https://chromium-try-flakes.appspot.com/all_flake_occurrences?key=ahVzfmNocm9taXVtLXRyeS1mbGFrZXNyKgsSBUZsYWtlIh9CYWNrZ3JvdW5kVGVzdC5BY3RpdmVPckluYWN0aXZlDA. 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).
Labels: -Sheriff-Chromium
Mergedinto: 622387
Status: Duplicate (was: Assigned)

Sign in to add a comment