trigger failing on chromium.perf/Mac Builder Perf |
|||
Issue descriptionFiled by sheriff-o-matic@appspot.gserviceaccount.com on behalf of eyaich@google.com trigger failing on chromium.perf/Mac Builder Perf Builders failed on: - Mac Builder Perf: https://build.chromium.org/p/chromium.perf/builders/Mac%20Builder%20Perf
,
Apr 19 2018
The bot doesn't have the tools installed, which is now being caught as it should be! otool: error: unable to find utility "otool", not a developer tool or in PATH ERROR from command "otool -l /b/c/b/Mac_Builder_Perf/src/out/Release/Google Chrome Framework.framework/Google Chrome Framework": 72 Infra: can we get the Xcode tools installed on these bots: vm175-m1 (https://ci.chromium.org/buildbot/chromium.perf/Mac%20Builder%20Perf/4296) vm168-m1 (https://ci.chromium.org/buildbot/chromium.perf/Mac%20Builder%20Perf/4294) vm158-m1 (https://ci.chromium.org/buildbot/chromium.perf/Mac%20Builder%20Perf/4292) vm669-m1 (https://ci.chromium.org/buildbot/chromium.chrome/Google%20Chrome%20Mac/32414)
,
Apr 19 2018
This has been broken for a while, as they had the Command Line Tools installed, but otool moved out of path as not to break hermetic Xcode, which has since been removed from bootstrapping scripts back in Feb. otool is now properly in path on the bots listed in #2. Long-term, probably best to pull in heremetic Xcode. |
|||
►
Sign in to add a comment |
|||
Comment 1 by eyaich@chromium.org
, Apr 19 2018Labels: -Pri-2 OS-Mac Pri-1
Owner: rsesek@chromium.org