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

Issue 666387 link

Starred by 3 users
Status: Fixed
Owner:
jbudorick@chromium.org
Closed: Nov 2016
Cc:
█ mikec...@chromium.org
agrieve@chromium.org
msramek@chromium.org
jbudorick@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Android
Pri: 1
Type: Bug



Sign in to add a comment

junit_tests are flaky due to a missing file

Project Member Reported by chromium...@appspot.gserviceaccount.com, Nov 17 2016 
"content_junit_tests (with patch)" 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=ahVzfmNocm9taXVtLXRyeS1mbGFrZXNyKwsSBUZsYWtlIiBjb250ZW50X2p1bml0X3Rlc3RzICh3aXRoIHBhdGNoKQw.

Comment 1 by msramek@chromium.org, Nov 18 2016

Labels: OS-Android
Status: Available (was: Untriaged)
Summary: junit_tests are flaky due to a missing file (was: "content_junit_tests (with patch)" is flaky)
Many tests failing, the trace is approximately the same in all tests - a .jar file in robolectric/ is missing.

Furthermore, the same is seen in other steps, such as components_policy_junit_tests, net_junit_tests, etc.

=====================================================================================================================


java.lang.IllegalArgumentException: File does not exist: /b/c/b/android/src/out/Release/lib.java/third_party/robolectric/shadows-core-3.0-21.jar
	at org.robolectric.internal.dependency.LocalDependencyResolver.validateFile(LocalDependencyResolver.java:55)
	at org.robolectric.internal.dependency.LocalDependencyResolver.getLocalArtifactUrl(LocalDependencyResolver.java:32)
	at org.robolectric.internal.dependency.LocalDependencyResolver.getLocalArtifactUrls(LocalDependencyResolver.java:40)
	at org.robolectric.internal.InstrumentingClassLoaderFactory.getSdkEnvironment(InstrumentingClassLoaderFactory.java:39)
	at org.robolectric.RobolectricTestRunner.runChild(RobolectricTestRunner.java:174)
	at org.robolectric.RobolectricTestRunner.runChild(RobolectricTestRunner.java:53)
	at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
	at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
	at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
	at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
	at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
	at org.robolectric.RobolectricTestRunner$1.evaluate(RobolectricTestRunner.java:139)
	at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
	at org.chromium.testing.local.GtestComputer$GtestSuiteRunner.run(GtestComputer.java:46)
	at org.junit.runners.Suite.runChild(Suite.java:128)
	at org.junit.runners.Suite.runChild(Suite.java:27)
	at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
	at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
	at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
	at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
	at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
	at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
	at org.junit.runner.JUnitCore.run(JUnitCore.java:137)
	at org.junit.runner.JUnitCore.run(JUnitCore.java:115)
	at org.chromium.testing.local.JunitTestMain.main(JunitTestMain.java:105)

Comment 2 by msramek@chromium.org, Nov 18 2016

Cc: msramek@chromium.org mikec...@chromium.org jbudorick@chromium.org
Owner: jbudorick@chromium.org
Doesn't look like an infra problem, since the missing file is not part of an environment, it's generated.

https://cs.chromium.org/chromium/src/third_party/robolectric/BUILD.gn?q=shadows-core-3.0-21&sq=package:chromium&dr=C&l=645-648

+cc robolectric owners, can you help with this?

Comment 3 by jbudorick@chromium.org, Nov 18 2016 

Issue 666536 has been merged into this issue.

Comment 4 by jbudorick@chromium.org, Nov 18 2016

Cc: agrieve@chromium.org
Status: Started (was: Available)
Looking.

Comment 5 by jbudorick@chromium.org, Nov 18 2016 

 Issue 666698  has been merged into this issue.

Comment 6 by jbudorick@chromium.org, Nov 18 2016 

https://chromium.googlesource.com/chromium/src/+/64b310827fc8b5eaa9e8784370d19c1b0f71a700 is responsible, but it no longer cleanly reverts.
Project Member

Comment 8 by bugdroid1@chromium.org, Nov 18 2016 

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

commit 2040bff2a904885249b1d58f3950b80ae45ebcbd
Author: jbudorick <jbudorick@chromium.org>
Date: Fri Nov 18 18:20:05 2016

[android] Fix robolectric shadows-core jar names.

BUG= 666387 
TBR=agrieve@chromium.org

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

[modify] https://crrev.com/2040bff2a904885249b1d58f3950b80ae45ebcbd/third_party/robolectric/BUILD.gn

Comment 9 by fsam...@chromium.org, Nov 18 2016

Labels: -Sheriff-Chromium

Comment 10 by jbudorick@chromium.org, Nov 18 2016

Status: Fixed (was: Started)
►

Sign in to add a comment