-
Notifications
You must be signed in to change notification settings - Fork 6
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix failing unit tests #903
Comments
System.IO.IOException: No space left on device : '/home/runner/runners/2.311.0/_diag/Worker_20231203-141012-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.311.0/_diag/Worker_20231203-141012-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.311.0/_diag/Worker_20231203-141012-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)
|
Definitely caused by us downloading spacy en_web_lg, even if there are workarounds we could take. We could use tools.suffolklitlab.org instead, just need to somehow put that into the unit test. |
After removing the spacy model, I monitored the running action and it still runs out of disk space. It seemed to be downloading docassemble.webapp over and over again for the whole 22 minutes: https://github.com/SuffolkLITLab/docassemble-ALWeaver/actions/runs/7101684469/job/19330335255
|
OK! It looks like this line: Edit: no actually the problem is with docassemble.webapp, not docassemble.base |
Looks related to this comment specifically: pypa/pip#9284 (comment). I'm gonna try setting some more strict versions in |
Where did you find that full log btw @nonprofittechy? |
It is only visible when it is actually running which is... annoying [Also I can only see the most recent thousand lines, not the top] |
Found what I think is the issue: FormFyxer depends on scikit-learn 1.2.2, and docassemble requires 1.3.0. It looks like something must have changed in pip recently such that when a conflict happens, it downloads an older (or newer, starting from a really old version? looking at your logs) version of the package until it can find one that works. Pretty silly. I can't seem to fix it though, because before this, docassemble required scikit-learn 1.2.1, so none of our FormFyxer scikit versions match docassembles. https://github.com/SuffolkLITLab/docassemble-ALWeaver/actions/runs/7102499306/job/19333005336. We're gonna have to fix on the FormFyxer side, but I don't remember why we fixed |
great find! I wonder how much of the scikit-learn stuff we'll need when we switch to GPT. |
It looks to me like the problem is the size of the dependencies. We should see what can be stripped out. Possibly it's the spacy models?
The text was updated successfully, but these errors were encountered: