"ios_chrome_unittests" is flaky (AppLaunchError: Simulator failed to start) |
|||||||||
Issue description"ios_chrome_unittests" is flaky. This issue was created automatically by the chromium-try-flakes app. Please find the right owner to fix the respective test/step and assign this issue to them. If the step/test is infrastructure-related, please add Infra-Troopers label and change issue status to Untriaged. When done, please remove the issue from Sheriff Bug Queue by removing the Sheriff-Chromium label. We have detected 3 recent flakes. List of all flakes can be found at https://chromium-try-flakes.appspot.com/all_flake_occurrences?key=ahVzfmNocm9taXVtLXRyeS1mbGFrZXNyHwsSBUZsYWtlIhRpb3NfY2hyb21lX3VuaXR0ZXN0cww.
,
Jun 3 2016
+smut Hey Sana, any idea why this is happening?
,
Jun 3 2016
No idea. +cc iOS sheriffs.
,
Jun 3 2016
(explicitly assigning for sheriff followup)
,
Jun 3 2016
ios_chrome_unittests is not flaky on downstream bot, so this is infrastructure problem rather than a problem with app code. Sana, do you know who would the the right person to troubleshoot this?
,
Jun 3 2016
No. I have no idea where to begin. I have seen app launch flake downstream on simulator, although it's somewhat rare. I have no idea why the app fails to launch sometimes or what it means when it says: iossim: ERROR: Simulator failed to start: "The operation couldn’t be completed. (Cocoa error -102.)" (NSCocoaErrorDomain:-102)
,
Jun 3 2016
Ok. We should figure out some options here then. 1) The error recommends one files a bug with apple - has anyone done that yet? 2) It looks like we're already doing one retry and it's failing the same way both times, so adding another probably won't help. 3) There seems to be agreement that we don't have enough information. What information would it take to understand what's happening or to reproduce the error? Here's the stdio of the failing step for future reference: @@@STEP_CURSOR@ios_chrome_unittests (iPhone 5s iOS 9.0)@@@ @@@STEP_STARTED@@@ /b/build/scripts/slave/ios/run.py --app /b/build/slave/ios-simulator-gn/build/src/out/Debug-iphonesimulator/ios_chrome_unittests.app --json_file /tmp/tmppjRxX8.json --iossim /b/build/slave/ios-simulator-gn/build/src/out/Debug-iphonesimulator/iossim --platform 'iPhone 5s' --version 9.0 in dir /b/build/slave/ios-simulator-gn/build: cmd: ['/b/build/scripts/slave/ios/run.py', '--app', '/b/build/slave/ios-simulator-gn/build/src/out/Debug-iphonesimulator/ios_chrome_unittests.app', '--json_file', '/tmp/tmppjRxX8.json', '--iossim', '/b/build/slave/ios-simulator-gn/build/src/out/Debug-iphonesimulator/iossim', '--platform', 'iPhone 5s', '--version', '9.0'] name: ios_chrome_unittests (iPhone 5s iOS 9.0) step_test_data: test_results(...) full environment: AWS_CREDENTIAL_FILE: /b/build/site_config/.boto BOTO_CONFIG: /b/build/site_config/.boto BUILDBOT_BLAMELIST: [u'eugenebut@chromium.org'] BUILDBOT_BRANCH: BUILDBOT_BUILDBOTURL: http://build.chromium.org/p/tryserver.chromium.mac/ BUILDBOT_BUILDERNAME: ios-simulator-gn BUILDBOT_BUILDNUMBER: 15998 BUILDBOT_CLOBBER: BUILDBOT_GOT_REVISION: None BUILDBOT_MASTERNAME: tryserver.chromium.mac BUILDBOT_REVISION: BUILDBOT_SCHEDULER: None BUILDBOT_SLAVENAME: vm898-m4 CHROME_HEADLESS: 1 GIT_USER_AGENT: darwin git/2.7.4 vm898-m4.golo.chromium.org HOME: /Users/chrome-bot LOGNAME: chrome-bot PAGER: cat PATH: /Users/chrome-bot/slavebin:/b/depot_tools:/usr/local/git/bin:/usr/bin:/usr/bin:/bin:/usr/sbin:/sbin:/usr/local/bin PWD: /b/build/slave/ios-simulator-gn/build PYTHONPATH: /b/build/site_config:/b/build/scripts:/b/build/scripts/release:/b/build/third_party:/b/build/third_party/requests_2_10_0:/b/build_internal/site_config:/b/build_internal/symsrc:/b/build/slave:/b/build/third_party/buildbot_slave_8_4:/b/build/third_party/twisted_10_2: SHELL: /bin/bash SSH_AUTH_SOCK: /private/tmp/com.apple.launchd.PvZyfi4E7w/Listeners USER: chrome-bot /usr/libexec/PlistBuddy -c Print:CFBundleIdentifier /b/build/slave/ios-simulator-gn/build/src/out/Debug-iphonesimulator/ios_chrome_unittests.app/Info.plist cwd: /b/build/slave/ios-simulator-gn/build com.google.gtest.ios_chrome_unittests pkill -9 -x iPhone Simulator iOS Simulator Simulator cwd: /b/build/slave/ios-simulator-gn/build /b/build/slave/ios-simulator-gn/build/src/out/Debug-iphonesimulator/iossim -d iPhone 5s -s 9.0 -t 120 -u /tmp/tmptLLEgs /b/build/slave/ios-simulator-gn/build/src/out/Debug-iphonesimulator/ios_chrome_unittests.app cwd: /b/build/slave/ios-simulator-gn/build 2016-06-03 08:50:51.727 iossim[6288:13374] [MT] DVTAssertions: Warning in /Library/Caches/com.apple.xbs/Sources/DVTFrameworks/DVTFrameworks-8201/DVTFoundation/PlugInArchitecture/PlugInManager/DVTPlugInManager.m:257 Details: Requested but did not find extension point with identifier Xcode.DVTFoundation.DevicePlatformMapping Object: <DVTPlugInManager: 0x7feaada20b00> Method: -extensionPointWithIdentifier: Thread: <NSThread: 0x7feaab40b760>{number = 1, name = main} Please file a bug at http://bugreport.apple.com with this warning message and any useful information you can provide. iossim: ERROR: Simulator failed to start: "The operation couldn’t be completed. (Cocoa error -102.)" (NSCocoaErrorDomain:-102) Supported device/SDK combinations: -d 'iossim - iPhone 5s ' -s '9.0' /b/build/slave/ios-simulator-gn/build/src/out/Debug-iphonesimulator/iossim returned 4 ios_chrome_unittests appears to have crashed on startup. Retrying... pkill -9 -x iPhone Simulator iOS Simulator Simulator cwd: /b/build/slave/ios-simulator-gn/build /b/build/slave/ios-simulator-gn/build/src/out/Debug-iphonesimulator/iossim -d iPhone 5s -s 9.0 -t 120 -u /tmp/tmpsvclxW /b/build/slave/ios-simulator-gn/build/src/out/Debug-iphonesimulator/ios_chrome_unittests.app cwd: /b/build/slave/ios-simulator-gn/build 2016-06-03 08:51:04.829 iossim[6357:14359] [MT] DVTAssertions: Warning in /Library/Caches/com.apple.xbs/Sources/DVTFrameworks/DVTFrameworks-8201/DVTFoundation/PlugInArchitecture/PlugInManager/DVTPlugInManager.m:257 Details: Requested but did not find extension point with identifier Xcode.DVTFoundation.DevicePlatformMapping Object: <DVTPlugInManager: 0x7fcfe9414b60> Method: -extensionPointWithIdentifier: Thread: <NSThread: 0x7fcfe940b760>{number = 1, name = main} Please file a bug at http://bugreport.apple.com with this warning message and any useful information you can provide. iossim: ERROR: Simulator failed to start: "The operation couldn’t be completed. (Cocoa error -102.)" (NSCocoaErrorDomain:-102) Supported device/SDK combinations: -d 'iossim - iPhone 5s ' -s '9.0' /b/build/slave/ios-simulator-gn/build/src/out/Debug-iphonesimulator/iossim returned 4 pkill -9 -x iPhone Simulator iOS Simulator Simulator cwd: /b/build/slave/ios-simulator-gn/build step returned non-zero exit code: 2 @@@STEP_TEXT@AppLaunchError@@@ @@@STEP_LOG_LINE@json.output@{@@@ @@@STEP_LOG_LINE@json.output@ "links": {}, @@@ @@@STEP_LOG_LINE@json.output@ "logs": {}, @@@ @@@STEP_LOG_LINE@json.output@ "step_text": "AppLaunchError"@@@ @@@STEP_LOG_LINE@json.output@}@@@ @@@STEP_LOG_END@json.output@@@ @@@STEP_EXCEPTION@@@
,
Jun 3 2016
Did we change anything in the way how we launch the Simulator? Should we try reinstalling Xcode on this specific machine? Filing radar against Apple unlikely will be helpful, though there is some value in doing that...
,
Jun 3 2016
We haven't changed anything in awhile.
,
Jun 3 2016
Maybe there is somethings wrong with one specific machine?
,
Jun 3 2016
According to the original report, it happened on three different VMs: https://build.chromium.org/p/tryserver.chromium.mac/builders/ios-simulator-gn/builds/15998 https://build.chromium.org/p/tryserver.chromium.mac/builders/ios-simulator-gn/builds/15930 https://build.chromium.org/p/tryserver.chromium.mac/builders/ios-simulator-gn/builds/15585
,
Jun 4 2016
+rohitrao who owns iossim. Rohit, does this error look familiar to you at all? Found in the OWNERS file here: https://chromium.googlesource.com/chromium/src/+/master/testing/iossim/OWNERS
,
Jun 4 2016
(please re-add trooper if something urgent comes up that the trooper needs to address)
,
Jun 16 2016
Marking WontFix since it has gone away? Please re-open if that is not the case. |
|||||||||
►
Sign in to add a comment |
|||||||||
Comment 1 by jbroman@chromium.org
, Jun 3 2016Summary: "ios_chrome_unittests" is flaky (AppLaunchError: Simulator failed to start) (was: "ios_chrome_unittests" is flaky)