-
Notifications
You must be signed in to change notification settings - Fork 1k
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
Use build-std=core
instead of build-std
alone
#3292
Conversation
r? @JohnTitor (rustbot has picked a reviewer for you, use r? to override) |
have you tested locally that |
Yes, tested with two targets:
Do you want me to test something else just in case? |
that seems fine - but just fyi most of the failures i mentioned #3289 (comment) are probably going to continue to be issues |
It's fine for now. I can take a look at them later on, it's less pressing than the current state. ^^' |
Thanks! @bors r+ |
☀️ Test successful - checks-actions, checks-cirrus-freebsd-12, checks-cirrus-freebsd-13, checks-cirrus-freebsd-14 |
1 similar comment
☀️ Test successful - checks-actions, checks-cirrus-freebsd-12, checks-cirrus-freebsd-13, checks-cirrus-freebsd-14 |
👀 Test was successful, but fast-forwarding failed: 422 Changes must be made through a pull request. |
Anything I need to do about this? |
The commit was pushed anyway so we don't have to do anything (I believe this is a bug/weird behavior of bors, I remember seeing this message on the rust repo). EDIT: Well, it seems the message is a bit different from what I've ever seen. Anyway, the main branch should have this change and we can call it a day unless any additional commits are missing. |
Noted, thanks for checking! Don't hesitate if I need to fix something. |
Should help with #3289.