11_x86 build - build failures due to 'no space on device'
ryandesign at macports.org
Fri Feb 12 01:19:28 UTC 2021
On Feb 11, 2021, at 18:45, 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
>> 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 ?
> Sigh... not again...
> Josh reported the same thing one month ago on the infrastructure list. At the time, I discovered that Xcode had created two separate copies of a CoreSimulator directory, each containing cache files for simulating iOS, iPadOS, watchOS and tvOS environments, none of which we need or asked for, and each copy occupied 9.2GB. At the time, I deleted one of them, leaving us with 25GB free space. I have now deleted the second one, leaving us with 11GB free space and additional space will be freed once the currently running build of py37-tensorflow finishes. But it seems likely that Xcode will silently recreate this enormous cache at some point in the future.
Looks like the copy of the CoreSimulator directory that I had deleted on January 18 got recreated on January 25. I have deleted it again. We are now at 20GB free.
More information about the macports-dev