Closed mtrezza closed 2 years ago
@cbaker6 do you remember why we run carthage still on CircleCI instead of GitHub Actions? I vaguely remember that it was about the resources because it takes a lot of time?
Yes, Carthage and some of the other obj-c builds take long time to finish, so it was left on circle
Got it. Maybe we should move this to Github Actions anyway; we don't see many CI runs here but it may be easier to debug in a single CI environment.
@parse-community/ios-sdk could anyone look into why carthage fails in CircleCI?
@mtrezza Not 100% sure about this, but IIRC, it times out.
I increased the no_output_timeout
to 30min in https://github.com/parse-community/Parse-SDK-iOS-OSX/pull/1657, let's see if that works
You were spot on, it requires a timeout of 1h, 30min even was too short. Carthage needs ~1h in total on CircleCI. It would be interesting to test this on GitHub Actions, because I suspect that CircleCI gives us little resources on the free plan and that may be one reason why it takes so long.
New Issue Checklist
Issue Description
Carthage build fails in CircleCI with error:
Steps to reproduce
See https://app.circleci.com/pipelines/github/parse-community/Parse-SDK-iOS-OSX/1328/workflows/78eee610-8187-4bda-9532-b1cd33142354/jobs/7471
Actual Outcome
Fails
Expected Outcome
Passes
Environment
Current master branch