fastlane: Skip Xcodebuild "Finished requesting crash reports. Continuing with testing."
Question Checklist
- Updated fastlane to the latest version
- I read the Contribution Guidelines
- I read docs.fastlane.tools
- I searched for existing GitHub issues
Question Subject
Skip requesting crash reports from Apple when running tests with Gym (or at least, have an option to do so).
Question Description
I’m running a CI machine with the Xcode.
The tests are triggered using fastlane gym. I see this line in the output:
2019-05-27 16:04:28.417 xcodebuild[54605:1482269] [MT] IDETestOperationsObserverDebug: (A72DBEA3-D13E-487E-9D04-5600243FF617) Finished requesting crash reports. Continuing with testing.
This operation takes some time (about a minute) to complete. As far, as I understand, the Xcode requests crash reports from Apple to show in the “Organizer” window.
Since this is a CI machine, the crash reports will never be viewed on it and this step could be skipped completely how can I skip it?
About this issue
- Original URL
- State: closed
- Created 5 years ago
- Reactions: 5
- Comments: 29 (2 by maintainers)
Still
Sent with GitHawk
Have the same situation: XCUITest + parallel running + Xcode 10.2.1 Stucks on “Finished requesting crash reports. Continuing with testing.”
These timeouts eat up any gains from parallelising tests to begin with.
I have the same situation when try to run iOS XCUITest. The scheme have “Execute in parallel on Simulator”.
When I run tests with faslane they hang with these logs:
[10:36:34]: Running Tests: ▸ Touching oneAppUITests.xctest (in target: oneAppUITests) [10:36:35]: ▸ 2019-09-03 10:36:35.825 xcodebuild[6686:67746] IDETestOperationsObserverDebug: Writing diagnostic log for test session to: [10:36:35]: ▸ /Users/userName/Library/Developer/Xcode/DerivedData/oneApp-drdvtlzcamctnjaceoefmlfsqfbp/Logs/Test/Run-oneApp-2019.09.03_10-30-35-+0300.xcresult/3_Test/Diagnostics/oneAppUITests-C89C9D84-18CC-4C4F-AEE5-ECDA5DD6412C/oneAppUITests-464B4A8A-5C1E-4632-92D5-F8FE18DE5544/Session-oneAppUITests-2019-09-03_103635-BFGgm3.log [10:36:35]: ▸ 2019-09-03 10:36:35.825 xcodebuild[6686:49333] [MT] IDETestOperationsObserverDebug: (6E115D89-F465-45A5-B298-60B247FE7B06) Beginning test session oneAppUITests-6E115D89-F465-45A5-B298-60B247FE7B06 at 2019-09-03 10:36:35.825 with Xcode 10E1001 on target <DVTiPhoneSimulator: 0x7f86fba81030> { [10:36:35]: ▸ SimDevice: Clone 1 of iPhone X (14753175-B882-4EA6-87D8-1A7A56ABF959, iOS 12.2, Shutdown) [10:36:35]: ▸ } (12.2 (16E226)) [10:36:49]: ▸ 2019-09-03 10:36:49.400 xcodebuild[6686:49333] [MT] IDETestOperationsObserverDebug: (6E115D89-F465-45A5-B298-60B247FE7B06) Finished requesting crash reports. Continuing with testing. [10:36:54]: ▸ 2019-09-03 10:36:54.568 xcodebuild[6686:49333] [MT] IDETestOperationsObserverDebug: (ECBCDD1C-3DE8-48C1-A29A-97037B539885) Beginning test session oneAppUITests-ECBCDD1C-3DE8-48C1-A29A-97037B539885 at 2019-09-03 10:36:54.569 with Xcode 10E1001 on target <DVTiPhoneSimulator: 0x7f86f5af4170> { [10:36:54]: ▸ SimDevice: Clone 2 of iPhone X (15A41C4F-4BF9-4577-8CFA-FDD3C2FBE008, iOS 12.2, Shutdown) [10:36:54]: ▸ } (12.2 (16E226)) [10:36:54]: ▸ 2019-09-03 10:36:54.569 xcodebuild[6686:67806] IDETestOperationsObserverDebug: Writing diagnostic log for test session to: [10:36:54]: ▸ /Users/userName/Library/Developer/Xcode/DerivedData/oneApp-drdvtlzcamctnjaceoefmlfsqfbp/Logs/Test/Run-oneApp-2019.09.03_10-30-35-+0300.xcresult/3_Test/Diagnostics/oneAppUITests-C89C9D84-18CC-4C4F-AEE5-ECDA5DD6412C/oneAppUITests-D7E29188-9F98-4FBD-875F-2468C948F59E/Session-oneAppUITests-2019-09-03_103654-Xs6HZG.log [10:36:54]: ▸ 2019-09-03 10:36:54.754 xcodebuild[6686:68887] IDETestOperationsObserverDebug: Writing diagnostic log for test session to: [10:36:54]: ▸ /Users/userName/Library/Developer/Xcode/DerivedData/oneApp-drdvtlzcamctnjaceoefmlfsqfbp/Logs/Test/Run-oneApp-2019.09.03_10-30-35-+0300.xcresult/3_Test/Diagnostics/oneAppUITests-C89C9D84-18CC-4C4F-AEE5-ECDA5DD6412C/oneAppUITests-9EBB97B0-507F-44A6-A71C-3D689A0D8E69/Session-oneAppUITests-2019-09-03_103654-dBUiaV.log [10:36:54]: ▸ 2019-09-03 10:36:54.754 xcodebuild[6686:49333] [MT] IDETestOperationsObserverDebug: (72E5669E-0869-458A-B9CE-4159AFEA903E) Beginning test session oneAppUITests-72E5669E-0869-458A-B9CE-4159AFEA903E at 2019-09-03 10:36:54.755 with Xcode 10E1001 on target <DVTiPhoneSimulator: 0x7f86fbc0bf40> { [10:36:54]: ▸ SimDevice: Clone 3 of iPhone X (341B57AC-0FD2-4303-9D27-AA244A4373DD, iOS 12.2, Shutdown) [10:36:54]: ▸ } (12.2 (16E226)) [10:38:35]: ▸ 2019-09-03 10:38:35.962 xcodebuild[6686:49333] [MT] IDETestOperationsObserverDebug: (ECBCDD1C-3DE8-48C1-A29A-97037B539885) Finished requesting crash reports. Continuing with testing. [10:38:36]: ▸ 2019-09-03 10:38:36.076 xcodebuild[6686:49333] [MT] IDETestOperationsObserverDebug: (72E5669E-0869-458A-B9CE-4159AFEA903E) Finished requesting crash reports. Continuing with testing.✅ fastlane environment ✅
Stack
System Locale
fastlane files:
`./fastlane/Fastfile`
`./fastlane/Appfile`
fastlane gems
Loaded fastlane plugins:
No plugins Loaded
Loaded gems
generated on: 2019-09-03
+1
This step causes our CI server to pause for 2-10 minutes on every run. It’s super-annoying.
+1
I am not aware of an existing way to do this. If
xcodebuildsomehow supports this, we could of course trivially implement this in fastlane as a new option.Related: https://stackoverflow.com/questions/56326847/xcodebuild-skip-finished-requesting-crash-reports-continuing-with-testing