Xcode 9 - Xcode Test build twice

Question & Answer Builds
,
1

Bitrise Build Issue Report template

Description of the issue

Since the update to Xcode 9, the Xcode test step compile the project twice.
This is the message I can read at the end of the first build attempt

Automatic retry reason found in log: Early unexpected exit, operation never finished bootstrapping - no restart will be attemptede
isAutomaticRetryOnReason=true - retrying…
Deleting existing xcpretty output: /Users/vagrant/deploy/xcode-test-results-Saks-Development.htmle
Running the tests…e

Environment:

On Bitrise.io1, stack: Xcode 9.0.x, on macOS 10.12 (Sierra)

Step: xcode-test @ 1.18.7

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) : NO
  • 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. : NO
  • If you have multiple different build configurations (workflows), does the issue affect all/more than one? : NO
  • If it’s an issue which happens sporadically, what’s the frequency? (e.g. Once a day ; about x% of the builds) : 100%
  • Does upgrading the build Step to the latest version help? : NO
  • When did the issue start? : since Xcode update to Xcode 9
1 Like
2

Hi @glanza,
the step has an input: (Experimental) Rerun test, when it fails?, if you set this input to yes the step will rerun the test if the first attempt failed with specific errors.

If one of the mentioned errors appear in the log, most of the times rerunning the test will solve the issue.

If you want to avoid from this behavious set the (Experimental) Rerun test, when it fails? input’s value to no.

1 Like
3

Hi, it is already no.

4

@glanza mi previous answer was not correct, sorry about that!

The step input: (Experimental) Rerun test, when it fails? is not related to the Automatic retry reasons.

We designed the step, to automatically rerun the test, it it failed because of an issue, which is not related to the test run. We collect these issues and we call it to: Automatic retry reasons, these issues are related to the ios simulator (may its not booted yet, or not setup correctly yet). You can not trun off this retry, since your test would fail, even if its not because of your test cases…

Using (Experimental) Rerun test, when it fails? step input you can control if the step should rerun the test if it failed with any issue or not.

1 Like
5

Mine seems to be making double builds too… I get 2 sets of exported assets. None of the rerun steps are enabled.

6

@JaredSartin please create a separate issue report at #issues:build-issues as that’s most likely a different issue (2 sets of exported assets)