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

commit 9d41f4b2df16e0696d89091020d6716f0bc1418d
Author: Adithya Srinivasan <adithyas@chromium.org>
Date: Fri Nov 10 20:58:23 2017

Disable DeviceSensorBrowserTest.MotionOnlySomeSensorsAreAvailableTest

TBR=timvolodine

Bug:  783891 
Change-Id: Ie7e83b910f49f6730763783aa82f901d33563491
Reviewed-on: https://chromium-review.googlesource.com/764449
Reviewed-by: Adithya Srinivasan <adithyas@chromium.org>
Commit-Queue: Adithya Srinivasan <adithyas@chromium.org>
Cr-Commit-Position: refs/heads/master@{#515677}
[modify] https://crrev.com/9d41f4b2df16e0696d89091020d6716f0bc1418d/content/browser/device_sensors/device_sensor_browsertest.cc

Removing sheriff tag, I've disabled this test for now (it also caused failures in some other bots). 

timvolodine@: I'm assigning this to you since you're the directory owner. Could you please take a look at why this test is flaky or reassign this to someone else?

I couldn't reproduce this test failure on my local Linux machine. Talked to reillyg@ about this issue, we plan to add some logs to the html file that the browser test uses and see what causes the test to fail.

Since this test has already been disabled, can we change it to be a Pri-2 issue?

Set the NextAction date to see what data causes the test to be flaky.

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

commit 7205a0d557dce9a56444ba5660e302aeeaa18b55
Author: Jun Cai <juncai@chromium.org>
Date: Fri Jan 05 22:41:45 2018

Enable DeviceSensorBrowserTest.MotionOnlySomeSensorsAreAvailableTest

Since the flakiness of DeviceSensorBrowserTest.MotionOnlySomeSensorsAreAvailableTest
couldn't be reproduced on a local machine, this CL adds some log info
to it and enables the test for now. This can help debugging what causes
it to be flaky.

TBR=timvolodine@chromium.org

Bug:  783891 
Change-Id: Iab357ef0846ed8ac58b6a040bae7c8561e140886
Reviewed-on: https://chromium-review.googlesource.com/852805
Commit-Queue: Jun Cai <juncai@chromium.org>
Reviewed-by: Reilly Grant <reillyg@chromium.org>
Cr-Commit-Position: refs/heads/master@{#527413}
[modify] https://crrev.com/7205a0d557dce9a56444ba5660e302aeeaa18b55/content/browser/device_sensors/device_sensor_browsertest.cc
[modify] https://crrev.com/7205a0d557dce9a56444ba5660e302aeeaa18b55/content/test/data/device_sensors/device_motion_only_some_sensors_are_available_test.html

The NextAction date has arrived: 2018-01-12

From a recent failing run:

[ RUN      ] DeviceSensorBrowserTest.MotionOnlySomeSensorsAreAvailableTest
Xlib:  extension "RANDR" missing on display ":99".

DevTools listening on ws://127.0.0.1:56744/devtools/browser/bb465fdc-3714-4728-976d-47b137f562b9
Fontconfig warning: "/etc/fonts/fonts.conf", line 146: blank doesn't take any effect anymore. please remove it from your fonts.conf
[31256:31383:0109/041205.278514:WARNING:child_process_launcher_helper_posix.cc(118)] Ignoring invalid file v8_context_snapshot.bin
[31392:31392:0109/041205.706496:WARNING:gpu_info.cc(104)] No active GPU found, returning primary GPU.
[31256:31256:0109/041205.863354:INFO:CONSOLE(24)] "event.acceleration.x is: 0", source: file:///b/s/w/ir/content/test/data/device_sensors/device_motion_only_some_sensors_are_available_test.html (24)
[31256:31256:0109/041205.863640:INFO:CONSOLE(25)] "event.acceleration.y is: 0", source: file:///b/s/w/ir/content/test/data/device_sensors/device_motion_only_some_sensors_are_available_test.html (25)
[31256:31256:0109/041205.863892:INFO:CONSOLE(26)] "event.acceleration.z is: 0", source: file:///b/s/w/ir/content/test/data/device_sensors/device_motion_only_some_sensors_are_available_test.html (26)
[31256:31256:0109/041205.864130:INFO:CONSOLE(27)] "event.accelerationIncludingGravity.x is: null", source: file:///b/s/w/ir/content/test/data/device_sensors/device_motion_only_some_sensors_are_available_test.html (27)
[31256:31256:0109/041205.864369:INFO:CONSOLE(28)] "event.accelerationIncludingGravity.y is: null", source: file:///b/s/w/ir/content/test/data/device_sensors/device_motion_only_some_sensors_are_available_test.html (28)
[31256:31256:0109/041205.864606:INFO:CONSOLE(29)] "event.accelerationIncludingGravity.z is: null", source: file:///b/s/w/ir/content/test/data/device_sensors/device_motion_only_some_sensors_are_available_test.html (29)
[31256:31256:0109/041205.864833:INFO:CONSOLE(30)] "event.rotationRate.alpha is: 0", source: file:///b/s/w/ir/content/test/data/device_sensors/device_motion_only_some_sensors_are_available_test.html (30)
[31256:31256:0109/041205.865062:INFO:CONSOLE(31)] "event.rotationRate.beta is: 0", source: file:///b/s/w/ir/content/test/data/device_sensors/device_motion_only_some_sensors_are_available_test.html (31)
[31256:31256:0109/041205.865299:INFO:CONSOLE(32)] "event.rotationRate.gamma is: 0", source: file:///b/s/w/ir/content/test/data/device_sensors/device_motion_only_some_sensors_are_available_test.html (32)
[31256:31256:0109/041205.865535:INFO:CONSOLE(33)] "event.interval is: 16", source: file:///b/s/w/ir/content/test/data/device_sensors/device_motion_only_some_sensors_are_available_test.html (33)
../../content/browser/device_sensors/device_sensor_browsertest.cc:433: Failure
Expected equality of these values:
  "pass"
  shell()->web_contents()->GetLastCommittedURL().ref()
    Which is: "fail"
[  FAILED  ] DeviceSensorBrowserTest.MotionOnlySomeSensorsAreAvailableTest, where TypeParam =  and GetParam() =  (1384 ms)

This appears to be a duplicate of  issue 799043  which was recently resolved and according to the flakiness dashboard this is no longer occurring.