This would need to be replaced with 10.11 instead then.

I expect most bots to still be on Xcode 5.1.1. Is this causing a problem? Ideally, we'd update the Xcode versions on the bots in batch via hermetic builds.

Oh if it's expected then I guess we should WontFix this. I figure the old ld/dsymutil are responsible for  bug 622406 .

Erik, do you mean that we’re currently getting Xcode tools like ld and dsymutil from a hermetic package and not the version installed on the system? If that’s the case, then what version of Xcode (or ld and dsymutil) is currently in that hermetic package?

If it’s not the case, then I think we’re set up for eventual disaster. It’s unwise to mix the Xcode tools with a newer SDK. An easy example is that ld from Xcode < 7 won’t understand the .tbd files in SDK >= 10.11.

We’re not trying to make official builds with that SDK yet, but there may well be aspects of the 10.10 SDK that older tools from Xcode 5.1.1 don’t really understand.

Also, if we are using the system Xcode tools, I’m surprised that we stopped at 5.1.1 for 10.9 bots when 10.9 will run Xcodes as new as 6.2 (which did actually ship with the 10.10 SDK).

We're using system Xcode. The reason that everything is still on an ancient Xcode version is that we want consistency, and prior to hermetic builds, updating all the machines was a gargantuan effort. 

When we rev the SDK, we should also rev Xcode, although that will be capped at 6, since reimaging machines to be > 10.9 is still a pain. Maybe one day with swarming...

Thanks.

Like I said, I’m fearful of mixing Xcode 5.1.1 with the 10.10 SDK, although we’ve been doing it for months, so maybe we’ve already seen everything that would shake out of this combination (and maybe it was nothing).

Would it be a gargantuan effort to update all of these 10.9 bots with Xcode 5.1.1 to Xcode 6.2? Is the project to hermeticize things ready?

We've turned on hermetic builds on quite a few of the bots in chromium_fyi, chromium_gpu and chromium_mac.

Looks like this bot lives in chromium_chrome.py.  Should we set 'force_mac_toolchain' in chromium_apply_config there as well?

we should try and let the sheriffs know and then wait to see what breaks.