out of disk space not handled well (ambiguous error, no way to recover or retry)



a year ago
a year ago


(Reporter: glacrugho, Unassigned)


Firefox Tracking Flags

(Not tracked)




a year ago
Reference excerpt from mozregression output, below. This gives the impression that the problem is that the build is broken, but in fact it turns out /tmp was out of space. The error message should indicate the lack of disk space as the problem.

Also, this error will continue to occur for each build it downloads from this point, until e.g. user reboots (which clears /tmp), or the user manually deletes files from /tmp (which they likely don't realize is the real problem). The script should offer a way to recover, such as by deleting other builds from /tmp or installing to another location.

Finally, since the script (incorrectly) presumes the build is broken, it removes it from the builds which can be tested (it doesn't let you retry). when the failure is due to running out of disk space, the user should have the opportunity to retry for the applicable build.

===== Downloaded 100% =====
27:38.73 INFO: Running mozilla-inbound build built on 2016-05-17 20:24:45.635000, revision 3de4044b
27:53.73 ERROR: Unable to install '/tmp/tmprPUW0i/3de4044b57f4--mozilla-inbound--firefox-49.0a1.en-US.linux-x86_64.tar.bz2'
27:53.75 INFO: Error: Unable to install '/tmp/tmprPUW0i/3de4044b57f4--mozilla-inbound--firefox-49.0a1.en-US.linux-x86_64.tar.bz2'. Skipping this build...
28:01.10 INFO: Pushlog:

Build was skipped. You can manually choose a new build to test, to be able to get out of a broken build range.
Please type the index of the build you would like to try - the index is 0-based on the middle of the remaining build range.
You can choose a build index between [-4, 3]
You need to log in before you can comment on or make changes to this bug.