Cuckoo: Builds failing on Bitrise with stack Xcode 13.3.x (beta)

Bitrise stack “Xcode 13.3.x (beta) on macOS 12.2 (Monterey)” is failing builds with the following error message

Last lines of the build log:
Script path: /Users/vagrant/git/CRM
xargs: /Users/vagrant/git/CRM/cuckoo_generator: terminated with signal 4; aborting
Command PhaseScriptExecution failed with a nonzero exit code

Test session results, code coverage, and logs:
	/var/folders/62/0p2cg52j6r16xjxfqch4vgt40000gn/T/XCUITestOutput573379856/Test.xcresult

Testing failed:
	Command PhaseScriptExecution failed with a nonzero exit code
	Testing cancelled because the build failed.

** TEST FAILED **

The following build commands failed:
	PhaseScriptExecution Cuckoo\ Run\ Script /Users/vagrant/Library/Developer/Xcode/DerivedData/CRM-gfmkxxwjwsejasaegkkqxuwbswfa/Build/Intermediates.noindex/CRM.build/Debug-iphonesimulator/CRMTests.build/Script-3312E990D1E37BD0916B2578.sh (in target 'CRMTests' from project 'CRM')
(1 failure)

Recently included the following conditionals in the Cuckoo Run Script which seems to have no improvement

if [ $ACTION == "indexbuild" ]; then
  echo "Not running Cuckoo generator during indexing."
  exit 0 
fi

# Skip for preview builds
if [ "${ENABLE_PREVIEWS}" = "YES" ]; then
  echo "Not running Cuckoo generator during preview builds."
  exit 0
fi

About this issue

  • Original URL
  • State: closed
  • Created 2 years ago
  • Comments: 38 (2 by maintainers)

Commits related to this issue

Most upvoted comments

Ok, after exploring why only some files were making the script crash. I found out that if the protocol defines a function without a label, it crashes.

func foo(_ bar: Bar) // It crashes
func foo(bar: Bar) // All good

We typically prepare for upcoming versions of Xcode/iOS as soon as they become available. We try to catch these issues proactively. This is sort of a heads up, but would also like to resolve this as we have nightly builds that run specs against the latest stacks (including betas)

Hi @MatyasKriz, using cocoapods here, got the Cuckoo 1.7.0 release. It’s working for me. Thank you very much for the fix.

Simply download the latest run script from master and run it with arguments --download --clean. Let me know if that works for you.

It looks like the run script on master hasn’t been updated in 2 years

I see, time flies. 😅 Though the current version seems to work without problems.

@ajpallares thanks for the thorough analysis. 🙂 Don’t worry about it, this kind of stuff happens. I’m glad you’re here to help us push through. I’ll release 1.7.1 without the SPM changes for now, so there’s no pressure at all.

I see, that’s my bad. The change here is actually in the generator, not Cuckoo itself, but the binary hasn’t been uploaded for some reason. I’ve fixed that, so now the newest one should get downloaded. 🙂