-
Notifications
You must be signed in to change notification settings - Fork 13.2k
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
[beta] branch 1.66 #103802
[beta] branch 1.66 #103802
Conversation
r? @thomcc (rustbot has picked a reviewer for you, use r? to override) |
|
Hey! It looks like you've submitted a new PR for the library teams! If this PR contains changes to any Examples of
|
@bors r+ rollup=never p=4 |
Could not determine reviewer from |
⌛ Testing commit e83be5d with merge 1546bd6b7ea4c7ae2379fdf5abc02b33157a08c3... |
💔 Test failed - checks-actions |
This comment has been minimized.
This comment has been minimized.
We don't distribute a miri build for beta/stable so it needs to be kept optional. In the future it likely makes sense to switch the miri *artifacts* to always be built, but the rustup component to not be included -- this will avoid some of this pain.
@bors r+ rollup=never p=4 |
☀️ Test successful - checks-actions |
@oli-obk any idea why it is even trying to build and package up Miri here? This is a beta branch build... Btw, AFAIK on master we are not ever testing Miri on i686-msvc. Is the same true for Clippy? Is this building and shipping Clippy on a target that we haven't even tested it? |
c2bb2e1 is the commit which fixed the miri problems on beta. As the description there says my guess is we'll want to either forward-port (to master) that as-is or an alternative which starts building but not distributing miri on beta/stable. |
This PR: