New issue
Advanced search Search tips

Issue 808977 link

Starred by 3 users

Issue metadata

Status: Fixed
Owner:
Closed: Nov 7
EstimatedDays: ----
NextAction: ----
OS: Android
Pri: 2
Type: ----



Sign in to add a comment

chrome_public_test_vr_apk-pixelxl-ddview-nougat on Android failing on chromium.android/Nougat Phone Tester

Project Member Reported by sheriff-...@appspot.gserviceaccount.com, Feb 5 2018

Issue description

Filed by sheriff-o-matic@appspot.gserviceaccount.com on behalf of gsennton@google.com

chrome_public_test_vr_apk-pixelxl-ddview-nougat on Android failing on chromium.android/Nougat Phone Tester

Builders failed on: 
- Nougat Phone Tester: 
  https://build.chromium.org/p/chromium.android/builders/Nougat%20Phone%20Tester

Looks like the culprit is https://chromium-review.googlesource.com/c/chromium/src/+/900463
 
Cc: bsheedy@chromium.org
Labels: OS-Android
Owner: mthiesse@chromium.org
Status: Assigned (was: Available)
https://uberchromegw.corp.google.com/i/chromium.android/builders/Nougat%20Phone%20Tester?numbuilds=100

This has been failing since build #3231
https://uberchromegw.corp.google.com/i/chromium.android/builders/Nougat%20Phone%20Tester/builds/3231


Stack trace:

java.lang.AssertionError: Two navigations showed up in history expected:<2> but was:<1>
	at org.junit.Assert.fail(Assert.java:88)
	at org.junit.Assert.failNotEquals(Assert.java:834)
	at org.junit.Assert.assertEquals(Assert.java:645)
	at org.chromium.chrome.browser.vr_shell.VrShellNavigationTest.test2dTo2d(VrShellNavigationTest.java:150)
	at java.lang.reflect.Method.invoke(Native Method)
	at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
	at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
	at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:52)
	at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
	at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
	at org.chromium.base.test.ScreenshotOnFailureStatement.evaluate(ScreenshotOnFailureStatement.java:37)
	at org.chromium.chrome.browser.vr_shell.rules.ChromeTabbedActivityVrTestRule$1.evaluate(ChromeTabbedActivityVrTestRule.java:27)
	at org.chromium.chrome.test.ChromeActivityTestRule$1.evaluate(ChromeActivityTestRule.java:113)
	at android.support.test.internal.statement.UiThreadStatement.evaluate(UiThreadStatement.java:55)
	at android.support.test.rule.ActivityTestRule$ActivityStatement.evaluate(ActivityTestRule.java:270)
	at org.junit.rules.RunRules.evaluate(RunRules.java:20)
	at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325)
	at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78)
	at org.chromium.base.test.BaseJUnit4ClassRunner.runChild(BaseJUnit4ClassRunner.java:201)
	at org.chromium.base.test.BaseJUnit4ClassRunner.runChild(BaseJUnit4ClassRunner.java:43)
	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.chromium.base.test.BaseJUnit4ClassRunner.run(BaseJUnit4ClassRunner.java:183)
	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 android.support.test.internal.runner.TestExecutor.execute(TestExecutor.java:59)
	at android.support.test.runner.AndroidJUnitRunner.onStart(AndroidJUnitRunner.java:262)
	at org.chromium.base.test.BaseChromiumAndroidJUnitRunner.onStart(BaseChromiumAndroidJUnitRunner.java:99)
	at android.app.Instrumentation$InstrumentationThread.run(Instrumentation.java:1932)
Project Member

Comment 2 by bugdroid1@chromium.org, Feb 5 2018

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

commit 8ae23ed0f4d6235db8a6f32d0273dbc850969399
Author: bsheedy <bsheedy@chromium.org>
Date: Mon Feb 05 19:42:14 2018

Fix VR test failure due to missing file

Fixes the test that started failing again because the CL that added the
missing file got reverted.

Bug:  808977 
Change-Id: Ia82f4f6c5d5c21b709ef25b8556799a4544b6800
Reviewed-on: https://chromium-review.googlesource.com/902182
Reviewed-by: Michael Thiessen <mthiesse@chromium.org>
Commit-Queue: Brian Sheedy <bsheedy@chromium.org>
Cr-Commit-Position: refs/heads/master@{#534464}
[add] https://crrev.com/8ae23ed0f4d6235db8a6f32d0273dbc850969399/chrome/test/data/vr/e2e_test_files/html/test_navigation_2d_page2.html

Comment 3 by bengr@chromium.org, Feb 5 2018

Status: Started (was: Assigned)
Cc: -bsheedy@chromium.org
Owner: bsheedy@chromium.org
Status: Fixed (was: Started)

Sign in to add a comment