Confirmed users
1,364
edits
Release:Release Automation on Mercurial:Troubleshooting: Difference between revisions
Release:Release Automation on Mercurial:Troubleshooting (view source)
Revision as of 02:59, 24 January 2014
, 24 January 2014added steps to back out release runner configs
(added steps to back out release runner configs) |
|||
| Line 7: | Line 7: | ||
If you're unable to resolve the issue on your own ask someone for help. Once you believe the issue has been resolved you need to mark the release as "ready" again on Ship It and restart the release runner process. This can be done with the following command on buildbot-master81 (as root): | If you're unable to resolve the issue on your own ask someone for help. Once you believe the issue has been resolved you need to mark the release as "ready" again on Ship It and restart the release runner process. This can be done with the following command on buildbot-master81 (as root): | ||
supervisorctl restart releaserunner | supervisorctl restart releaserunner | ||
The release might fail again, with an error similar to: | |||
subprocess.CalledProcessError: Command '['hg', 'commit', '-m', 'Update release config for Fennec-27.0b9-build1', '-u', 'ffxbld']' returned non-zero exit status 1 | |||
This is because the prior failure happened after the release configs were already updated. The solution is to: | |||
# revert the changes on both default & production branches of "<tt>buildbot-configs</tt>" | |||
# re-mark the releases as "ready" again, and hit "do eeet" | |||
==== "[release-runner] WARNING: Reconfig exceeded (time)" ==== | ==== "[release-runner] WARNING: Reconfig exceeded (time)" ==== | ||