New issue
Advanced search Search tips

Issue 693211 link

Starred by 1 user

Issue metadata

Status: Duplicate
Merged: issue 743149
Owner:
Closed: Aug 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Feature

Blocked on:
issue 689118

Blocking:
issue 707006



Sign in to add a comment

[WPT Export] Set up alerting for WPT Export

Project Member Reported by jeffcarp@chromium.org, Feb 16 2017

Issue description

If a WPT Export fails in the middle of a forest and there's nobody around to see the failure, does it still fail?

The answer as I've found out is yes. I usually find out the WPT Export is stuck either via:

1. An email from Travis CI
2. When I log into my workstation and check the logs

It would be great if I could get paged if the export process is stuck or fails due to a programming error on our end.
 

Comment 1 by foolip@chromium.org, Feb 17 2017

That would be great, yes. As we learn of typical causes of failure, we should also document how to unblock the export, for example that you might have to manually merge with Travis errors like with https://github.com/w3c/web-platform-tests/pull/4832, and a list of people who can do this.

I expect it's also just a matter of time until we have a case where the changes don't even apply and one would have to start from a patch file and create+merge a PR manually. When that happens we need documentation for how to create that patch file.
I created a new bug for writing the documentation you suggested, foolip:  bug 693821 
Cc: jeffcarp@chromium.org
 Issue 701046  has been merged into this issue.
Blocking: 707006
Components: Blink>Infra>Ecosystem
Components: -Blink>Infra>Predictability
Mergedinto: 743149
Status: Duplicate (was: Assigned)
Merging into  issue 743149  for turning the builder red when patch failures occur. Other alertable failures should also be caught by the Ecosystem rotation.

Sign in to add a comment