-
Notifications
You must be signed in to change notification settings - Fork 263
WIP: Split crates requiring nightly Rust into separate unstable
workspace
#1227
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
base: master
Are you sure you want to change the base?
Conversation
Marking as WIP, because it'll need some CI debugging to make sure tests don't fail. |
Also I merged #1225 so you can rebase now. |
Currently attempting a full implementation of #1220. Still WIP; will work on ensuring CI passes. |
unstable
workspace
Side note: |
bb14e51
to
444ca79
Compare
@kkysen EDIT: Seems to be working again. |
@kkysen I just realized that the Docker images probably don't get rebuilt as a result of this pipeline; I updated the scripts that build Docker images, and then the failure is happening because the CI runs using the old Docker images. I think this may be easiest to fix by going ahead and switching away from Azure pipelines. I'll work towards that. |
It's used in a test here: c2rust/c2rust-analyze/tests/analyze.rs Line 74 in 4b7691e
As long as you keep the relative paths the same, it should still work fine. We in general gitignored *.bc files but added this one manually for this one test.
|
Oh yes, that's always been one of the very annoying pain points with Azure pipelines. We have to update the docker images separately, and so we can't test multiple in CI at the same time either. One of the many reasons I've always wanted to move away from Azure pipelines. I agree it's probably easier to just move to GitHub Actions in one go and things will work better there. Thanks again for helping with all of this! |
No description provided.