-
Notifications
You must be signed in to change notification settings - Fork 1.3k
Fix nightly tests #2650
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
Fix nightly tests #2650
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks!
|
You'll have to bump the nightly version in the GitHub actions workflow file to fix CI. |
|
Fixed. I thought it pulled latest nightly (since I didn't find any version in the CI file) and I thought that's why I saw breakage in the other PR. Turns out there were just actual errors and when I tried to run the tests locally I must have ran them from the parent directory so the rust-toolchain file was ignored. |
|
cc @jplatte Now with an earlier nightly toolchain I got: Is it possible to switch the feature gate by different nightly toolchain? Or how can I work around this compile error. Bump nightly toolchain can be a significant change for our project (new ICEs, features incompatible, although we'll do it sooner or later, but I'm trying not to couple everything. I'm bumping axum from 0.6 to 0.7 now) |
|
I use |
I think it's possible but I'd rather not. Instead, we can have an explicit feature to turn that attribute on. I'm thjnking something like For now, you can pin the version. Also I would recommend checking a lockfile into git when you are using nightly. |
Motivation
The
diagnostic_namespacewas stabilized in nightly 1.78 and gives warnings. Some trybuild tests were broken.Solution
The
diagnostic_namespacefeature was removed and tests were updated automatically.