-
-
Notifications
You must be signed in to change notification settings - Fork 17
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
Reduce CI time #55
Comments
For now, my goal with this issue is to complete all jobs within 30 minutes. The following jobs currently violate this.
As for |
As for
|
Part of #55. As mentioned in PRs in tokio and hyper, this is actually enough depth.
As for
|
- x86 Windows targets have been tested in test jobs in GitHub Actions. Also, we do not have Windows-specific code on x86. - RISC-V no-std targets have been tested in tools/no-std.sh. Also, we do not have M/C-extension-specific code on RISC-V. - Add x86_64-fortanix-unknown-sgx. - Move builds for some targets to test jobs in GitHub Actions. Targets for which we have architecture-specific code remain in the default targets list. Related to #55.
- x86 Windows targets have been tested in test jobs in GitHub Actions. Also, we do not have Windows-specific code on x86. - RISC-V no-std targets have been tested in tools/no-std.sh. Also, we do not have M/C-extension-specific code on RISC-V. - Add x86_64-fortanix-unknown-sgx. - Move builds for some targets to test jobs in GitHub Actions. Targets for which we have architecture-specific code remain in the default targets list. Related to #55.
- x86 Windows targets have been tested in test jobs in GitHub Actions. Also, we do not have Windows-specific code on x86. - RISC-V no-std targets have been tested in tools/no-std.sh. Also, we do not have M/C-extension-specific code on RISC-V. - Add x86_64-fortanix-unknown-sgx. - Move builds for some targets to test jobs in GitHub Actions. Targets for which we have architecture-specific code remain in the default targets list. Related to #55.
The slowest job in our CI (
build (nightly)
) takes over an hour. This is a really annoying situation, so let's investigate if we can shorten the time.The text was updated successfully, but these errors were encountered: