You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
... Here is a copy of the task status in JSON if that link disappears:
{
"status": "failure",
"jobs": {
"retrieve-resources": {
"status": "ok",
"errors": []
},
"specberus": {
"status": "ok",
"errors": []
},
"token-checker": {
"status": "ok",
"errors": []
},
"third-party-checker": {
"status": "ok",
"errors": []
},
"publish": {
"status": "failure",
"errors": [
{
"property_path": "editorDraft",
"message": "The editor draft URL is invalid."
}
]
},
"tr-install": {
"status": "",
"errors": []
},
"update-tr-shortlink": {
"status": "",
"errors": []
}
},
"history": [
{
"time": "2015-06-30T22:07:17.166Z",
"fact": "The file has been retrieved."
},
{
"time": "2015-06-30T22:07:18.560Z",
"fact": "The document passed specberus."
},
{
"time": "2015-06-30T22:07:19.203Z",
"fact": "The document passed the third party checker."
},
{
"time": "2015-06-30T22:07:19.514Z",
"fact": "The document could not be published: List [ \"The editor draft URL is invalid.\" ]"
}
],
"metadata": {
"previousVersion": "http://www.w3.org/TR/2015/WD-presentation-api-20150217/",
"deliverers": [
{
"homepage": "http://www.w3.org/2014/secondscreen/",
"name": "Second Screen Presentation\n Working Group"
}
],
"delivererIDs": [
74168
],
"docDate": "2015-06-30T00:00:00.000Z",
"editorIDs": [
68454,
63802
],
"process": "http://www.w3.org/2014/Process-20140801/",
"latestVersion": "http://www.w3.org/TR/presentation-api/",
"status": "WD",
"title": "Presentation API",
"thisVersion": "http://www.w3.org/TR/2015/WD-presentation-api-20150630/",
"editorsDraft": "http://w3c.github.io/presentation-api/ \n"
}
}
Note: the failure in that case was due to #201 and was easy to fix. This issue is really just about not receiving the failure notification on the mailing-list.
The text was updated successfully, but these errors were encountered:
Apparently, Echidna does not to send any email to the public-tr-notifications mailing-list when the
publish
job fails.An example of a job that was started at about
2015-06-30T22:07:17Z
:http://labs.w3.org/echidna/api/status?id=47b38647-30e3-4d7c-9193-ee25e1b0c983
... Here is a copy of the task status in JSON if that link disappears:
Note: the failure in that case was due to #201 and was easy to fix. This issue is really just about not receiving the failure notification on the mailing-list.
The text was updated successfully, but these errors were encountered: