Closed
Bug 1752234
Opened 3 years ago
Closed 3 years ago
[wpt-sync] Sync PR 32563 - Update Safari Technology Preview to 139
Categories
(Testing :: web-platform-tests, task, P4)
Testing
web-platform-tests
Tracking
(firefox99 fixed)
RESOLVED
FIXED
99 Branch
Tracking | Status | |
---|---|---|
firefox99 | --- | fixed |
People
(Reporter: mozilla.org, Unassigned)
References
(Depends on 1 open bug, )
Details
(Whiteboard: [wptsync downstream])
Sync web-platform-tests PR 32563 into mozilla-central (this bug is closed when the sync is complete).
PR: https://github.com/web-platform-tests/wpt/pull/32563
Details from upstream follow.
autofoolip <auto@foolip.org> wrote:
Update Safari Technology Preview to 139
Version as reported by safaridriver --version:
Included with Safari Technology Preview (Release 139, 16613.1.14.41.2)Source: https://developer.apple.com/safari/download/
Build: https://dev.azure.com/foolip/safari-technology-preview-updater/_build/results?buildId=4097&view=logs
Assignee | ||
Comment 1•3 years ago
|
||
PR 32563 applied with additional changes from upstream: 36b66d8ef6e7435f38c4ebbd1ae8da3b1750f0b2
Assignee | ||
Updated•3 years ago
|
Status: NEW → RESOLVED
Closed: 3 years ago
Resolution: --- → INVALID
Assignee | ||
Updated•3 years ago
|
Status: RESOLVED → REOPENED
Resolution: INVALID → ---
Assignee | ||
Comment 2•3 years ago
|
||
Pushed by wptsync@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/ddcecca73241
[wpt PR 32563] - Update Safari Technology Preview to 139, a=testonly
Assignee | ||
Comment 4•3 years ago
|
||
Test result changes from PR not available.
Pushed by wptsync@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/3c52f3dd5d0d
[wpt PR 32563] - Update Safari Technology Preview to 139, a=testonly
Assignee | ||
Comment 6•3 years ago
|
||
Test result changes from PR not available.
Comment 7•3 years ago
|
||
bugherder |
Status: REOPENED → RESOLVED
Closed: 3 years ago → 3 years ago
status-firefox99:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → 99 Branch
You need to log in
before you can comment on or make changes to this bug.
Description
•