On Mar 23, 2021, at 11:04, Ryan Schmidt 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
This change uninstalled more ports than I intended. This resulted in many ports
needing to be reinstalled often. This slowed down builds and resulted in a
backlog of builds. I fixed the problem which means more ports will remain
installed now, which will take a little more disk space again.
https://trac.macports.org/ticket/57464#comment:16
> 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.
Both copies of the simulator caches came back again. I filed FB9072613 with
Apple about this. We were down to 3GB free disk space which isn't a good place
to be. I deleted the caches again and marked the dyld directories chmod 000.
Let's see if that prevents Xcode from recreating the caches, hopefully without
causing error messages that cause builds to fail. We now have 21GB free.
