New issue
Advanced search Search tips

Issue 689253 link

Starred by 1 user

Issue metadata

Status: Archived
Owner: ----
Closed: Apr 2017
Components:
EstimatedDays: ----
NextAction: ----
OS: Android
Pri: 3
Type: Bug



Sign in to add a comment

GamepadProviderTest.PollingAccess failed

Project Member Reported by joedow@chromium.org, Feb 6 2017

Issue description

So far I've seen this error once on the Android builder and it cleared up the next run:
https://uberchromegw.corp.google.com/i/chromium.linux/builders/Android%20Tests/builds/37871

I wanted to file a tracking bug in case this is an infrequent flake.

The debug output for the failure is:
I   18.077s run_tests_on_device(01ab75200c375e69)  [ RUN      ] GamepadProviderTest.PollingAccess
I   18.077s run_tests_on_device(01ab75200c375e69)  ../../device/gamepad/gamepad_provider_unittest.cc:105: Failure
I   18.077s run_tests_on_device(01ab75200c375e69)  Value of: output.items[0].buttonsLength
I   18.078s run_tests_on_device(01ab75200c375e69)    Actual: 0
I   18.078s run_tests_on_device(01ab75200c375e69)  Expected: 1u
I   18.078s run_tests_on_device(01ab75200c375e69)  Which is: 1
I   18.078s run_tests_on_device(01ab75200c375e69)  ../../device/gamepad/gamepad_provider_unittest.cc:106: Failure
I   18.078s run_tests_on_device(01ab75200c375e69)  Value of: output.items[0].buttons[0].value
I   18.078s run_tests_on_device(01ab75200c375e69)    Actual: 0
I   18.078s run_tests_on_device(01ab75200c375e69)  Expected: 1.f
I   18.078s run_tests_on_device(01ab75200c375e69)  Which is: 1
I   18.078s run_tests_on_device(01ab75200c375e69)  ../../device/gamepad/gamepad_provider_unittest.cc:107: Failure
I   18.078s run_tests_on_device(01ab75200c375e69)  Value of: output.items[0].buttons[0].pressed
I   18.078s run_tests_on_device(01ab75200c375e69)    Actual: false
I   18.078s run_tests_on_device(01ab75200c375e69)  Expected: true
I   18.078s run_tests_on_device(01ab75200c375e69)  ../../device/gamepad/gamepad_provider_unittest.cc:108: Failure
I   18.078s run_tests_on_device(01ab75200c375e69)  Value of: output.items[0].axesLength
I   18.078s run_tests_on_device(01ab75200c375e69)    Actual: 0
I   18.078s run_tests_on_device(01ab75200c375e69)  Expected: 2u
I   18.078s run_tests_on_device(01ab75200c375e69)  Which is: 2
I   18.078s run_tests_on_device(01ab75200c375e69)  ../../device/gamepad/gamepad_provider_unittest.cc:109: Failure
I   18.078s run_tests_on_device(01ab75200c375e69)  Value of: output.items[0].axes[0]
I   18.078s run_tests_on_device(01ab75200c375e69)    Actual: 0
I   18.078s run_tests_on_device(01ab75200c375e69)  Expected: -1.f
I   18.078s run_tests_on_device(01ab75200c375e69)  Which is: -1
I   18.078s run_tests_on_device(01ab75200c375e69)  ../../device/gamepad/gamepad_provider_unittest.cc:110: Failure
I   18.078s run_tests_on_device(01ab75200c375e69)  Value of: output.items[0].axes[1]
I   18.078s run_tests_on_device(01ab75200c375e69)    Actual: 0
I   18.078s run_tests_on_device(01ab75200c375e69)  Expected: 0.5f
I   18.078s run_tests_on_device(01ab75200c375e69)  Which is: 0.5
I   18.079s run_tests_on_device(01ab75200c375e69)  [  FAILED  ] GamepadProviderTest.PollingAccess (19 ms)
I   18.079s run_tests_on_device(01ab75200c375e69)  [----------] 1 test from GamepadProviderTest (19 ms total)
 
I did not see any CLs which might have caused this problem and the last change I see to any of the files occurred several weeks ago.
Status: Archived (was: Untriaged)
Closing this since we haven't seen any more failures since February. Please reopen if you see it again.

Sign in to add a comment