-
Notifications
You must be signed in to change notification settings - Fork 680
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
Ported cargo-check-each-crate-macos
to GitHub actions
#5386
Conversation
53af713
to
996dbd2
Compare
@alvicsam @lovelaced @mordamax this PR is ready for review. I have tried both with Both of them can complete the job. The first one takes more than 90 minutes, the second one takes around 45 minutes. Which one should I assign as the runner for this job? |
What is the cost basis for each? (which one is cheaper to run given the time it takes :D?) |
From the documentation it seems that the costs per minute are:
So, seeing the time it takes, we could summarize the total price:
As the |
9cfb14d
to
9b7ffbf
Compare
2787457
to
d1b58f4
Compare
A workflow already exists named `Check Cargo Check Runtimes`. We will add this job into that workflow
Replaced it for brew's installation
Co-authored-by: Bastian Köcher <git@kchr.de>
39c98eb
to
103e1d2
Compare
It is already available in the needed step.
I suggest closing this PR because this one was already merged |
Closed in favour of #5690 |
Resolves paritytech/ci_cd#1021
Ported the gitlab job to run on GitHub actions.