Skip to content
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

Rollup of 6 pull requests #91983

Closed
wants to merge 16 commits into from

Conversation

matthiaskrgr
Copy link
Member

Successful merges:

Failed merges:

r? @ghost
@rustbot modify labels: rollup

Create a similar rollup

orlp and others added 16 commits October 30, 2021 09:31
…ottmcm

Added next_up and next_down for f32/f64.

This is a pull request implementing the features described at rust-lang/rfcs#3173.
…rop-since, r=kennytm

Fix since attribute for const_manually_drop feature

const_manually_drop was stabilized in 1.32 as mentioned in
https://github.com/rust-lang/rust/blob/master/RELEASES.md#version-1320-2019-01-17
…riplett

Add `io::Error::other`

This PR adds a small utility constructor, `io::Error::other`, a shorthand for `io::Error::new(io::ErrorKind::Other, err)`, something I find myself writing often.

For some concrete stats, a quick search on [grep.app](https://grep.app) shows that more than half of the uses of `io::Error::new` use `ErrorKind::Other`:
```
Error::new\((?:std::)?(?:io::)?ErrorKind:: => 3,898 results
Error::new\((?:std::)?(?:io::)?ErrorKind::Other => 2,186 results
```
update stdarch

2 commits in d219ad6..0716b22
2021-12-9 23:50:37 +0000 to 2021-12-14 16:17:57 +0100
 * Fix a bunch of typos ([Fix a bunch of typos stdarch#1267](rust-lang/stdarch#1267))
 * Stabilize armv8 neon instruction set on aarch64 ([Stabilize armv8 neon instruction set on aarch64 stdarch#1266](rust-lang/stdarch#1266))

The update stabilizes armv8 neon instructions on aarch64. rust-lang#90972
…lacrum

link to pref_align_of tracking issue

If we are not going to remove this intrinsic (rust-lang#90877), I think we should at least have a place to centralize discussion around it, so here we go. Intrinsics don't have their own separate features and usually we instead use the public method for tracking it, but this one does not have such a method... so the tracking issue is just a regular link. (And then we sue it for the const part as well.)
@rustbot rustbot added the rollup A PR which is a rollup label Dec 16, 2021
@matthiaskrgr
Copy link
Member Author

@bors r+ rollup=never p=6

@bors
Copy link
Contributor

bors commented Dec 16, 2021

📌 Commit a96c5bc has been approved by matthiaskrgr

@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 Dec 16, 2021
@bors
Copy link
Contributor

bors commented Dec 16, 2021

⌛ Testing commit a96c5bc with merge abd852c649501a9f6d3eb03b84a911d31d8362e1...

@rust-log-analyzer
Copy link
Collaborator

The job dist-i586-gnu-i586-i686-musl failed! Check out the build log: (web) (plain)

Click to see the possible cause of the failure (guessed by this bot)
test sync::mpsc::tests::stress_recv_timeout_two_threads ... ok

failures:

---- f32::tests::test_next_down stdout ----
thread 'f32::tests::test_next_down' panicked at 'assertion failed: `(left == right)`
 right: `2140493141`', library/std/src/f32/tests.rs:358:9

---- f32::tests::test_next_up stdout ----
---- f32::tests::test_next_up stdout ----
thread 'f32::tests::test_next_up' panicked at 'assertion failed: `(left == right)`
 right: `2140493141`', library/std/src/f32/tests.rs:321:9

---- f64::tests::test_next_down stdout ----
---- f64::tests::test_next_down stdout ----
thread 'f64::tests::test_next_down' panicked at 'assertion failed: `(left == right)`
 right: `9219619037165300394`', library/std/src/f64/tests.rs:347:9

---- f64::tests::test_next_up stdout ----
---- f64::tests::test_next_up stdout ----
thread 'f64::tests::test_next_up' panicked at 'assertion failed: `(left == right)`
 right: `9219619037165300394`', library/std/src/f64/tests.rs:310:9


failures:
failures:
    f32::tests::test_next_down
    f32::tests::test_next_up
    f64::tests::test_next_down
    f64::tests::test_next_up

test result: FAILED. 915 passed; 4 failed; 0 ignored; 0 measured; 0 filtered out; finished in 10.38s

error: test failed, to rerun pass '-p std --lib'


command did not execute successfully: "/checkout/obj/build/x86_64-unknown-linux-gnu/stage0/bin/cargo" "test" "--target" "i686-unknown-linux-musl" "-Zbinary-dep-depinfo" "-j" "16" "--release" "--locked" "--color" "always" "--features" "panic-unwind backtrace compiler-builtins-c" "--manifest-path" "/checkout/library/test/Cargo.toml" "-p" "std" "--"


Build completed unsuccessfully in 0:35:25

@bors
Copy link
Contributor

bors commented Dec 16, 2021

💔 Test failed - checks-actions

@bors bors added S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. and removed S-waiting-on-bors Status: Waiting on bors to run and complete tests. Bors will change the label on completion. labels Dec 16, 2021
@matthiaskrgr matthiaskrgr deleted the rollup-xgtw5uo branch January 2, 2022 22:34
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
rollup A PR which is a rollup S-waiting-on-review Status: Awaiting review from the assignee but also interested parties.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

10 participants