-
Notifications
You must be signed in to change notification settings - Fork 198
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
Don't cache the detected rustc-version, it's cheap enough to requery #2306
Conversation
(Waiting to check that the test fails before I push the fix, I can't run build tests locally at the moment) |
Going to give it a try locally. |
ef24168
to
2dd86d1
Compare
Still not working for me. Same error. |
converting to draft until it works (coming from the comments, and the change itself that only adds tests :) |
For the test, wouldn't it be better to have a new CI testsuite which starts the DB and then run the |
Draft PRs don't have tests run on them |
That's a lot more maintenance work than having it run via the existing infrastructure. The test I have written using two separate |
The CI passed iirc and it doesn't work locally, so I'm not sure it's exactly the same. |
CI build-tests was skipped, it's not meant to pass, this is just adding a test that should fail, I haven't pushed the fix for it. |
Oh fun, out of disk space error (which shows as skipped instead of failed, which is a ✔️ because of GHA's weirdness about states). |
That would be new to me, and a thing I would fix. Here's a draft PR with tests that are run: #2292 |
Ah, they aren't run with some configs. I had seen the CI/build result was skipped and assumed that was caused by the change to draft status, didn't notice it was out-of-disk till inspecting the second attempt. |
... where is the button to mark as draft hiding EDIT: Under reviewers of course, such an obvious place to hide it 🙃 |
2dd86d1
to
7c007fc
Compare
Good, the test failed with the expected error message: https://github.com/rust-lang/docs.rs/actions/runs/6811549892/job/18522282940?pr=2306 |
🎉 |
c1453bc
to
f8d8d8b
Compare
Fixes the issue from #2296 (comment), running local builds still fails after updating the toolchain in a separate invocation because it does not attempt to detect the version.