New issue
Advanced search Search tips

Issue 785607 link

Starred by 1 user

Issue metadata

Status: Available
Owner: ----
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: iOS
Pri: 3
Type: Bug



Sign in to add a comment

auto_reboot=true is not working on GomaCanaryiOS builder

Project Member Reported by tikuta@chromium.org, Nov 16 2017

Issue description

https://luci-milo.appspot.com/buildbot/chromium.fyi/GomaCanaryiOS/30896

[5012/54780] ACTION //ios/showcase/core/resources:launchscreen_xib_compile_storyboard(//build/toolchain/mac:ios_clang_arm)
FAILED: gen/ios/showcase/core/resources/launchscreen_xib_compile_storyboard/LaunchScreen.storyboardc 
python ../../build/config/mac/compile_ib_files.py --input ../../ios/showcase/core/resources/LaunchScreen.storyboard --output /b/build/slave/GomaCanaryiOS/build/src/out/Release-iphoneos/gen/ios/showcase/core/resources/launchscreen_xib_compile_storyboard/LaunchScreen.storyboardc --developer_dir /b/build/slave/GomaCanaryiOS/build/src/build/ios_files/Xcode.app --minimum-deployment-target 9.0 --auto-activate-custom-fonts --target-device iphone --target-device ipad
2017-11-15 16:19:58.605 ibtoold[49462:570852415] [MT] IBPlatformTool: *** Failed to launch tool with description <IBCocoaTouchPlatformToolDescription: 0x7fea8a440420> System content for IBCocoaTouchFramework-ElevenAndLater <IBScaleFactorDeviceTypeDescription: 0x7fea8a4434a0> scaleFactor=2x: Failed to find or create execution context for description <IBCocoaTouchPlatformToolDescription: 0x7fea8a440420> System content for IBCocoaTouchFramework-ElevenAndLater <IBScaleFactorDeviceTypeDescription: 0x7fea8a4434a0> scaleFactor=2x: Failed to find a suitable device for the type IBSimDeviceTypeiPad2x (com.apple.dt.Xcode.IBSimDeviceType.iPad-2x) with runtime iOS 11.1 (11.1 - 15B87) - com.apple.CoreSimulator.SimRuntime.iOS-11-1 (Failure reason: Failed to create new simulator device that matches IBSimDeviceTypeiPad2x (com.apple.dt.Xcode.IBSimDeviceType.iPad-2x) for runtime iOS 11.1 (11.1 - 15B87) - com.apple.CoreSimulator.SimRuntime.iOS-11-1 (Invalid runtime: com.apple.CoreSimulator.SimRuntime.iOS-11-1)): Invalid runtime: com.apple.CoreSimulator.SimRuntime.iOS-11-1
2017-11-15 16:20:07.787 ibtoold[49462:570852415] [MT] IBPlatformTool: Wrote failed marshalling request diagnostics to path: /var/folders/p4/py6nlvcx4fs5s3fg51_pzqmc0000gm/T/IB-agent-diagnostics_2017-11-15_16-20-06_629000
/* com.apple.ibtool.errors */
/b/build/slave/GomaCanaryiOS/build/src/ios/showcase/core/resources/LaunchScreen.storyboard: error: Internal error. Please file a bug at bugreport.apple.com and attach "/var/folders/p4/py6nlvcx4fs5s3fg51_pzqmc0000gm/T/IB-agent-diagnostics_2017-11-15_16-20-06_629000".
    Underlying Errors:
        Description: Failed to find or create execution context for description <IBCocoaTouchPlatformToolDescription: 0x7fea8a440420> System content for IBCocoaTouchFramework-ElevenAndLater <IBScaleFactorDeviceTypeDescription: 0x7fea8a4434a0> scaleFactor=2x
        Underlying Errors:
            Description: Failed to find a suitable device for the type IBSimDeviceTypeiPad2x (com.apple.dt.Xcode.IBSimDeviceType.iPad-2x) with runtime iOS 11.1 (11.1 - 15B87) - com.apple.CoreSimulator.SimRuntime.iOS-11-1
            Failure Reason: Failed to create new simulator device that matches IBSimDeviceTypeiPad2x (com.apple.dt.Xcode.IBSimDeviceType.iPad-2x) for runtime iOS 11.1 (11.1 - 15B87) - com.apple.CoreSimulator.SimRuntime.iOS-11-1 (Invalid runtime: com.apple.CoreSimulator.SimRuntime.iOS-11-1)
            Underlying Errors:
                Description: Invalid runtime: com.apple.CoreSimulator.SimRuntime.iOS-11-1
Traceback (most recent call last):
  File "../../build/config/mac/compile_ib_files.py", line 61, in <module>
    sys.exit(main())
  File "../../build/config/mac/compile_ib_files.py", line 44, in main
    stdout = subprocess.check_output(ibtool_args)
  File "/System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/subprocess.py", line 573, in check_output
    raise CalledProcessError(retcode, cmd, output=output)
subprocess.CalledProcessError: Command '['xcrun', 'ibtool', '--errors', '--warnings', '--notices', '--output-format', 'human-readable-text', '--minimum-deployment-target', '9.0', '--auto-activate-custom-fonts', '--target-device', 'iphone', '--target-device', 'ipad', '--compile', '/b/build/slave/GomaCanaryiOS/build/src/out/Release-iphoneos/gen/ios/showcase/core/resources/launchscreen_xib_compile_storyboard/LaunchScreen.storyboardc', '/b/build/slave/GomaCanaryiOS/build/src/ios/showcase/core/resources/LaunchScreen.storyboard']' returned non-zero exit status 1


At first, I thought disk issue. But looks not.
The builder went to broken status?
 

Comment 1 by tikuta@chromium.org, Nov 16 2017

Owner: tikuta@chromium.org
Status: Started (was: Untriaged)
I found some threads saying restart of Xcode fix the issue for similar error.
https://stackoverflow.com/questions/42823160/ios-build-failed-at-compile-time-with-issue-failed-to-find-a-suitable-device-fo

And buildbot running 30 days.
chrome-bot@vm66-m1:(Mac 10.12.2):~$ uptime 
18:02  up 30 days,  4:33, 2 users, load averages: 5.35 5.13 6.08

Let me try to reboot the vm.

Comment 3 by tikuta@chromium.org, Nov 16 2017

Cc: dpranke@chromium.org
Components: Infra>Labs
Summary: auto_reboot=true is not working on GomaCanaryiOS builder (was: Build failure on GomaCanaryiOS)
Dirk, do you know about auto_reboot config or someone knows about it?
sorry for the delay, any trooper should probably be able to look into this, but iannucci@ and agable@ are particularly wise in these things :).

Comment 5 by tikuta@chromium.org, Nov 22 2017

Cc: aga...@chromium.org iannucci@chromium.org
Owner: ----
Status: Available (was: Started)
#4, Thanks.

iannucci@, agable@, do you know something about this?

Comment 6 by aga...@chromium.org, Nov 29 2017

That auto_reboot change was landed on Nov 16th, but master.chromium.fyi hasn't been rebooted since Nov 14th: https://build.chromium.org/p/chromium.fyi/json/clock?as_text=1
  server_started: {
    local: "2017-11-14T16:27:14.425674",
    utc: "2017-11-15T00:27:14.425666",
    utc_ts: 1510705634.425666
  }

Just file a master restart request and the trooper will handle it.

Comment 7 by tikuta@chromium.org, Nov 30 2017

My link was just taken from the HEAD at that time.

Actual change was landed more than a year ago.
https://chromium.googlesource.com/chromium/tools/build/+blame/7e55ea0f0a4cc58ed44afd5fff20083a1546c5e1/masters/master.chromium.fyi/master.cfg#646

Comment 8 by aga...@chromium.org, Nov 30 2017

Huh, then I've got no idea.
Clearly the answer is to just move off of buildbot :).
Cc: -iannucci@chromium.org iannu...@google.com

Sign in to add a comment