Skip to content
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

CI: pin nightly; test minimal-versions on stable #378

Merged
merged 1 commit into from
Oct 26, 2023
Merged

Conversation

tarcieri
Copy link
Member

  • Pins to nightly-2023-10-01 to prevent regressions
  • On minimal-versions only uses nightly to resolve versions, and runs tests on stable instead

This is a workaround for build failures we're seeing due to a recent nightly regression. See:

https://github.com/RustCrypto/RSA/actions/runs/6655788342/job/18086838437?pr=377

https://github.com/RustCrypto/RSA/actions/runs/6655788342/job/18086838800?pr=377

- Pins to nightly-2023-10-01 to prevent regressions
- On `minimal-versions`, only uses nightly to resolve versions, and runs
  tests on stable instead
@tarcieri tarcieri mentioned this pull request Oct 26, 2023
Copy link
Member

@newpavlov newpavlov left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It looks good as a temporary measure. But I think we should revert it after the regression is fixed. Do we know if someone create a Rust issue for it?

UPD: The issue is rust-lang/rust#117120 and it looks like it was already fixed. We probably can simply wait for a future Nightly release with the fix.

@tarcieri
Copy link
Member Author

I think it would be good to change minimal-versions to always test using stable after using nightly to resolve the lockfile

@tarcieri tarcieri merged commit ec1cebf into master Oct 26, 2023
9 checks passed
@tarcieri tarcieri deleted the ci/pin-nightly branch October 26, 2023 16:04
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants