/srv/irclogs.ubuntu.com/2021/04/21/#launchpad.txt

=== JanC is now known as Guest65907
=== JanC_ is now known as JanC
=== cjwatson changed the topic of #launchpad to: git.launchpad.net emergency maintenance | Help contact: @pappacena (12:00-21:00 UTC Mon-Fri) | Launchpad is an open source project: https://dev.launchpad.net/ | This channel is logged: http://irclogs.ubuntu.com/ | User Guide: https://help.launchpad.net/ | Support and spam reporting: https://answers.launchpad.net/launchpad
=== cjwatson changed the topic of #launchpad to: Help contact: @pappacena (12:00-21:00 UTC Mon-Fri) | Launchpad is an open source project: https://dev.launchpad.net/ | This channel is logged: http://irclogs.ubuntu.com/ | User Guide: https://help.launchpad.net/ | Support and spam reporting: https://answers.launchpad.net/launchpad
cjwatsonApologies for the git disruption there.  Hopefully things will be a bit smoother now14:18
pmjdebruijnhttps://launchpadlibrarian.net/534741323/buildlog_ubuntu-focal-amd64.prusa-slicer_2.3.1-0pmjdebruijn1~20.04_BUILDING.txt.gz am I reading that right, that my package build failed because of a lack of diskspace?17:39
pmjdebruijna local builddir does end up taking ~14GB17:41
pappacenapmjdebruijn If I'm not wrong, the builders are provisioned with 30gb disks. Are you sure it doesn't use more than 14GB at any given time during the build?17:47
pmjdebruijnnot sure18:00
pmjdebruijnbut presumably on those 30GB disks, part of that is taken with the build environment18:00
pappacenaYes, for sure. BTW, did you try to build again? I'm not seeing explicit disk space errors during the build process.18:01
pmjdebruijnI have enabled the debug symbols, which in local builds results in a 300MB ddeb18:01
pmjdebruijnI can ask to rebuild, np18:02
pmjdebruijnso let's wait and see18:02
pappacenaIt seems to be failing for some other reason, not disk space. The only place where "disk space" is mentioned is the final summary...18:05
cjwatsonThey're 60GB disks18:53
cjwatsonAnd agreed, disk space is not the problem here18:54
cjwatsonIt's just absurdly buried in a gigantic log18:55
cjwatsonBut if you search for the *first* occurrence of "Error 2" (matching the final error code from make) then you'll find it18:55
cjwatsonvirtual memory exhausted: Cannot allocate memory18:55
cjwatsonmake[3]: *** [tests/libslic3r/CMakeFiles/libslic3r_tests.dir/build.make:261: tests/libslic3r/CMakeFiles/libslic3r_tests.dir/test_voronoi.cpp.o] Error 118:55
cjwatsonSo single absurdly large translation unit I guess18:56
cjwatsonMaybe try a lower optimization level at least for that file18:56
cjwatsonI shouldn't think tests critically need to be built with -O3, so that might help.  Or there are typically various other approaches to make compilers use less memory18:57
sarnoldI saw discussion recently about some projects trying to bundle multiple source files into a single translation unit for some reason, and this causinga  huge amount of memory use19:16

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!