From: Marco Atzeri <marco.atzeri@gmail.com>
To: Jon Turney <jon.turney@dronecode.org.uk>,
"cygwin-apps@cygwin.com" <cygwin-apps@cygwin.com>
Subject: Re: disk space limit of scallywag ?
Date: Sun, 12 Mar 2023 21:33:03 +0100 [thread overview]
Message-ID: <e0288317-d1ab-f93f-3407-60fdf64676fe@gmail.com> (raw)
In-Reply-To: <9174a7c2-856e-00ae-0a3b-971a85f54808@dronecode.org.uk>
On 12.03.2023 18:39, Jon Turney wrote:
> On 12/03/2023 17:08, Marco Atzeri via Cygwin-apps wrote:
>> Hi Jon,
>>
>> what is the current disk space limit of scallywag ?
>>
>> jobs 5594
>>
>> https://github.com/cygwin/scallywag/actions/runs/4397354263/jobs/7700519955
>>
>> ..
>> scallywag: staging/cmake/vim-cmake/vim-cmake-3.23.2-2.hint
>> scallywag: staging/cmake/vim-cmake/vim-cmake-3.23.2-2.tar.xz
>> xz: (stdout): Write error: No space left on device
>> tar: /cygdrive/d/a/scallywag/scallywag/builddir.tar.xz: Cannot write:
>> Broken pipe
>> tar: Child returned status 1
>> tar: Error is not recoverable: exiting now
>> Traceback (most recent call last):
>>
>
> The the VM is supposed to have at least 14GB free disk space, which
> seems like it should be enough.
>
> But maybe there's something I'm doing wrong here (like trying to create
> this archive on the wrong drive or something...). Let me look into this
> a bit more...
>
cmake is a huge orc
previous build tree on my laptop
(only difference was python 3.8 instead of 3.9)
$ du -hs cmake-3.23.2-1.x86_64
13G cmake-3.23.2-1.x86_64
$ du -hs *
9.0G build
1.0K config
0 CYGWIN-PATCHES
387M dist
2.7G inst
1.7M log
71M origsrc
0 patch
9.6M spkg
71M src
656K temp
just the testing is requiring
3.6G Tests
so no doubt it hits the 14GB issues
Regards
Marco
next prev parent reply other threads:[~2023-03-12 20:33 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-12 17:08 Marco Atzeri
2023-03-12 17:30 ` Brian Inglis
2023-03-12 17:39 ` Jon Turney
2023-03-12 20:33 ` Marco Atzeri [this message]
2023-03-12 21:00 ` Jon Turney
2023-03-12 22:27 ` Marco Atzeri
2023-03-13 14:33 ` Jon Turney
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=e0288317-d1ab-f93f-3407-60fdf64676fe@gmail.com \
--to=marco.atzeri@gmail.com \
--cc=cygwin-apps@cygwin.com \
--cc=jon.turney@dronecode.org.uk \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).