Yeah, we were already wondering about that. Before the builds starts, it has 160 GB of free disk space. Could the build really eat up all that?
We've had kernel crashing on the host side of the VM, and that has caused the VM to put its disks on read-only mode. That has then created errors that can't write on disk. That's different error message though. Just wondering if the error message this time is wrong, but from the same reason... -Tony -----Original Message----- From: Development <[email protected]> On Behalf Of Thiago Macieira Sent: keskiviikko 31. lokakuuta 2018 6.17 To: [email protected] Subject: [Development] CI machines out of disk space https://testresults.qt.io/logs/qt/qtbase/ 4d1c701336289c6c70c86b1bdea0324214a5687a/ LinuxUbuntu_18_04x86_64LinuxQEMUarmv7GCCqtci-linux-Ubuntu-18.04-x86_64- ea77a2DeveloperBuild_DisableTests/2a48a3b7dcb9652b1532a3ad14de7580b5b9b1ee/ build_1542285435/log.txt.gz agent:2018/10/31 03:51:26 build.go:193: {standard input}: Assembler messages: agent:2018/10/31 03:51:26 build.go:193: {standard input}: Fatal error: can't write 76 bytes to section .text of .obj/qgraphicssceneindex.o because: 'No space left on device' -- Thiago Macieira - thiago.macieira (AT) intel.com Software Architect - Intel Open Source Technology Center _______________________________________________ Development mailing list [email protected] http://lists.qt-project.org/mailman/listinfo/development _______________________________________________ Development mailing list [email protected] http://lists.qt-project.org/mailman/listinfo/development
