Release:Release Automation on Mercurial:Troubleshooting: Difference between revisions

Release:Release Automation on Mercurial:Troubleshooting (view source)

567 bytes removed , 28 April 2020

Confirmed users

3,104

edits

@@ Line 2: / Line 2: @@
 === Paperwork ===
 Some releases require creation of build notes when failures occur, others should already have a page created at release start - [[Release:Release_Automation_on_Mercurial:Starting_a_Release#Paperwork | requirements]]. Either way, document all problems and their solutions.
-=== Addressing Disk Space Issues ===
-Each builder should ensure adequate disk space before starting a job, so this "shouldn't happen" unless the build's needs have grown. In that case, the logs will not give a good clue, and the job will be retried. Clean space on the build slave by deleting older builds, AND file a bug to have the configs fixed. (No, you can't just run purge_builds.py -- at least until {{bug|712205|we have local "tools" checkouts}})
-You can confirm disk space is the issue via browsing [https://graphite-scl3.mozilla.org/dashboard/ graphite].
 === Restarting failed builders without patching the config ===