New issue
Advanced search Search tips

Issue 854206 link

Starred by 1 user
Status: Assigned
Owner:
benwells@chromium.org
Cc:
rdevlin....@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 1
Type: Bug



Sign in to add a comment

"ExternalProviderImplChromeOSTest.Standalone" is flaky

Project Member Reported by chromium...@appspot.gserviceaccount.com, Jun 19 2018 
"ExternalProviderImplChromeOSTest.Standalone" 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 4 recent flakes. List of all flakes can be found at https://chromium-try-flakes.appspot.com/all_flake_occurrences?key=ahVzfmNocm9taXVtLXRyeS1mbGFrZXNyNgsSBUZsYWtlIitFeHRlcm5hbFByb3ZpZGVySW1wbENocm9tZU9TVGVzdC5TdGFuZGFsb25lDA.

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

This flaky test/step was previously tracked in  issue 540404 .

Comment 1 by holte@chromium.org, Jun 19 2018 

Test error output:
[ RUN      ] ExternalProviderImplChromeOSTest.Standalone
[8417:8417:0618/220702.391544:16649656204:ERROR:network_service.cc(68)] Not implemented reached in std::unique_ptr<net::NetworkChangeNotifier> network::(anonymous namespace)::CreateNetworkChangeNotifierIfNeeded()
[8417:8530:0618/220702.412314:16649676956:WARNING:local_extension_cache.cc(273)] Could not create cache directory /var/cache/external_cache; extensions cannot be installed from update URLs.
../../chrome/browser/extensions/external_provider_impl_chromeos_unittest.cc:164: Failure
Value of: service_->GetInstalledExtension(kStandaloneAppId)
  Actual: false
Expected: true
Stack trace:
#0 0x00000259a32c testing::internal::UnitTestImpl::CurrentOsStackTraceExceptTop()
#1 0x000002599d09 testing::internal::AssertHelper::operator=()
#2 0x0000016e162c extensions::ExternalProviderImplChromeOSTest_Standalone_Test::TestBody()
../../chrome/browser/extensions/external_provider_impl_chromeos_unittest.cc:166: Failure
Value of: service_->GetInstalledExtension(kStandaloneChildAppId)
  Actual: false
Expected: true
Stack trace:
#0 0x00000259a32c testing::internal::UnitTestImpl::CurrentOsStackTraceExceptTop()
#1 0x000002599d09 testing::internal::AssertHelper::operator=()
#2 0x0000016e1783 extensions::ExternalProviderImplChromeOSTest_Standalone_Test::TestBody()

Comment 2 by holte@chromium.org, Jun 19 2018

Owner: rdevlin....@chromium.org
Status: Assigned (was: Untriaged)

Comment 3 by holte@chromium.org, Jun 19 2018

Cc: rdevlin....@chromium.org
 Issue 854295  has been merged into this issue.
Project Member

Comment 4 by bugdroid1@chromium.org, Jun 19 2018 

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

commit e104d4946b8324d16451adbe6e57ee3851502c64
Author: Steven Holte <holte@google.com>
Date: Tue Jun 19 20:24:31 2018

Disable flaky ExternalProviderImplChromeOSTests

Bug: 854206
TBR=rdevlin.cronin
NOTRY=true

Change-Id: I7788b389478f47bbd37e8336ae1379c6dbad88df
Reviewed-on: https://chromium-review.googlesource.com/1106776
Reviewed-by: Steven Holte <holte@chromium.org>
Commit-Queue: Steven Holte <holte@chromium.org>
Cr-Commit-Position: refs/heads/master@{#568589}
[modify] https://crrev.com/e104d4946b8324d16451adbe6e57ee3851502c64/chrome/browser/extensions/external_provider_impl_chromeos_unittest.cc

Comment 5 by holte@chromium.org, Jun 19 2018

Components: Platform>Extensions
Labels: -Sheriff-Chromium Test-Disabled

Comment 6 by rdevlin....@chromium.org, Jun 19 2018

Labels: OS-Chrome
Owner: benwells@chromium.org
Ben, is there someone on the CrOS team that can take a look at this?
►

Sign in to add a comment