Closed
Bug 1527276
Opened 7 years ago
Closed 7 years ago
[wpt-sync] Sync PR 15307 - [PE] Avoid crash about unaliased status when skipping fragment clips
Categories
(Testing :: web-platform-tests, enhancement, P4)
Testing
web-platform-tests
Tracking
(firefox67 fixed)
RESOLVED
FIXED
mozilla67
| Tracking | Status | |
|---|---|---|
| firefox67 | --- | fixed |
People
(Reporter: wpt-sync, Unassigned)
References
()
Details
(Whiteboard: [wptsync downstream])
Sync web-platform-tests PR 15307 into mozilla-central (this bug is closed when the sync is complete).
PR: https://github.com/web-platform-tests/wpt/pull/15307
Details from upstream follow.
Xianzhu Wang <wangxianzhu@chromium.org> wrote:
[PE] Avoid crash about unaliased status when skipping fragment clips
Bug: 929979
Change-Id: I2bd0c2c8088fc1af328db5f7162c5c1c7092c23e
Reviewed-on: https://chromium-review.googlesource.com/c/1461098
Commit-Queue: Xianzhu Wang \<wangxianzhu@chromium.org>
Reviewed-by: vmpstr \<vmpstr@chromium.org>
Cr-Commit-Position: refs/heads/master@{#630980}
| Assignee | ||
Updated•7 years ago
|
Whiteboard: [wptsync downstream] → [wptsync downstream error]
| Assignee | ||
Updated•7 years ago
|
Whiteboard: [wptsync downstream error] → [wptsync downstream]
| Assignee | ||
Comment 1•7 years ago
|
||
| Assignee | ||
Comment 2•7 years ago
|
||
The PR was not expected to affect any tests, but the try push wasn't a success. Check the try results for infrastructure issues
Pushed by wptsync@mozilla.com:
https://hg.mozilla.org/integration/mozilla-inbound/rev/9128147cb4f1
[wpt PR 15307] - [PE] Avoid crash about unaliased status when skipping fragment clips, a=testonly
Pushed by james@hoppipolla.co.uk:
https://hg.mozilla.org/integration/mozilla-inbound/rev/84f85cd8729e
[wpt PR 15307] - [PE] Avoid crash about unaliased status when skipping fragment clips, a=testonly
Comment 5•7 years ago
|
||
| bugherder | ||
Status: NEW → RESOLVED
Closed: 7 years ago
status-firefox67:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → mozilla67
You need to log in
before you can comment on or make changes to this bug.
Description
•