Closed Bug 1638391 Opened 5 years ago Closed 5 years ago

[wpt-sync] Sync PR 23639 - Mark AmbientLightSensor.https.html as a slow test.

Categories

(Core :: DOM: Device Interfaces, task, P4)

task

Tracking

()

RESOLVED FIXED
mozilla78
Tracking Status
firefox78 --- fixed

People

(Reporter: wpt-sync, Unassigned)

References

()

Details

(Whiteboard: [wptsync downstream])

Sync web-platform-tests PR 23639 into mozilla-central (this bug is closed when the sync is complete).

PR: https://github.com/web-platform-tests/wpt/pull/23639
Details from upstream follow.

Raphael Kubo da Costa <raphael.kubo.da.costa@intel.com> wrote:

Mark AmbientLightSensor.https.html as a slow test.

ALS and Magnetometer have a maximum frequency of 10Hz, which can cause the
Generic Sensors test suite to take longer than normal to run.

Add the \<meta> tag with the annotation to AmbientLightSensor.https.html, as
Magnetometer.https.html already has it.

Bug: 731018
Change-Id: Ia437fb2907c0e52caa281c8e709c1d48ca59873f
Reviewed-on: https://chromium-review.googlesource.com/2203071
WPT-Export-Revision: 958c003297ffb3c2074dc2d4c097e7f3d25bbaf2

Component: web-platform-tests → DOM: Device Interfaces
Product: Testing → Core

CI Results

Ran 0 Firefox configurations based on mozilla-central, and Firefox, Chrome, and Safari on GitHub CI

Total 1 tests and 20 subtests

Status Summary

Firefox

OK : 1
FAIL: 20

Chrome

OK : 1
PASS: 1
FAIL: 19

Safari

OK : 1
FAIL: 20

Links

GitHub PR Head
GitHub PR Base

Details

New Tests That Don't Pass

/ambient-light/AmbientLightSensor.https.html
AmbientLightSensor: Test that frequency is capped to the maximum supported frequency.: FAIL (Chrome: FAIL, Safari: FAIL)
AmbientLightSensor: sensor.stop() returns undefined.: FAIL (Chrome: FAIL, Safari: FAIL)
AmbientLightSensor: Test that onerror is send when start() call has failed.: FAIL (Chrome: FAIL, Safari: FAIL)
AmbientLightSensor: Test that frequency is capped to allowed maximum.: FAIL (Chrome: FAIL, Safari: FAIL)
AmbientLightSensor: Test that frequency is limited to the minimum supported frequency.: FAIL (Chrome: FAIL, Safari: FAIL)
AmbientLightSensor: sensor reading is correct.: FAIL (Chrome: FAIL, Safari: FAIL)
AmbientLightSensor: Test that sensor can be successfully created and its states are correct.: FAIL (Chrome: FAIL, Safari: FAIL)
AmbientLightSensor: sensor.start() returns undefined.: FAIL (Chrome: FAIL, Safari: FAIL)
AmbientLightSensor: throw 'TypeError' if frequency is invalid.: FAIL (Chrome: PASS, Safari: FAIL)
AmbientLightSensor: Test that sensor cannot be constructed within iframe disallowed to use feature policy.: FAIL (Chrome: FAIL, Safari: FAIL)
AmbientLightSensor: frequency hint works.: FAIL (Chrome: FAIL, Safari: FAIL)
AmbientLightSensor: Test that onerror is sent when permissions are not granted.: FAIL (Chrome: FAIL, Safari: FAIL)
AmbientLightSensor: no exception is thrown when calling stop() on already stopped sensor.: FAIL (Chrome: FAIL, Safari: FAIL)
AmbientLightSensor: Test that 'onreading' is called and sensor reading is valid.: FAIL (Chrome: FAIL, Safari: FAIL)
AmbientLightSensor: sensor timestamp is updated when time passes.: FAIL (Chrome: FAIL, Safari: FAIL)
AmbientLightSensor: Test that fresh reading is fetched on start().: FAIL (Chrome: FAIL, Safari: FAIL)
AmbientLightSensor: Test that sensor can be constructed within an iframe allowed to use feature policy.: FAIL (Chrome: FAIL, Safari: FAIL)
AmbientLightSensor: sensor receives suspend / resume notifications when cross-origin subframe is focused.: FAIL (Chrome: FAIL, Safari: FAIL)
AmbientLightSensor: no exception is thrown when calling start() on already started sensor.: FAIL (Chrome: FAIL, Safari: FAIL)
AmbientLightSensor: Test that onerror is sent when sensor is not supported.: FAIL (Chrome: FAIL, Safari: FAIL)

Severity: -- → S4
Pushed by wptsync@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/9f61afeb8239 [wpt PR 23639] - Mark AmbientLightSensor.https.html as a slow test., a=testonly
Status: NEW → RESOLVED
Closed: 5 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla78
You need to log in before you can comment on or make changes to this bug.