New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fastlane reports succes when xcodebuild fails #20685
Comments
Reopening #20496 |
There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Friendly reminder: contributions are always welcome! Check out CONTRIBUTING.md for more information on how to help with This issue will be auto-closed if there is no reply within 1 month. |
Pls, check the resolution of this issue in the MR #20739 |
New Regression Checklist
Regression Information
2.201.0
2.200.0
Regression Description
This is one of the most craziest heizenbugs i had :)
So I have a Xcode project with some tests on it and a pipeline with separate build-for-testing and test jobs.
fastlane reports succesful build-for-testing lane execution when scan definitely should fail getting exit status 65 from xcodebuild. It sometimes happens randomly and as far as understand depends on which files are compiled first by xcodebuild.
So I digged in scan sources and found that error_handler matches xcode output against word 'Executed'. If any file has 'Executed' pattern in its path, this match fires and no exception about build failure will be raised.
I've checked previous fastlane versions and found this issue on all of them starting from 2.201.0
Demo project with this bug
Build reproducing this bug
Complete output when running fastlane, including the stack trace and command used
Environment
The text was updated successfully, but these errors were encountered: