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

Issue 704980 link

Starred by 2 users

Issue metadata

Status: Assigned
Owner:
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 1
Type: Bug



Sign in to add a comment

"NaClBrowserTestPnaclSubzero.PnaclErrorHandling" is flaky on Win/Mac/Linux

Project Member Reported by chromium...@appspot.gserviceaccount.com, Mar 24 2017

Issue description

"NaClBrowserTestPnaclSubzero.PnaclErrorHandling" 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=ahVzfmNocm9taXVtLXRyeS1mbGFrZXNyOQsSBUZsYWtlIi5OYUNsQnJvd3NlclRlc3RQbmFjbFN1Ynplcm8uUG5hY2xFcnJvckhhbmRsaW5nDA.

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
 
Example error:

[ RUN      ] NaClBrowserTestPnaclSubzero.PnaclErrorHandling
Xlib:  extension "RANDR" missing on display ":99".
Xlib:  extension "RANDR" missing on display ":99".
[19942:19942:0317/121310.686595:WARNING:audio_manager.cc(295)] Multiple instances of AudioManager detected
[19942:19942:0317/121310.686627:WARNING:audio_manager.cc(254)] Multiple instances of AudioManager detected
[19942:19942:0317/121310.838671:WARNING:password_store_factory.cc(247)] Using basic (unencrypted) store for password storage. See https://chromium.googlesource.com/chromium/src/+/master/docs/linux_password_storage.md for more information about password storage options.
[19942:19981:0317/121311.303176:WARNING:simple_synchronous_entry.cc(1054)] Could not open platform files for entry.
[19942:19942:0317/121311.448680:INFO:nacl_browsertest_util.cc(130)] |||| [STARTUP]
[19942:19942:0317/121311.478389:INFO:nacl_browsertest_util.cc(130)] ||||
[19942:19942:0317/121311.478741:INFO:nacl_browsertest_util.cc(130)] |||| [bad_pexe BEGIN]
[19942:19998:0317/121311.494552:WARNING:embedded_test_server.cc(219)] Request not handled. Returning 404: /favicon.ico
[1,284108928:19:13:11.552833] Native Client module will be loaded at base address 0x00004a8a00000000
[19942:19942:0317/121311.640531:INFO:CONSOLE(0)] "NativeClient: PnaclCoordinator: Invalid PNaCl bitcode header", source: http://127.0.0.1:51759/pnacl_error_handling.html?pnacl=1 (0)
[19942:19942:0317/121311.654827:INFO:nacl_browsertest_util.cc(130)] |||| [bad_pexe PASS]
[19942:19942:0317/121311.655173:INFO:nacl_browsertest_util.cc(130)] ||||
[19942:19942:0317/121311.663521:INFO:nacl_browsertest_util.cc(130)] |||| [bad_pexe_O0 BEGIN]
[1,284108928:19:13:11.709921] Native Client module will be loaded at base address 0x0000412a00000000
[19942:19942:0317/121311.736475:INFO:CONSOLE(0)] "NativeClient: PnaclCoordinator: Invalid PNaCl bitcode header", source: http://127.0.0.1:51759/pnacl_error_handling.html?pnacl=1 (0)
[19942:19942:0317/121311.747426:INFO:nacl_browsertest_util.cc(130)] |||| [bad_pexe_O0 PASS]
[19942:19942:0317/121311.757351:INFO:nacl_browsertest_util.cc(130)] ||||
[19942:19942:0317/121311.758121:INFO:nacl_browsertest_util.cc(130)] |||| [bad_nonfinal_pexe_O0 BEGIN]
[1,284108928:19:13:11.917122] Native Client module will be loaded at base address 0x00000e5700000000
BrowserTestBase received signal: Terminated. Backtrace:
#0 0x000002e647b7 base::debug::StackTrace::StackTrace()
#1 0x000003555ea6 content::(anonymous namespace)::DumpStackTraceSignalHandler()
#2 0x7f3a3db34cb0 <unknown>
#3 0x7f3a3dbeafdd __poll
#4 0x7f3a43596fe4 <unknown>
#5 0x7f3a435970ec g_main_context_iteration
#6 0x000002e86dd6 base::MessagePumpGlib::Run()
#7 0x000002e844be base::MessageLoop::RunHandler()
#8 0x000002ead26c base::RunLoop::Run()
#9 0x0000035884ec content::RunMessageLoop()
#10 0x0000035634d9 content::JavascriptTestObserver::Run()
#11 0x0000012ea158 NaClBrowserTestBase::RunNaClIntegrationTest()
#12 0x0000012e5d8e (anonymous namespace)::NaClBrowserTestPnacl_PnaclErrorHandling_Test::RunTestOnMainThread()
#13 0x000002f3d00f InProcessBrowserTest::RunTestOnMainThreadLoop()
#14 0x000003555c16 content::BrowserTestBase::ProxyRunTestOnMainThreadLoop()
#15 0x00000337d2c9 ChromeBrowserMainParts::PreMainMessageLoopRunImpl()
#16 0x00000337c181 ChromeBrowserMainParts::PreMainMessageLoopRun()
#17 0x000001abab35 content::BrowserMainLoop::PreMainMessageLoopRun()
#18 0x000001eab626 content::StartupTaskRunner::RunAllTasksNow()
#19 0x000001ab89cb content::BrowserMainLoop::CreateStartupTasks()
#20 0x000001abe71e content::BrowserMainRunnerImpl::Initialize()
#21 0x000001ab5de8 content::BrowserMain()
#22 0x000002e3ff73 content::RunNamedProcessTypeMain()
#23 0x000002e40c86 content::ContentMainRunnerImpl::Run()
#24 0x000002e3f284 content::ContentMain()
#25 0x000003555520 content::BrowserTestBase::SetUp()
#26 0x000002f3b651 InProcessBrowserTest::SetUp()
#27 0x000003d2a39e testing::Test::Run()
#28 0x000003d2af60 testing::TestInfo::Run()
#29 0x000003d2b2d7 testing::TestCase::Run()
#30 0x000003d32527 testing::internal::UnitTestImpl::RunAllTests()
#31 0x000003d321a7 testing::UnitTest::Run()
#32 0x000002f4e7b1 base::TestSuite::Run()
#33 0x000002e54cc8 ChromeTestSuiteRunner::RunTestSuite()
#34 0x00000358501c content::LaunchTests()
#35 0x000002e54c47 main
#36 0x7f3a3db1ff45 __libc_start_main
#37 0x000000604151 <unknown>
This test always fails in concert with MediaFileValidatorTest.UnsupportedExtension, which may be useful information for tracking down the underlying cause.

MediaFileValidatorTest.UnsupportedExtension was disabled in  bug 704614 .
Cc: bradnelson@chromium.org
Labels: -Sheriff-Chromium
Owner: mseaborn@chromium.org
I don't see an obvious change that would lead this to flake. Assigning bug based on OWNER information.
Project Member

Comment 4 by bugdroid1@chromium.org, Mar 24 2017

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

commit 44b664eb0800e5367ebb927691fb4a213957e1f6
Author: wittman <wittman@chromium.org>
Date: Fri Mar 24 19:12:45 2017

Disable NaClBrowserTestPnaclSubzero.PnaclErrorHandling on Linux

Flaky on linux_chromium_rel_ng.

TBR=mseaborn
BUG=704980

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

[modify] https://crrev.com/44b664eb0800e5367ebb927691fb4a213957e1f6/chrome/test/nacl/nacl_browsertest.cc

The previous CL actually disabled the NaClBrowserTestPnacl.PnaclErrorHandling test (oops), but this was flaky also under  bug 704979 , so no harm done.
Project Member

Comment 6 by bugdroid1@chromium.org, Mar 24 2017

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

commit 369b8f475926bbf246b569ffb7d6236b7946f209
Author: wittman <wittman@chromium.org>
Date: Fri Mar 24 21:44:43 2017

Disable NaClBrowserTestPnaclSubzero.PnaclErrorHandling on Linux for real

Flaky on linux_chromium_rel_ng.

TBR=mseaborn@chromium.org
BUG=704980

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

[modify] https://crrev.com/369b8f475926bbf246b569ffb7d6236b7946f209/chrome/test/nacl/nacl_browsertest.cc

Cc: mseaborn@chromium.org
 Issue 704979  has been merged into this issue.
Status: Assigned (was: Untriaged)
Labels: Sheriff-Chromium
Detected 5 new flakes for test/step "NaClBrowserTestPnaclSubzero.PnaclErrorHandling". To see the actual flakes, please visit https://chromium-try-flakes.appspot.com/all_flake_occurrences?key=ahVzfmNocm9taXVtLXRyeS1mbGFrZXNyOQsSBUZsYWtlIi5OYUNsQnJvd3NlclRlc3RQbmFjbFN1Ynplcm8uUG5hY2xFcnJvckhhbmRsaW5nDA. 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).
Summary: "NaClBrowserTestPnaclSubzero.PnaclErrorHandling" is flaky on Win/Mac/Linux (was: "NaClBrowserTestPnaclSubzero.PnaclErrorHandling" is flaky)
 Issue 870309  has been merged into this issue.
Project Member

Comment 12 by bugdroid1@chromium.org, Aug 6

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

commit 4fff9d396231ba4b38a77a237717e8e625f7a1d6
Author: Balazs Engedy <engedy@chromium.org>
Date: Mon Aug 06 15:24:46 2018

Disable NaClBrowserTestPnacl.PnaclErrorHandling on Mac.

The test is flaky on Mac as well.

Bug: 704980
Change-Id: I6d56312bd8ffb8fffe6911535a0029d95a27812a
TBR: mseaborn@chromium.org
Reviewed-on: https://chromium-review.googlesource.com/1163676
Commit-Queue: Balazs Engedy <engedy@chromium.org>
Reviewed-by: Balazs Engedy <engedy@chromium.org>
Cr-Commit-Position: refs/heads/master@{#580874}
[modify] https://crrev.com/4fff9d396231ba4b38a77a237717e8e625f7a1d6/chrome/test/nacl/nacl_browsertest.cc

Labels: -Sheriff-Chromium

Sign in to add a comment