Buildbot failures on 10.11

[Ryan Schmidt]

On Mar 23, 2019, at 04:37, Christopher Jones wrote:

>> The log says:
>> 
>> 
>> xcrun: warning: cache file '/var/folders/b3/_c47r31s23q0mgj1jvy64bkw0000gp/T/xcrun_db' appears to be corrupted (21, 2090430, 327680); resetting it
>>       cache: 0x10217d000
>>       .magic: XR1L
>>       .numEntries: 21
>>       .strTableSize: 2090430
>>       .entries: {
>> xcrun: warning: cache file '/var/folders/b3/_c47r31s23q0mgj1jvy64bkw0000gp/T/xcrun_db' appears to be corrupted (21, 2090430, 327680); resetting it
>>       cache: 0x106a9a000
>>       .magic: XR1L
>>       .numEntries: 21
>>       .strTableSize: 2090430
>>       .entries: {
>> xcrun: warning: cache file '/var/folders/b3/_c47r31s23q0mgj1jvy64bkw0000gp/T/xcrun_db' appears to be corrupted (21, 2090430, 327680); resetting it
>>       cache: 0x109d00000
>>       .magic: XR1L
>>       .numEntries: 21
>>       .strTableSize: 2090430
>>       .entries: {
>> xcrun: warning: cache file '/var/folders/b3/_c47r31s23q0mgj1jvy64bkw0000gp/T/xcrun_db' appears to be corrupted (21, 2090430, 327680); resetting it
>>       cache: 0x10e300000
>>       .magic: XR1L
>>       .numEntries: 21
>>       .strTableSize: 2090430
>>       .entries: {
>> /usr/bin/mig: line 162: : command not found
>> mig: fatal: "<no name yet>", line -1: no SubSystem declaration
>> make[3]: *** [mach_startup.h] Error 1
>> 
>> 
>> I'm not familiar with this error. I don't know what xcrun_db is (I presume it is used by xcrun), in what way it might be corrupt, or how that corruption might be fixed. Do you have any suggestions?
> 
> I think you need to clear out those temporary files, in some way, from /var/folders. Maybe try a simple reboot ??

I took the builder offline after my last message. I've rebooted it now and brought it back online, but I haven't manually deleted any files. It seems to be building successfully. I've scheduled new builds for the two ports that failed due to this issue. I've manually uninstalled some large unneeded ports to free up more space.


>> Maybe it was corrupted because it was truncated because it could not be fully written because the disk was full; as you know, we are low on disk space on these builders. We should try having the build system uninstall unneeded ports on an ongoing basis, as in https://trac.macports.org/ticket/57464
> 
> I am sure this was the result of a previously failure due to disk space. I really think we need to press on deploying those changes discussed above.

The ticket discusses conceptual changes we could make to the buildbot setup, but the code to implement those changes has not yet been written; there's nothing to deploy right now. I agree we should decide what to do, and then do it.