From: Brian Inglis <Brian.Inglis@Shaw.ca>
To: cygwin-apps@cygwin.com
Subject: Re: disk space limit of scallywag ?
Date: Sun, 12 Mar 2023 11:30:43 -0600 [thread overview]
Message-ID: <f52a100d-1191-90e2-97ed-282dd49e0ee4@Shaw.ca> (raw)
In-Reply-To: <d2f1cca7-8aab-8328-89f7-441e579c72f3@gmail.com>
Hi Marco,
Look in job at Summary - Annotations, and Artifacts:
(5594) cmake #2043
Triggered via repository dispatch 5 hours ago Status Total duration
@scallywag-botscallywag-bot
(5594) cmake c8f5df0 Failure 4h 51m 15s
Artifacts
4
...
Annotations
1 error and 3 warnings
x86_64 / build
Process completed with exit code 1.
noarch / build
No files were found with the provided path: builddir.tar.xz
setup.log.full. No artifacts will be uploaded.
x86_64 / build
The process 'C:\cygwin\bin\git.exe' failed with exit code 128
x86_64 / build
You are running out of disk space. The runner will stop working when the machine
runs out of disk space. Free space left: 99 MB
Artifacts
Produced during runtime
Name Size
metadata 222 Bytes
source builddir 34.8 MB
source packages 9.5 MB
x86_64 builddir 159 MB
So maybe 160MB?
On 2023-03-12 11: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):
--
Take care. Thanks, Brian Inglis Calgary, Alberta, Canada
La perfection est atteinte Perfection is achieved
non pas lorsqu'il n'y a plus rien à ajouter not when there is no more to add
mais lorsqu'il n'y a plus rien à retirer but when there is no more to cut
-- Antoine de Saint-Exupéry
next prev parent reply other threads:[~2023-03-12 17:30 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 [this message]
2023-03-12 17:39 ` Jon Turney
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=f52a100d-1191-90e2-97ed-282dd49e0ee4@Shaw.ca \
--to=brian.inglis@shaw.ca \
--cc=cygwin-apps@cygwin.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).