Skip to content
Publish tarballs monthly

Publish tarballs monthly #27

Sign in to view logs

Publish tarballs monthly

Publish tarballs monthly #27

Triggered via schedule October 1, 2023 00:30
@KexyBiscuitKexyBiscuit
⁠ 308fae4
stable
Status Failure
Total duration 1d 7h 43m 5s
Artifacts 16
This run and associated checks have been archived and are scheduled for deletion. Learn more about checks retention

tarballs-monthly.yml

on: schedule
Matrix: tarball
Fit to window
Zoom out
Zoom in

Annotations

71 errors and 2 warnings
tarball (base, Ry3950X)
Process completed with exit code 255.
tarball (base, Ry3950X)
Process completed with exit code 255.
tarball (buildkit, Ry3950X)
Process completed with exit code 255.
tarball (buildkit, Ry3950X)
Process completed with exit code 255.
tarball (cinnamon, Ry3950X)
Process completed with exit code 255.
tarball (cinnamon, Ry3950X)
Process completed with exit code 255.
tarball (cinnamon, powernv)
No files were found with the provided path: os-ppc64el/cinnamon. No artifacts will be uploaded.
tarball (cinnamon, Resonance)
No files were found with the provided path: os-loongson3/cinnamon. No artifacts will be uploaded.
tarball (container, Ry3950X)
Process completed with exit code 255.
tarball (container, Ry3950X)
Process completed with exit code 255.
tarball (gnome, Ry3950X)
Process completed with exit code 255.
tarball (gnome, Ry3950X)
Process completed with exit code 255.
tarball (gnome, powernv)
No files were found with the provided path: os-ppc64el/gnome. No artifacts will be uploaded.
tarball (gnome, Resonance)
No files were found with the provided path: os-loongson3/gnome. No artifacts will be uploaded.
tarball (kde, Ry3950X)
Process completed with exit code 255.
tarball (kde, Ry3950X)
Process completed with exit code 255.
tarball (kde, kp920)
The hosted runner: GitHub Actions 2 lost communication with the server. Anything in your workflow that terminates the runner process, starves it for CPU/Memory, or blocks its network access can cause this error.
tarball (kde, kp920)
ENOSPC: no space left on device, write
tarball (kde, kp920)
Unable to process command 'error' successfully.
tarball (kde, kp920)
Unable to process file command 'step_summary' successfully.
tarball (kde, kp920)
No space left on device : '/home/runner/runners/2.309.0/_diag/Worker_20231001-135204-utc.log'
tarball (kde, powernv)
System.IO.IOException: No space left on device : '/home/runner/runners/2.309.0/_diag/Worker_20231001-171034-utc.log' at System.IO.RandomAccess.WriteAtOffset(SafeFileHandle handle, ReadOnlySpan`1 buffer, Int64 fileOffset) at System.IO.Strategies.BufferedFileStreamStrategy.FlushWrite() at System.IO.StreamWriter.Flush(Boolean flushStream, Boolean flushEncoder) at System.Diagnostics.TextWriterTraceListener.Flush() at GitHub.Runner.Common.HostTraceListener.WriteHeader(String source, TraceEventType eventType, Int32 id) at GitHub.Runner.Common.HostTraceListener.TraceEvent(TraceEventCache eventCache, String source, TraceEventType eventType, Int32 id, String message) at System.Diagnostics.TraceSource.TraceEvent(TraceEventType eventType, Int32 id, String message) at GitHub.Runner.Worker.Worker.RunAsync(String pipeIn, String pipeOut) at GitHub.Runner.Worker.Program.MainAsync(IHostContext context, String[] args) System.IO.IOException: No space left on device : '/home/runner/runners/2.309.0/_diag/Worker_20231001-171034-utc.log' at System.IO.RandomAccess.WriteAtOffset(SafeFileHandle handle, ReadOnlySpan`1 buffer, Int64 fileOffset) at System.IO.Strategies.BufferedFileStreamStrategy.FlushWrite() at System.IO.StreamWriter.Flush(Boolean flushStream, Boolean flushEncoder) at System.Diagnostics.TextWriterTraceListener.Flush() at GitHub.Runner.Common.HostTraceListener.WriteHeader(String source, TraceEventType eventType, Int32 id) at GitHub.Runner.Common.HostTraceListener.TraceEvent(TraceEventCache eventCache, String source, TraceEventType eventType, Int32 id, String message) at System.Diagnostics.TraceSource.TraceEvent(TraceEventType eventType, Int32 id, String message) at GitHub.Runner.Common.Tracing.Error(Exception exception) at GitHub.Runner.Worker.Program.MainAsync(IHostContext context, String[] args) Unhandled exception. System.IO.IOException: No space left on device : '/home/runner/runners/2.309.0/_diag/Worker_20231001-171034-utc.log' at System.IO.RandomAccess.WriteAtOffset(SafeFileHandle handle, ReadOnlySpan`1 buffer, Int64 fileOffset) at System.IO.Strategies.BufferedFileStreamStrategy.FlushWrite() at System.IO.StreamWriter.Flush(Boolean flushStream, Boolean flushEncoder) at System.Diagnostics.TextWriterTraceListener.Flush() at System.Diagnostics.TraceSource.Flush() at GitHub.Runner.Common.TraceManager.Dispose(Boolean disposing) at GitHub.Runner.Common.TraceManager.Dispose() at GitHub.Runner.Common.HostContext.Dispose(Boolean disposing) at GitHub.Runner.Common.HostContext.Dispose() at GitHub.Runner.Worker.Program.Main(String[] args)
tarball (kde, powernv)
The hosted runner: GitHub Actions 2 lost communication with the server. Anything in your workflow that terminates the runner process, starves it for CPU/Memory, or blocks its network access can cause this error.
tarball (kde, powernv)
ENOSPC: no space left on device, write
tarball (kde, Resonance)
No files were found with the provided path: os-loongson3/kde. No artifacts will be uploaded.
tarball (mate, Ry3950X)
Process completed with exit code 255.
tarball (mate, Ry3950X)
Process completed with exit code 255.
tarball (mate, powernv)
No files were found with the provided path: os-ppc64el/mate. No artifacts will be uploaded.
tarball (mate, Resonance)
No files were found with the provided path: os-loongson3/mate. No artifacts will be uploaded.
tarball (server, Ry3950X)
Process completed with exit code 255.
tarball (server, Ry3950X)
Process completed with exit code 255.
tarball (xfce, Ry3950X)
Process completed with exit code 255.
tarball (xfce, Ry3950X)
Process completed with exit code 255.
tarball (xfce, powernv)
No files were found with the provided path: os-ppc64el/xfce. No artifacts will be uploaded.
tarball (xfce, Resonance)
No files were found with the provided path: os-loongson3/xfce. No artifacts will be uploaded.
tarball (Ry3950X, base+nvidia, amd64)
Process completed with exit code 255.
tarball (Ry3950X, base+nvidia, amd64)
Process completed with exit code 255.
tarball (Ry3950X, base+nvidia340, amd64)
Process completed with exit code 255.
tarball (Ry3950X, base+nvidia340, amd64)
Process completed with exit code 255.
tarball (Ry3950X, base+nvidia390, amd64)
Process completed with exit code 255.
tarball (Ry3950X, base+nvidia390, amd64)
Process completed with exit code 255.
tarball (Ry3950X, cinnamon+nvidia, amd64)
Process completed with exit code 255.
tarball (Ry3950X, cinnamon+nvidia, amd64)
Process completed with exit code 255.
tarball (Ry3950X, cinnamon+nvidia340, amd64)
Process completed with exit code 255.
tarball (Ry3950X, cinnamon+nvidia340, amd64)
Process completed with exit code 255.
tarball (Ry3950X, cinnamon+nvidia390, amd64)
Process completed with exit code 255.
tarball (Ry3950X, cinnamon+nvidia390, amd64)
Process completed with exit code 255.
tarball (Ry3950X, gnome+nvidia, amd64)
Process completed with exit code 255.
tarball (Ry3950X, gnome+nvidia, amd64)
Process completed with exit code 255.
tarball (Ry3950X, gnome+nvidia340, amd64)
Process completed with exit code 255.
tarball (Ry3950X, gnome+nvidia340, amd64)
Process completed with exit code 255.
tarball (Ry3950X, gnome+nvidia390, amd64)
Process completed with exit code 255.
tarball (Ry3950X, gnome+nvidia390, amd64)
Process completed with exit code 255.
tarball (Ry3950X, kde+nvidia, amd64)
Process completed with exit code 255.
tarball (Ry3950X, kde+nvidia, amd64)
Process completed with exit code 255.
tarball (Ry3950X, kde+nvidia340, amd64)
Process completed with exit code 255.
tarball (Ry3950X, kde+nvidia340, amd64)
Process completed with exit code 255.
tarball (Ry3950X, kde+nvidia390, amd64)
Process completed with exit code 255.
tarball (Ry3950X, kde+nvidia390, amd64)
Process completed with exit code 255.
tarball (Ry3950X, mate+nvidia, amd64)
Process completed with exit code 255.
tarball (Ry3950X, mate+nvidia, amd64)
Process completed with exit code 255.
tarball (Ry3950X, mate+nvidia340, amd64)
Process completed with exit code 255.
tarball (Ry3950X, mate+nvidia340, amd64)
Process completed with exit code 255.
tarball (Ry3950X, mate+nvidia390, amd64)
Process completed with exit code 255.
tarball (Ry3950X, mate+nvidia390, amd64)
Process completed with exit code 255.
tarball (Ry3950X, xfce+nvidia, amd64)
Process completed with exit code 255.
tarball (Ry3950X, xfce+nvidia, amd64)
Process completed with exit code 255.
tarball (Ry3950X, xfce+nvidia340, amd64)
Process completed with exit code 255.
tarball (Ry3950X, xfce+nvidia340, amd64)
Process completed with exit code 255.
tarball (Ry3950X, xfce+nvidia390, amd64)
Process completed with exit code 255.
tarball (Ry3950X, xfce+nvidia390, amd64)
Process completed with exit code 255.
tarball (kde, kp920)
You are running out of disk space. The runner will stop working when the machine runs out of disk space. Free space left: 91 MB
tarball (kde, powernv)
You are running out of disk space. The runner will stop working when the machine runs out of disk space. Free space left: 82 MB

Artifacts

Produced during runtime
Name Size
os-arm64_base Expired
2.23 GB
os-arm64_buildkit Expired
1.6 GB
os-arm64_cinnamon Expired
10.1 GB
os-arm64_container Expired
1.05 GB
os-arm64_gnome Expired
9.84 GB
os-arm64_mate Expired
9.91 GB
os-arm64_server Expired
2.62 GB
os-arm64_xfce Expired
9.67 GB
os-loongson3_base Expired
1.76 GB
os-loongson3_buildkit Expired
1.48 GB
os-loongson3_container Expired
1010 MB
os-loongson3_server Expired
2.24 GB
os-ppc64el_base Expired
1.92 GB
os-ppc64el_buildkit Expired
1.6 GB
os-ppc64el_container Expired
1020 MB
os-ppc64el_server Expired
2.39 GB