Closed
Bug 1485476
Opened 6 years ago
Closed 6 years ago
[wpt-sync] Sync PR 12629 - Reland "Move XR LayoutTests over to be WPTs"
Categories
(Testing :: web-platform-tests, enhancement, P4)
Testing
web-platform-tests
Tracking
(firefox63 fixed)
RESOLVED
FIXED
mozilla63
Tracking | Status | |
---|---|---|
firefox63 | --- | fixed |
People
(Reporter: wpt-sync, Unassigned)
References
()
Details
(Whiteboard: [wptsync downstream])
Sync web-platform-tests PR 12629 into mozilla-central (this bug is closed when the sync is complete).
PR: https://github.com/web-platform-tests/wpt/pull/12629
Details from upstream follow.
Anna Offenwanger <offenwanger@chromium.org> wrote:
> Reland "Move XR LayoutTests over to be WPTs"
>
> This is a reland of f4c510e1cb2ccdc0ce07b060be9ad52f8eda5cb8
>
> Original change's description:
> > Move XR LayoutTests over to be WPTs
> >
> > Moving as many of the WebXR LayoutTests as possible over to be
> > WebPlatformTests. All the tests that have been moved test some
> > aspect of the spec (https://immersive-web.github.io/webxr/) in
> > a platform agnostic way.
> >
> > Bug: 863557, 844772
> > Change-Id: I203b4c59be0daa0ca624fb0281fc33035f1be8a1
> > Reviewed-on: https://chromium-review.googlesource.com/1171857
> > Reviewed-by: Brandon Jones <bajones@chromium.org>
> > Reviewed-by: Brian Sheedy <bsheedy@chromium.org>
> > Commit-Queue: Anna Offenwanger <offenwanger@chromium.org>
> > Cr-Commit-Position: refs/heads/master@{#585064}
>
> Bug: 863557, 844772
> Change-Id: I2a85e45018fc0a17fe91c3d7bddd89587a2617e0
>
> Reviewed-on: https://chromium-review.googlesource.com/1185384
> WPT-Export-Revision: d5edab4524596149fe6b9c780d926184bd8a115c
Assignee | ||
Comment 1•6 years ago
|
||
Assignee | ||
Updated•6 years ago
|
Whiteboard: [wptsync downstream] → [wptsync downstream error]
Assignee | ||
Updated•6 years ago
|
Whiteboard: [wptsync downstream error] → [wptsync downstream]
Assignee | ||
Updated•6 years ago
|
Whiteboard: [wptsync downstream] → [wptsync downstream error]
Assignee | ||
Updated•6 years ago
|
Whiteboard: [wptsync downstream error] → [wptsync downstream]
Assignee | ||
Updated•6 years ago
|
Whiteboard: [wptsync downstream] → [wptsync downstream error]
Assignee | ||
Updated•6 years ago
|
Whiteboard: [wptsync downstream error] → [wptsync downstream]
Assignee | ||
Comment 2•6 years ago
|
||
Assignee | ||
Comment 3•6 years ago
|
||
Pushed to try (stability) https://treeherder.mozilla.org/#/jobs?repo=try&revision=fad2e6747f4d2583ae073df4f076b2358242c841
Assignee | ||
Comment 4•6 years ago
|
||
Ran 21 tests and 28 subtests
OK : 21
PASS : 2
FAIL : 26
New tests that have failures or other problems:
/webxr/navigator_xr_requestDevice.https.html
navigator.xr.requestDevice returns a device: FAIL
/webxr/navigator_xr_requestDevice_no_device.https.html
navigator.xr.requestDevice properly rejects when there are 0 devices: FAIL
/webxr/webGLCanvasContext_create_with_xrdevice.https.html
webglCanvasContext can be created with an XRDevice: FAIL
/webxr/webGLCanvasContext_setdevice_contextlost.https.html
A lost webglCanvasContext should not be able to set device: FAIL
/webxr/xrDevice_requestSession_immersive.https.html
Tests requestSession resolves when supported: FAIL
/webxr/xrDevice_requestSession_immersive_no_gesture.https.html
Requesting immersive session outside of a user gesture rejects: FAIL
/webxr/xrDevice_requestSession_immersive_unsupported.https.html
Requesting an immersive session when unsupported rejects: FAIL
/webxr/xrDevice_requestSession_non_immersive_no_gesture.https.html
Requesting non-immersive session outside of a user gesture succeeds: FAIL
/webxr/xrDevice_supportsSession_immersive.https.html
supportsSession resolves when immersive options supported: FAIL
/webxr/xrDevice_supportsSession_immersive_unsupported.https.html
supportsSession rejects when options not supported: FAIL
/webxr/xrDevice_supportsSession_non_immersive.https.html
supportsSession resolves when non-immersive options supported: FAIL
/webxr/xrSession_cancelAnimationFrame.https.html
XRSession requestAnimationFrame callbacks can be unregistered with cancelAnimationFrame for immersive sessions: FAIL
XRSession requestAnimationFrame callbacks can be unregistered with cancelAnimationFrame for non-immersive sessions: FAIL
/webxr/xrSession_cancelAnimationFrame_invalidhandle.https.html
XRSession cancelAnimationFrame does not have unexpected behavior when given invalid handles on immersive testSession: FAIL
XRSession cancelAnimationFrame does not have unexpected behavior when given invalid handles on non-immersive testSession: FAIL
/webxr/xrSession_device.https.html
Requested session has device set: FAIL
/webxr/xrSession_end.https.html
end event fires when immersive session ends: FAIL
end event fires when non-immersive session ends: FAIL
/webxr/xrSession_prevent_multiple_exclusive.https.html
Test prevention of multiple simultaneous immersive sessions: FAIL
/webxr/xrSession_requestAnimationFrame_callback_calls.https.html
XRSession requestAnimationFrame calls the provided callback a non-immersive session: FAIL
XRSession requestAnimationFrame calls the provided callback for an immersive session: FAIL
/webxr/xrSession_requestAnimationFrame_data_valid.https.html
RequestAnimationFrame resolves with good data: FAIL
/webxr/xrSession_requestAnimationFrame_getDevicePose.https.html
XRFrame getDevicePose updates on the next frame for immersive sessions: FAIL
XRFrame getDevicePose updates on the next frame for non-immersive sessions: FAIL
/webxr/xrSession_requestFrameOfReference.https.html
Immersive XRSession requestFrameOfReference returns expected objects: FAIL
Non-immersive XRSession requestFrameOfReference returns expected objects: FAIL
Pushed by wptsync@mozilla.com:
https://hg.mozilla.org/integration/mozilla-inbound/rev/81368bd086e6
[wpt PR 12629] - Reland "Move XR LayoutTests over to be WPTs", a=testonly
https://hg.mozilla.org/integration/mozilla-inbound/rev/68480db895db
[wpt PR 12629] - Update wpt metadata, a=testonly
Comment 6•6 years ago
|
||
bugherder |
https://hg.mozilla.org/mozilla-central/rev/81368bd086e6
https://hg.mozilla.org/mozilla-central/rev/68480db895db
Status: NEW → RESOLVED
Closed: 6 years ago
status-firefox63:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → mozilla63
You need to log in
before you can comment on or make changes to this bug.
Description
•