Travis failed with error 65

Question

I have set up Travis CI on GitHub. I use it to check my commits for an iOS app. The problem is that I very often and accidentally receive error message 65. I still have to find a solution.

When I restart the task 2-3 times after its failure, it passes in 90% of cases.

I also had a problem with magazines that are too verbose for Travis (> 4MB), but I added xcpretty to fix this.

Errors I took from the log:

 ... Generating 'XYZ.app.dSYM' ❌ error: couldn't remove '/Users/travis/Library/Developer/Xcode/DerivedData/XYZ-aaltcjvmshpmlufpmzdsgbernspl/Build/Products/Debug-iphonesimulator/XYZ.app/SomeName.storyboardc' after command failed: Directory not empty ... 

And then at the end of Travis magazine:

 Testing failed: The file "056-Jj-FAu-view-XmS-Ro-0cO.nib" couldn't be opened because there is no such file. error: couldn't remove '/Users/travis/Library/Developer/Xcode/DerivedData/XYZ-aaltcjvmshpmlufpmzdsgbernspl/Build/Products/Debug-iphonesimulator/XYZ.app/SomeName.storyboardc' after command failed: Directory not empty error: lipo: can't move temporary file: /Users/travis/Library/Developer/Xcode/DerivedData/XYZ-aaltcjvmshpmlufpmzdsgbernspl/Build/Products/Debug-iphonesimulator/XYZ.app.dSYM/Contents/Resources/DWARF/XYZ to file: /Users/travis/Library/Developer/Xcode/DerivedData/XYZ-aaltcjvmshpmlufpmzdsgbernspl/Build/Products/Debug-iphonesimulator/XYZ.app.dSYM/Contents/Resources/DWARF/XYZ.lipo (No such file or directory) Command /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/dsymutil emitted errors but did not return a nonzero exit code to indicate failure ** TEST FAILED ** The following build commands failed: LinkStoryboards LinkStoryboards (2 failures) The command "./scripts/build.sh" exited with 65. 

I use Xcode 8 both Xcode and Travis settings.

Answer 1

Ah, a good question. Sometimes, the xcodebuild steps that fail during the code synchronization phase can be eliminated with travis_retry - Travis will repeat the step 3 times for any non-zero exit state, which should reduce the need to manually restart it. This section provides some suggested code snippets in the travis-ci/travis-ci GitHub problem . Good luck

Answer 2

If you use error code 65 (from random crashes), here you can run the command at the end of your xcodebuild (assuming you run the tests) to get more consistent results:

(XCODEBUILD_COMMAND_HERE) | awk 'BEGIN {success=0} $0 ~ /.* tests, with 0 failures \(.*/ {success=1} {print $0} END {if(success==0){exit 1}}

This appears in the text of the tests, with 0 failures ( output tests, with 0 failures ( , therefore, the xcodebuild text output is xcodebuild instead of the xcodebuild status code to determine success.

Note. Keep in mind that if you do something like NSLog(' tests, with 0 failures ('); in your code, you do a false positive, it is very unlikely if this happens by accident. You may need to update tests, with 0 failures ( in an awk script between xcodebuild updates. But, having consistent results with xcodebuild is definitely worth the price.