Buildbot failure in Python on AMD64 Ubuntu Shared 3.x

The Buildbot has detected a failed build on builder AMD64 Ubuntu Shared 3.x while building python/cpython. Full details are available at: https://buildbot.python.org/all/#builders/506/builds/124
Buildbot URL: https://buildbot.python.org/all/
Worker for this Build: bolen-ubuntu
Build Reason: <unknown> Blamelist: Victor Stinner <vstinner@python.org>
BUILD FAILED: failed compile (failure)
Summary of the results of the build (if available):
Captured traceback
remote: Enumerating objects: 4, done.
remote: Counting objects: 25% (1/4)
remote: Counting objects: 50% (2/4)
remote: Counting objects: 75% (3/4)
remote: Counting objects: 100% (4/4)
remote: Counting objects: 100% (4/4), done.
remote: Total 4 (delta 3), reused 4 (delta 3), pack-reused 0
From https://github.com/python/cpython
- branch master -> FETCH_HEAD Reset branch 'master'
Parser/parser.c:24830:1: fatal error: error writing to /tmp/ccadKSXO.s: No space left on device } ^ compilation terminated. make: *** [Parser/parser.o] Error 1
find: ‘build’: No such file or directory find: ‘build’: No such file or directory find: ‘build’: No such file or directory find: ‘build’: No such file or directory make: [clean-retain-profile] Error 1 (ignored)
Test report
Sincerely, -The Buildbot

Hi David,
The disk of the buildbot worker bolen-ubuntu is full: https://buildbot.python.org/all/#/builders/506/builds/124
Would you mind having a look?
Did you read this email sent one month ago? https://mail.python.org/archives/list/python-buildbots@python.org/thread/SZR... "ACTION NEEDED: upgrade your buildbot client configuration"
=> especially "(...) You should also clean up manually the temporary directory (/tmp) to remove old "ccXXX" and "tmpXXX" files: rm -f /tmp/{cc,tmp}*"
And also this email:
"Cleaning up leftover directories that fill up the disk space of the buildbots" https://mail.python.org/archives/list/python-buildbots@python.org/thread/R4C...
=> Your buildbot worker client should use "delete_leftover_dirs = 1".
Victor
Le sam. 26 sept. 2020 à 12:50, <buildbot@python.org> a écrit :
-- Night gathers, and now my watch begins. It shall not end until my death.

Whoops, thanks for the heads up - it was user error. I neglected some clean-up after non-buildbot work last night and I didn't realize how tight the free space had gotten. Nothing to do with /tmp itself.
Should be corrected now.
-- David
On Sat, Sep 26, 2020 at 6:56 AM Victor Stinner <vstinner@python.org> wrote:

Hi David,
The disk of the buildbot worker bolen-ubuntu is full: https://buildbot.python.org/all/#/builders/506/builds/124
Would you mind having a look?
Did you read this email sent one month ago? https://mail.python.org/archives/list/python-buildbots@python.org/thread/SZR... "ACTION NEEDED: upgrade your buildbot client configuration"
=> especially "(...) You should also clean up manually the temporary directory (/tmp) to remove old "ccXXX" and "tmpXXX" files: rm -f /tmp/{cc,tmp}*"
And also this email:
"Cleaning up leftover directories that fill up the disk space of the buildbots" https://mail.python.org/archives/list/python-buildbots@python.org/thread/R4C...
=> Your buildbot worker client should use "delete_leftover_dirs = 1".
Victor
Le sam. 26 sept. 2020 à 12:50, <buildbot@python.org> a écrit :
-- Night gathers, and now my watch begins. It shall not end until my death.

Whoops, thanks for the heads up - it was user error. I neglected some clean-up after non-buildbot work last night and I didn't realize how tight the free space had gotten. Nothing to do with /tmp itself.
Should be corrected now.
-- David
On Sat, Sep 26, 2020 at 6:56 AM Victor Stinner <vstinner@python.org> wrote:
participants (3)
-
buildbot@python.org
-
David Bolen
-
Victor Stinner