public inbox for cygwin-apps@cygwin.com
 help / color / mirror / Atom feed
From: Jon Turney <jon.turney@dronecode.org.uk>
To: Marco Atzeri <marco.atzeri@gmail.com>,
	"cygwin-apps@cygwin.com" <cygwin-apps@cygwin.com>
Subject: Re: disk space limit of scallywag ?
Date: Sun, 12 Mar 2023 17:39:51 +0000	[thread overview]
Message-ID: <9174a7c2-856e-00ae-0a3b-971a85f54808@dronecode.org.uk> (raw)
In-Reply-To: <d2f1cca7-8aab-8328-89f7-441e579c72f3@gmail.com>

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...


  parent reply	other threads:[~2023-03-12 17:39 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 [this message]
2023-03-12 20:33   ` Marco Atzeri
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=9174a7c2-856e-00ae-0a3b-971a85f54808@dronecode.org.uk \
    --to=jon.turney@dronecode.org.uk \
    --cc=cygwin-apps@cygwin.com \
    --cc=marco.atzeri@gmail.com \
    /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).