I've been having trouble getting deno to build since v1.9.0 (April 13th, 2021) on x86_64. Tried various _constraints values, but the job is failing with the same error: [ 3311s] LLVM ERROR: IO failure on output stream: No space left on device [ 3311s] /.build/build-vm: line 460: echo: write error: No space left on device [ 3312s] error: could not compile `deno` [ 3312s] https://build.opensuse.org/package/show/devel:languages:javascript/deno#comm... Can anyone advise? Thanks, avindra goolcharan
On Freitag, 14. Mai 2021, 04:35:33 CEST Avindra G wrote:
I've been having trouble getting deno to build since v1.9.0 (April 13th, 2021) on x86_64.
Tried various _constraints values, but the job is failing with the same error:
[ 3311s] LLVM ERROR: IO failure on output stream: No space left on device [ 3311s] /.build/build-vm: line 460: echo: write error: No space left on device [ 3312s] error: could not compile `deno` [ 3312s]
https://build.opensuse.org/package/show/devel:languages:javascript/deno#comm...
Can anyone advise?
it is still an error from inside of the VM. You require 16GB and the worker provides 24GB disk space. It still seems not to be enough for this build job. I would try a local build and check what it needs. There might be also some endless loop which would require infinite amount of disk space.... -- Adrian Schroeter <adrian@suse.de> Build Infrastructure Project Manager SUSE Software Solutions Germany GmbH, Maxfeldstr. 5, 90409 Nuernberg, Germany (HRB 247165, AG München), Geschäftsführer: Felix Imendörffer
Thanks for the suggestion. Is there an idiomatic way to check how much disk space a local build uses? For the record, it appears the problems with the VM have been resolved (builds on x86_64 working again). I'll go in and clean up the _constraints for deno at some point. Regards, avindra goolcharan On Fri, May 14, 2021 at 1:44 AM Adrian Schröter <adrian@suse.de> wrote:
On Freitag, 14. Mai 2021, 04:35:33 CEST Avindra G wrote:
I've been having trouble getting deno to build since v1.9.0 (April 13th, 2021) on x86_64.
Tried various _constraints values, but the job is failing with the same error:
[ 3311s] LLVM ERROR: IO failure on output stream: No space left on device [ 3311s] /.build/build-vm: line 460: echo: write error: No space left on device [ 3312s] error: could not compile `deno` [ 3312s]
https://build.opensuse.org/package/show/devel:languages:javascript/deno#comm...
Can anyone advise?
it is still an error from inside of the VM.
You require 16GB and the worker provides 24GB disk space. It still seems not to be enough for this build job.
I would try a local build and check what it needs. There might be also some endless loop which would require infinite amount of disk space....
--
Adrian Schroeter <adrian@suse.de> Build Infrastructure Project Manager
SUSE Software Solutions Germany GmbH, Maxfeldstr. 5, 90409 Nuernberg, Germany (HRB 247165, AG München), Geschäftsführer: Felix Imendörffer
On Montag, 17. Mai 2021, 22:43:53 CEST Avindra G wrote:
Thanks for the suggestion. Is there an idiomatic way to check how much disk space a local build uses?
For the record, it appears the problems with the VM have been resolved (builds on x86_64 working again).
I'll go in and clean up the _constraints for deno at some point.
Each successful build writes a _statistics file as part of the build result. You find the maximal used storage disk space inside. bye adrian
avindra goolcharan
On Fri, May 14, 2021 at 1:44 AM Adrian Schröter <adrian@suse.de> wrote:
On Freitag, 14. Mai 2021, 04:35:33 CEST Avindra G wrote:
I've been having trouble getting deno to build since v1.9.0 (April 13th, 2021) on x86_64.
Tried various _constraints values, but the job is failing with the same error:
[ 3311s] LLVM ERROR: IO failure on output stream: No space left on device [ 3311s] /.build/build-vm: line 460: echo: write error: No space left on device [ 3312s] error: could not compile `deno` [ 3312s]
https://build.opensuse.org/package/show/devel:languages:javascript/deno#comm...
Can anyone advise?
it is still an error from inside of the VM.
You require 16GB and the worker provides 24GB disk space. It still seems not to be enough for this build job.
I would try a local build and check what it needs. There might be also some endless loop which would require infinite amount of disk space....
--
Adrian Schroeter <adrian@suse.de> Build Infrastructure Project Manager
SUSE Software Solutions Germany GmbH, Maxfeldstr. 5, 90409 Nuernberg, Germany (HRB 247165, AG München), Geschäftsführer: Felix Imendörffer
-- Adrian Schroeter <adrian@suse.de> Build Infrastructure Project Manager SUSE Software Solutions Germany GmbH, Maxfeldstr. 5, 90409 Nuernberg, Germany (HRB 247165, AG München), Geschäftsführer: Felix Imendörffer
Running into this issue again with x86_64 builds of deno. The last successful build was 1.11.5. Note that the aarch64 is building 1.13.0 successfully. https://build.opensuse.org/package/show/devel:languages:javascript/deno Is there something needing cleaning in the backend? avindra goolcharan On Tue, May 18, 2021 at 2:01 AM Adrian Schröter <adrian@suse.de> wrote:
On Montag, 17. Mai 2021, 22:43:53 CEST Avindra G wrote:
Thanks for the suggestion. Is there an idiomatic way to check how much disk space a local build uses?
For the record, it appears the problems with the VM have been resolved (builds on x86_64 working again).
I'll go in and clean up the _constraints for deno at some point.
Each successful build writes a _statistics file as part of the build result.
You find the maximal used storage disk space inside.
bye adrian
avindra goolcharan
On Fri, May 14, 2021 at 1:44 AM Adrian Schröter <adrian@suse.de> wrote:
On Freitag, 14. Mai 2021, 04:35:33 CEST Avindra G wrote:
I've been having trouble getting deno to build since v1.9.0 (April 13th, 2021) on x86_64.
Tried various _constraints values, but the job is failing with the same error:
[ 3311s] LLVM ERROR: IO failure on output stream: No space left on device [ 3311s] /.build/build-vm: line 460: echo: write error: No space left on device [ 3312s] error: could not compile `deno` [ 3312s]
https://build.opensuse.org/package/show/devel:languages:javascript/deno#comm...
Can anyone advise?
it is still an error from inside of the VM.
You require 16GB and the worker provides 24GB disk space. It still seems not to be enough for this build job.
I would try a local build and check what it needs. There might be also some endless loop which would require infinite amount of disk space....
--
Adrian Schroeter <adrian@suse.de> Build Infrastructure Project Manager
SUSE Software Solutions Germany GmbH, Maxfeldstr. 5, 90409 Nuernberg, Germany (HRB 247165, AG München), Geschäftsführer: Felix Imendörffer
--
Adrian Schroeter <adrian@suse.de> Build Infrastructure Project Manager
SUSE Software Solutions Germany GmbH, Maxfeldstr. 5, 90409 Nuernberg, Germany (HRB 247165, AG München), Geschäftsführer: Felix Imendörffer
On Aug 11 2021, Avindra G wrote:
Running into this issue again with x86_64 builds of deno.
The last successful build was 1.11.5.
Note that the aarch64 is building 1.13.0 successfully.
Using 25G of disk space. You have been lucky that the worker had such a big disk, despite only asking for 4G.
https://build.opensuse.org/package/show/devel:languages:javascript/deno
Is there something needing cleaning in the backend?
You need to increase the disk size constraint. You are only asking for 16G, and the last worker had 24G. Andreas. -- Andreas Schwab, schwab@linux-m68k.org GPG Key fingerprint = 7578 EB47 D4E5 4D69 2510 2552 DF73 E780 A9DA AEC1 "And now for something completely different."
After increasing to 25GB for x86_64 the build is green again. Thanks for your help. avindra goolcharan On Wed, Aug 11, 2021 at 3:06 PM Andreas Schwab <schwab@linux-m68k.org> wrote:
On Aug 11 2021, Avindra G wrote:
Running into this issue again with x86_64 builds of deno.
The last successful build was 1.11.5.
Note that the aarch64 is building 1.13.0 successfully.
Using 25G of disk space. You have been lucky that the worker had such a big disk, despite only asking for 4G.
https://build.opensuse.org/package/show/devel:languages:javascript/deno
Is there something needing cleaning in the backend?
You need to increase the disk size constraint. You are only asking for 16G, and the last worker had 24G.
Andreas.
-- Andreas Schwab, schwab@linux-m68k.org GPG Key fingerprint = 7578 EB47 D4E5 4D69 2510 2552 DF73 E780 A9DA AEC1 "And now for something completely different."
participants (3)
-
Adrian Schröter -
Andreas Schwab -
Avindra G