-
Notifications
You must be signed in to change notification settings - Fork 25
scan is twice slower on building code #35
Comments
Any feedback here? I find it funny how |
Looks like this is an issue. I tried running the xcodebuild command generated by scan directly without the build option. Just clean test. That seems to have cut the time in half. |
@yakimant did you test everything when removing the |
+1 for that. |
@KrauseFx I have been using xcodebuild to workaround this problem, instead of Scan. Currently, I am just passing the test command and have seen no issues with it in running our CI. Also, I compared the execution times of just xcodebuild test from fastlane and using Scan from fastlane. Scan is considerably slower because does a build and test. Hope this helps. I have a PR, if you think everything's alright - #62 |
I am also seeing not only everything built twice but the tests are being ran twice 😁 Looks like I am going to switch back to |
same here. |
Was able to speed things up thanks to #86 by using gym to build the binary first then run scan with the new |
Yeah, thanks for updating this issue, this is now implemented with #86 |
This issue was migrated to fastlane/fastlane#3353. Please post all further comments there.
|
As I see - the difference between my xcodebuild arguments and scan generated is:
I run
clean test
and scan runsclean build test
.I also see duplicates of compiling lines.
Is it building twice?
The text was updated successfully, but these errors were encountered: