Hi Erik, thanks for trying to make GitLab CI work again.
On Wednesday, April 17, 2019 at 3:46:44 PM UTC+2, E. Madison Bray wrote: > > Well it was hard to tell from the logs, but the main problem turned > out to be running out of disk space. I don't know why--the worker > machines had 20GB each which you'd think should be enough, and that it > wasn't is something worth investigating in its own right. > I wrote a comment in the `.gitlab-ci.yml` at some point that says # * runners tagged as "gce" (Google Compute Engine) provide about 22GB of HDD , # a single core, 4GB of RAM. Since we are relying on OverlayFS, the disk # space is not sufficient to build sage from scratch. It seems that with overlayfs we need lots of disk space temporarily. I forgot about the details but I think it could be how the copy-on-write works that we basically need space for several copies of Sage's local/ directory. Anyway, requiring that much temporary disk space is probably nothing we can do much about in a docker setup easily. julian -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-devel+unsubscr...@googlegroups.com. To post to this group, send email to sage-devel@googlegroups.com. Visit this group at https://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
