Hi, Great, thanks. As it happens I’ve been working on the bazel builds a bit, and discovered an option to disable local build caching. To quote the manual
--[no]use_action_cache <https://docs.bazel.build/versions/master/user-manual.html#flag--use_action_cache> This option is enabled by default. If disabled, Bazel will not use its local action cache. Disabling the local action cache saves memory and disk space for clean builds, but will make incremental builds slower. As the ‘incremental’ build option is not an issue for MacPorts, as builds are always started afresh with an empty cache, enabling this does not help us at all, and just uses resources. So I will turn this off. Chris > On 23 Mar 2021, at 4:04 pm, Ryan Schmidt <[email protected]> wrote: > > On Feb 11, 2021, at 04:21, Christopher Jones wrote: > >> I am seeing some large builds fail due to drive space issues >> >> https://build.macports.org/builders/ports-11_x86_64-builder/builds/21466/steps/install-port/logs/stdio >> error: >> /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/install_name_tool: >> can't write output file: >> bazel-out/host/bin/tensorflow/python/_pywrap_tfcompile.so.XXXXXX (No space >> left on device) >> Could the space on the drive for this build be reviewed and purged / >> increased a bit ? >> >> cheers Chris > > I did make an additional change to mpbb to delete more unneeded ports: > > https://trac.macports.org/ticket/57464#comment:12 > > And after updating to macOS 11.2.3 and Xcode 12.4 I deleted the simulator > directories again and I don't think they've come back. > > We have 26GB free at the moment. So let's let the next builds of > py-tensorflow* run without interrupting them and see if they complete now. >
smime.p7s
Description: S/MIME cryptographic signature
