Closed Bug 1568264 Opened 5 years ago Closed 5 years ago

[wpt-sync] Sync PR 18004 - Fix WebGLLayer test expectations

Categories

(Testing :: web-platform-tests, task, P4)

Product:
Testing
Component:
web-platform-tests
Type:
task

Tracking

(firefox70 fixed)

Status:
RESOLVED FIXED
Milestone:
mozilla70
Tracking Flags:
Tracking Status
firefox70 --- fixed

People

(Reporter: mozilla.org, Unassigned)

References

(
URL
)

Details

(Whiteboard: [wptsync downstream])

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

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

Alex Cooper <alcooper@chromium.org> wrote:

Fix WebGLLayer test expectations

The xrWebGLLayer tests didn't have their expectations wrapped in t.step
so their failures were reported as timeouts, rather than the actual
error.

xrWebGLLayer_viewports expected the device init viewport to match the
output viewport, which is not a specced behavior, and contradicts the
webxr-test-api spec which calls this out as unsupported, so that part
has also been reverted.

Bug:986672
Change-Id: I23713956f6b0bd3d432f0e6e6fdc9d015d509099
Reviewed-on: https://chromium-review.googlesource.com/1715237
WPT-Export-Revision: 88b131ef810a1d511a50dde7c46eacbc83993a1d

Whiteboard: [wptsync downstream] → [wptsync downstream error]
PR 18004 applied with additional changes from upstream: cecaf876966eea0694dd28b72940e5b8feff5c1b
Whiteboard: [wptsync downstream error] → [wptsync downstream]
Ran 2 tests and 4[linux32-shippable-opt,linux64-asan-opt,linux64-debug,linux64-opt,linux64-qr-debug,linux64-qr-opt,linux64-shippable-opt,linux64-shippable-qr-opt,windows10-64-debug,windows10-64-opt,windows10-64-qr-debug,windows10-64-qr-opt,windows10-64-shippable-opt,windows10-64-shippable-qr-opt,windows7-32-debug,windows7-32-opt,windows7-32-shippable-opt] subtests
OK     : 2[linux32-shippable-opt,linux64-asan-opt,linux64-debug,linux64-opt,linux64-qr-debug,linux64-qr-opt,linux64-shippable-opt,linux64-shippable-qr-opt,windows10-64-debug,windows10-64-opt,windows10-64-qr-debug,windows10-64-qr-opt,windows10-64-shippable-opt,windows10-64-shippable-qr-opt,windows7-32-debug,windows7-32-opt,windows7-32-shippable-opt]
FAIL   : 4[linux32-shippable-opt,linux64-asan-opt,linux64-debug,linux64-opt,linux64-qr-debug,linux64-qr-opt,linux64-shippable-opt,linux64-shippable-qr-opt,windows10-64-debug,windows10-64-opt,windows10-64-qr-debug,windows10-64-qr-opt,windows10-64-shippable-opt,windows10-64-shippable-qr-opt,windows7-32-debug,windows7-32-opt,windows7-32-shippable-opt]

New tests that have failures or other problems:
/webxr/xrWebGLLayer_framebuffer.https.html: SKIP[android-em-7.0-x86_64-debug,android-em-7.0-x86_64-opt]
    XRWebGLLayer reports a valid framebuffer for immersive sessions: FAIL[linux32-shippable-opt,linux64-asan-opt,linux64-debug,linux64-opt,linux64-qr-debug,linux64-qr-opt,linux64-shippable-opt,linux64-shippable-qr-opt,windows10-64-debug,windows10-64-opt,windows10-64-qr-debug,windows10-64-qr-opt,windows10-64-shippable-opt,windows10-64-shippable-qr-opt,windows7-32-debug,windows7-32-opt,windows7-32-shippable-opt]
    XRWebGLLayer reports a valid framebuffer for inline sessions: FAIL[linux32-shippable-opt,linux64-asan-opt,linux64-debug,linux64-opt,linux64-qr-debug,linux64-qr-opt,linux64-shippable-opt,linux64-shippable-qr-opt,windows10-64-debug,windows10-64-opt,windows10-64-qr-debug,windows10-64-qr-opt,windows10-64-shippable-opt,windows10-64-shippable-qr-opt,windows7-32-debug,windows7-32-opt,windows7-32-shippable-opt]

Tests that are disabled for instability:
/webxr/xrWebGLLayer_viewports.https.html: [android-em-7.0-x86_64-debug,android-em-7.0-x86_64-opt]
Pushed by wptsync@mozilla.com:
https://hg.mozilla.org/integration/mozilla-inbound/rev/2b502bcd6d26
[wpt PR 18004] - Fix WebGLLayer test expectations, a=testonly
https://hg.mozilla.org/integration/mozilla-inbound/rev/c5953fb3afe4
[wpt PR 18004] - Update wpt metadata, a=testonly

https://hg.mozilla.org/mozilla-central/rev/2b502bcd6d26
https://hg.mozilla.org/mozilla-central/rev/c5953fb3afe4

Status: NEW → RESOLVED
Closed: 5 years ago
status-firefox70: --- → fixed
Resolution: --- → FIXED
Target Milestone: --- → mozilla70
You need to log in before you can comment on or make changes to this bug.