Re: disk space limit of scallywag ?
On 12/03/2023 22:27, Marco Atzeri via Cygwin-apps wrote:
Hi Jon,
will be possible to pass the token notest to the sub-command rerun ?
For the time being I used SCALLYWEG="notest"
Yes, e.g. 'jobs rerun --token notest 5594'
Unfortunately, this can run into well known ssh quotation difficulties
when you want to specify multiple space separated tokens (as the command
is evaluated by the local shell and the the remote shell), so maybe
needs some improvement...
(I think maybe something like ssh cyg...@cygwin.com "jobs rerun --token
'notest label' 5594" works, but I haven't tested it...)
PS: there is a mismatch in the documentation
subcommands:
{cancel,deploy,help,rerun}
cancel cancel job
deploy deploy job
help this help
rerun re-run job
While on the web:
rebuild
rebuild a job (e.g. if it failed due to some transient condition, or
optionally with different tokens).
Thanks for pointing this out. I fixed the documentation.
Re: disk space limit of scallywag ?
On 12.03.2023 22:00, Jon Turney wrote:
On 12/03/2023 20:33, Marco Atzeri via Cygwin-apps wrote:
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...
just the testing is requiring
3.6G Tests
so no doubt it hits the 14GB issues
Yeah. It seems to be the test suite which takes a fantastic amount of
disk space (and time), so as a workaround for the moment, adding the
control token 'notest' should let it build and package successfully.
Hi Jon,
will be possible to pass the token notest to the sub-command rerun ?
For the time being I used SCALLYWEG="notest"
PS: there is a mismatch in the documentation
subcommands:
{cancel,deploy,help,rerun}
cancel cancel job
deploy deploy job
helpthis help
rerun re-run job
While on the web:
rebuild
rebuild a job (e.g. if it failed due to some transient condition, or
optionally with different tokens).
Regards
Marco
Re: disk space limit of scallywag ?
On 12/03/2023 20:33, Marco Atzeri via Cygwin-apps wrote: 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 Yeah. It seems to be the test suite which takes a fantastic amount of disk space (and time), so as a workaround for the moment, adding the control token 'notest' should let it build and package successfully.
Re: disk space limit of scallywag ?
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.0Gbuild 1.0Kconfig 0 CYGWIN-PATCHES 387Mdist 2.7Ginst 1.7Mlog 71M origsrc 0 patch 9.6Mspkg 71M src 656Ktemp just the testing is requiring 3.6GTests so no doubt it hits the 14GB issues Regards Marco
Re: disk space limit of scallywag ?
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...
Re: disk space limit of scallywag ?
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 c8f5df0Failure 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 NameSize metadata222 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
disk space limit of scallywag ?
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): Regards Marco
