intellij-platform-plugin-template icon indicating copy to clipboard operation
intellij-platform-plugin-template copied to clipboard

System.IO.IOException: No space left on device - CI Build phase

Open ramonvermeulen opened this issue 1 year ago • 3 comments

What happened?

Recently out of the sudden (I can't find an obvious cause) the build pipeline is throwing an IOException with No space left on device. The run history on my plugin it's build workflow can be found here, and the workflow yaml can be found here.

Relevant log output or stack trace

System.IO.IOException: No space left on device : '/home/runner/runners/2.320.0/_diag/Worker_20241111-195224-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.320.0/_diag/Worker_20241111-195224-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.320.0/_diag/Worker_20241111-195224-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)

Steps to reproduce

Create any PR on my repository, can't really find the root cause? Maybe GitHub recently changed something around disk space provisioning? Provisioning less disk space per (default) runner?

Gradle IntelliJ Plugin version

2.0.2

Gradle version

8.6

Operating System

Linux

Link to build, i.e. failing GitHub Action job

https://github.com/ramonvermeulen/dbt-toolkit/actions/runs/11785245430/job/32826093484

ramonvermeulen avatar Nov 12 '24 08:11 ramonvermeulen

Actually there is an open PR with a fix, I am not sure if it is the desired solution however the fix at least works for me.

PR with fix: https://github.com/JetBrains/intellij-platform-plugin-template/pull/482 Applied changes in my repo: https://github.com/ramonvermeulen/dbt-toolkit/pull/230

Might this be the desired fix and get merged, this issue can be closed.

ramonvermeulen avatar Nov 12 '24 09:11 ramonvermeulen

bumping this one, have the same issue :) thanks @ramonvermeulen for the workaround, it would be nice to see this incorporated into the plugin template though

nieomylnieja avatar May 29 '25 18:05 nieomylnieja

bumping to same issue, solved by trying this pr

Alanxtl avatar Jun 22 '25 12:06 Alanxtl