Closed
Bug 1484659
Opened 7 years ago
Closed 7 years ago
Manifest update doesn't handle VersionNumberMismatch
Categories
(Testing :: web-platform-tests, enhancement)
Tracking
(firefox63 fixed)
RESOLVED
FIXED
mozilla63
| Tracking | Status | |
|---|---|---|
| firefox63 | --- | fixed |
People
(Reporter: jgraham, Assigned: jgraham)
Details
Attachments
(1 file)
This breaks the build(!)
|
Assignee | |
Comment 1•7 years ago
|
||
If the wpt manifest format changes we bump the version number, causing
loading the old manifest to throw an error. We weren't correctly
handling this error when trying to update the manifest (by creating a
new empty manifest) so updates after the version number changed broke.
MozReview-Commit-ID: 4H1nMtRI9PZ
|
||
Comment 2•7 years ago
|
||
Comment on attachment 9002419 [details]
Bug 1484659 - Handle wpt version number changes, r=ato
Andreas Tolfsen ﹝:ato﹞ has approved the revision.
Attachment #9002419 -
Flags: review+
Pushed by james@hoppipolla.co.uk:
https://hg.mozilla.org/integration/autoland/rev/edaf8fd303bb
Handle wpt version number changes, r=ato
|
||
Comment 4•7 years ago
|
||
| bugherder | ||
Status: NEW → RESOLVED
Closed: 7 years ago
status-firefox63:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → mozilla63
|
||
Updated•7 years ago
|
Assignee: nobody → james
You need to log in
before you can comment on or make changes to this bug.
Description
•