Changes

Jump to: navigation, search

ReleaseEngineering/How To/VCSSync

526 bytes added, 23:45, 14 October 2013
Successful emails with messages
From: vcs2vcs@vcssync1.srv.releng.usw2.mozilla.com
Subject: [vcs2vcs] Successful conversion for beagle (72s)
 
 
Error log is non-zero!
 
02:16:08 ERROR - abort: HTTP Error 500: Internal Server Error
02:16:08 ERROR - Automation Error: hg not responding
02:16:08 ERROR - Return code: 65280
02:16:08 ERROR - Error getting changes for mozilla-inbound; skipping!
Summary is non-zero:
info - Successfully pushed mozilla-aurora.
error - Error getting changes for mozilla-inbound; skipping!
</pre>
Whenever the summary of a job is non-zero, or the error log is non-zero, we'll get a message body in the success email. This is usually a successful push notification, but can include the contents of the error log or any other information we put in the summary. (At some future point we may add l10n repo creation on git.m.o in here).
 
In this case, the ISE from hg.m.o is an intermittent issue. In general, the script should auto-fix by clobbering+recloning, and the conversion will happen later, though it'll be delayed by this action.
=== Failure emails ===
Confirm
4,971
edits

Navigation menu