Closed
Bug 1519174
Opened 5 years ago
Closed 5 years ago
Default to downloading latest manifest if no commits are found
Categories
(Testing :: web-platform-tests, enhancement)
Tracking
(firefox66 fixed)
RESOLVED
FIXED
mozilla66
| Tracking | Status | |
|---|---|---|
| firefox66 | --- | fixed |
People
(Reporter: jgraham, Assigned: jgraham)
References
Details
Attachments
(3 files)
Currently we default to generating the manifest if no wpt commits are found, which is almost certainly the wrong behaviour; instead default to downloading the latest manifest.
|
Assignee | |
Comment 1•5 years ago
|
||
This should help with diagnosing cases where we fail to download a manifest.
|
|
Assignee | |
Comment 2•5 years ago
|
||
Instead of defaulting to regenerating the manifest in this case default to downloading whatever the latest on central is. Depends on D16315
|
|
Assignee | |
Comment 3•5 years ago
|
||
This can happen if there's a problem writing the file. Depends on D16316
Pushed by james@hoppipolla.co.uk: https://hg.mozilla.org/integration/autoland/rev/c55708f47973 Add debug logging of which taskcluster URLs are being loaded, r=ato https://hg.mozilla.org/integration/autoland/rev/e37abec79d08 Default to downloading latest m-c manifest if no commits are found, r=ato https://hg.mozilla.org/integration/autoland/rev/0b0fc6359576 Download wpt manifest if existing file is empty, r=ato
|
||
Comment 5•5 years ago
|
||
| bugherder | ||
https://hg.mozilla.org/mozilla-central/rev/c55708f47973
https://hg.mozilla.org/mozilla-central/rev/e37abec79d08
https://hg.mozilla.org/mozilla-central/rev/0b0fc6359576
Status: NEW → RESOLVED
Closed: 5 years ago
status-firefox66:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → mozilla66
|
||
Updated•5 years ago
|
Assignee: nobody → james
You need to log in
before you can comment on or make changes to this bug.
Description
•