> On 13 Feb 2021, at 9:06 am, Ryan Schmidt <ryandes...@macports.org> wrote:
>
> On Feb 11, 2021, at 19:19, Ryan Schmidt wrote:
>
>>> 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
>>>>
>>>> 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 ?
>>>
>>> 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.
>
> Apple helpfully recreated the CoreSimulator directory again today. I'm not
> going to delete it again unless we have a plan for how to prevent it from
> being recreated, to avoid unnecessary wear and tear on the SSD, since we've
> already destroyed three SSDs in these servers. 16 GB free. I have another
> change planned to mpbb to free up some more space.
Just a though but maybe if you delete it and create a stub empty file in its
place, will block whatever is recreating it ?
Chris
>
