Xcode Test step fails with


#1

Bitrise Build Issue Report template

Description of the issue

▸ Test Succeeded
xcode test exit code: -1
xcode test failed, error: signal: abort trap
Last lines of the Xcode's build log:
 15   __64-[SimDevice shutdownAsyncWithCompletionQueue:completionHandler:]_block_invoke (in CoreSimulator)
 16   __67-[SimDevice bootstrapQueueAsync:completionQueue:completionHandler:]_block_invoke (in CoreSimulator)
 17   _dispatch_call_block_and_release (in libdispatch.dylib)
 18   _dispatch_client_callout (in libdispatch.dylib)
 19   _dispatch_queue_serial_drain (in libdispatch.dylib)
 20   _dispatch_queue_invoke (in libdispatch.dylib)
 21   _dispatch_root_queue_drain_deferred_wlh (in libdispatch.dylib)
 22   _dispatch_workloop_worker_thread (in libdispatch.dylib)
 23   _pthread_wqthread (in libsystem_pthread.dylib)
 24   start_wqthread (in libsystem_pthread.dylib)
If you can't find the reason of the error in the log, please check the raw-xcodebuild-output.log
The log file is stored in $BITRISE_DEPLOY_DIR, and its full path
is available in the $BITRISE_XCODE_RAW_TEST_RESULT_TEXT_PATH environment variable.
You can check the full, unfiltered and unformatted Xcode output in the file:
/Users/vagrant/deploy/raw-xcodebuild-output.log
If you have the Deploy to Bitrise.io step (after this step),
that will attach the file to your build as an artifact!

Environment:

Where did the issue happen?

Xcode 10.1.x

Which build Step causes the issue and which version of the step?

Xcode Test

Reproducibility

  • Does a “Rebuild” help? (You can trigger a rebuild from the Build’s page, by clicking the “Rebuild” button in the top right corner of a finished build) : YES
  • Does a rebuild without caches help? (You can remove the Cache:Pull and Cache:Push steps temporarily to not to use the cache, or you can delete all the caches on the Settings tab of the app. : YES
  • Does the issue happen sporadically, or every time? : Sporadically, quite random.
  • Does upgrading the build Step to the latest version help? : NO
  • When did the issue start? : Around switching to Xcode 10.1 stack.

Build log


#2

Solution: set Run the test in headless mode? to no in the Xcode Test step’s Debug input section:

Or in YAML mode:

    - xcode-test:
        inputs:
        - headless_mode: 'no'

#3

We’re seeing this too


#4

Did the included solution help @yonaskolb?


#5

Yes, seems to. Just a shame to lose headless mode


#6

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.