Skip to content

Rollup of 8 pull requests #75113

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

Closed
wants to merge 16 commits into from

Conversation

Manishearth
Copy link
Member

Successful merges:

Failed merges:

r? @ghost

carbotaniuman and others added 16 commits July 29, 2020 10:38
The purpose of the auto-fallible job is to run builders that are likely
to fail on CI without gating on them. Having fast-fail enabled there
kinda defeats the purpose, as if one of them fails we can't monitor the
outcome of the other ones.

This was prompted by the aarch64-gnu builder consistently failing due to
a broken test, preventing us from seeing if the macOS spurious failure
is fixed.
riscv64 has an LLVM bug that makes rust-analyzer not build.
add `unsigned_abs` to signed integers

Mentioned on rust-lang/rfcs#2914

This PR simply adds an `unsigned_abs` to signed integers function which returns the correct absolute value as a unsigned integer.
…-obk

Lint path statements to suggest using drop when the type needs drop

Fixes rust-lang#48852. With this change the current lint description doesn't really fit entirely anymore I think.
…ark-Simulacrum

Clarify reuse of a BTreeMap insert support function and treats split support likewise

r? @Mark-Simulacrum
…r=lcnr

Do not trigger `unused_braces` for `while let`

Follow-up for rust-lang#75031
r? @lcnr
Use u32::from_le_bytes to fix a FIXME

`u32::from_be_bytes` has been const stable since 1.44.
…Mark-Simulacrum

ci: disable fast-fail on auto-fallible

The purpose of the auto-fallible job is to run builders that are likely to fail on CI without gating on them. Having fast-fail enabled there kinda defeats the purpose, as if one of them fails we can't monitor the outcome of the other ones.

This was prompted by the aarch64-gnu builder consistently failing due to a broken test, preventing us from seeing if the macOS spurious failure is fixed.

r? @Mark-Simulacrum
…r=matklad

Disable building rust-analyzer on riscv64

riscv64 has an LLVM bug that makes rust-analyzer not build. Should permit future rust-analyzer ups (e.g., rust-lang#74813) to land.
@Manishearth
Copy link
Member Author

@rustbot modify labels: +rollup
@bors r+ rollup=never p=5

@bors
Copy link
Collaborator

bors commented Aug 3, 2020

📌 Commit 5aaf07a has been approved by Manishearth

@rustbot rustbot added the rollup A PR which is a rollup label Aug 3, 2020
@bors bors added the S-waiting-on-bors Status: Waiting on bors to run and complete tests. Bors will change the label on completion. label Aug 3, 2020
@bors
Copy link
Collaborator

bors commented Aug 3, 2020

⌛ Testing commit 5aaf07a with merge 5643c6820ef9b30657827c01a42bba49c8c52197...

@cuviper
Copy link
Member

cuviper commented Aug 3, 2020

Can you remove #75086? I think that is incorrect for big-endian, but sadly we don't test that in CI...

@Manishearth Manishearth closed this Aug 3, 2020
# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
rollup A PR which is a rollup S-waiting-on-bors Status: Waiting on bors to run and complete tests. Bors will change the label on completion.
Projects
None yet
Development

Successfully merging this pull request may close these issues.