Rollup of 13 pull requests #136998

workingjubilee · 2025-02-14T01:09:02Z

Successful merges:

Make -O mean OptLevel::Aggressive #135439 (Make -O mean OptLevel::Aggressive)
Simplify rustc_span analyze_source_file #136460 (Simplify rustc_span analyze_source_file)
Put the alloc unit tests in a separate alloctests package #136642 (Put the alloc unit tests in a separate alloctests package)
add IntoBounds trait #136904 (add IntoBounds trait)
[AIX] expect EINVAL for pthread_mutex_destroy #136908 ([AIX] expect EINVAL for pthread_mutex_destroy)
Add profiling of bootstrap commands using Chrome events #136924 (Add profiling of bootstrap commands using Chrome events)
Use the right binder for rebinding PolyTraitRef #136951 (Use the right binder for rebinding PolyTraitRef)
add vendor directory to .gitignore #136956 (add vendor directory to .gitignore)
Use slice::fill in io::Repeat implementation #136967 (Use slice::fill in io::Repeat implementation)
alloc boxed: docs: use MaybeUninit::write instead of as_mut_ptr #136976 (alloc boxed: docs: use MaybeUninit::write instead of as_mut_ptr)
ci: switch loongarch jobs to free runners #136981 (ci: switch loongarch jobs to free runners)
Update backtrace #136992 (Update backtrace)
[cg_llvm] Remove dead error message #136993 ([cg_llvm] Remove dead error message)

r? @ghost
@rustbot modify labels: rollup

Only newlines and multibyte characters are actually relevant

for `range_into_bounds` feature, rust-lang#136903

Use the existing `fill` methods on slices instead of manually writing the fill loop.

For the tests that make use of internal implementation details, we include the module to test using #[path] in alloctests now.

In the deferred initialization pattern, the docs were needlessly going through as_mut_ptr().write() to initialize, which is unnecessary use of a pointer, needs to be inside an unsafe block, and may weaken alias analysis.

Make `-O` mean `OptLevel::Aggressive` Implementation of this MCP: rust-lang/compiler-team#828, changing the meaning of `-O` from `-Copt-level=2` to `-Copt-level=3`. This also renames `OptLevel::Default` to `OptLevel::More`, as `Default` no longer makes sense.

…yze, r=Noratrieb Simplify `rustc_span` `analyze_source_file` Simplifies the logic to what the code *actually* does, which is to just record newlines and multibyte characters. Checking for other ASCII control characters is unnecessary because the generic fallback doesn't do anything for those cases. Also uses a simpler (and more efficient) means of iterating the set bits of the mask.

…=cuviper Put the alloc unit tests in a separate alloctests package Same rationale as rust-lang#135937. This PR has some extra complexity though as a decent amount of tests are testing internal implementation details rather than the public api. As such I opted to include the modules containing the types under test using `#[path]` into the alloctests package. This means that those modules still need `#[cfg(test)]`, but the rest of liballoc no longer need it.

add `IntoBounds` trait for `range_into_bounds` feature Tracking issue: rust-lang#136903 ACP: rust-lang/libs-team#538

… r=joboet [AIX] expect `EINVAL` for `pthread_mutex_destroy` Calling `pthread_mutex_destory` on a mutex initalized with the static initializer macro `PTHREAD_MUTEX_INITIALIZER` will result in `EINVAL` if the mutex is not lock/unlocked prior to calling `pthread_mutex_destroy`.

Add profiling of bootstrap commands using Chrome events Since we now have support for tracing in bootstrap, and the execution of most commands is centralized within a few functions, it's quite trivial to also trace command execution, and visualize it using the Chrome profiler. This can be helpful both to profile what takes time in bootstrap and also to get a visual idea of what happens in a given bootstrap invocation (since the execution of external commands is usually the most interesting thing). This is how it looks: ![image](https://github.com/user-attachments/assets/3351489e-3a0f-4729-9082-5bf40c586d4b) I first tried to use [tracing-flame](https://github.com/tokio-rs/tracing/tree/master/tracing-flame), but the output wasn't very useful, because the event/stackframe names were bootstrap code locations, instead of the command contents. r? `@jieyouxu`

Use the right binder for rebinding `PolyTraitRef` Fixes rust-lang#136940 I committed a slightly different test which still demonstrates the issue.

add vendor directory to .gitignore

Use `slice::fill` in `io::Repeat` implementation Use the existing `fill` methods on slices instead of manually writing the fill loop.

…it, r=tgross35 alloc boxed: docs: use MaybeUninit::write instead of as_mut_ptr In the deferred initialization pattern, the docs were needlessly going through `as_mut_ptr().write()` to initialize, which is unnecessary use of a pointer, needs to be inside an `unsafe` block, and may weaken alias analysis.

…r=Kobzol ci: switch loongarch jobs to free runners try-job: dist-loongarch64-linux try-job: dist-loongarch64-musl

…ubilee Update backtrace This updates the backtrace submodule. 6 commits in f8cc6ac9acc4e663ecd96f9bcf1ff4542636d1b9..9d2c34e7e63afe1e71c333b247065e3b7ba4d883 2025-01-04 03:37:47 +0100 to 2025-02-13 14:14:18 -0800 - Various cleanups: rust-lang/backtrace-rs#673 - libunwind: Use builtin _Unwind_GetIP for NuttX on ARM platform: rust-lang/backtrace-rs#692 - remove outdated docs part on Dbghelp::ensure_open: rust-lang/backtrace-rs#696 - Cleanup Windows trace modules: rust-lang/backtrace-rs#697 - Attempt to fix ARM32 Windows: rust-lang/backtrace-rs#685 - Prepare backtrace for Rust 2024: rust-lang/backtrace-rs#700

…bilee [cg_llvm] Remove dead error message Part of rust-lang#135502 Discovered a dead error message in rustc_codegen_llvm, so removing it. r? `@Zalathar`

workingjubilee · 2025-02-14T01:09:12Z

@bors r+ rollup=never p=5

bors · 2025-02-14T01:09:14Z

📌 Commit f431f11 has been approved by workingjubilee

It is now in the queue for this repository.

bors · 2025-02-14T02:21:52Z

⌛ Testing commit f431f11 with merge 5f4e6f2...

…kingjubilee Rollup of 13 pull requests Successful merges: - rust-lang#135439 (Make `-O` mean `OptLevel::Aggressive`) - rust-lang#136460 (Simplify `rustc_span` `analyze_source_file`) - rust-lang#136642 (Put the alloc unit tests in a separate alloctests package) - rust-lang#136904 (add `IntoBounds` trait) - rust-lang#136908 ([AIX] expect `EINVAL` for `pthread_mutex_destroy`) - rust-lang#136924 (Add profiling of bootstrap commands using Chrome events) - rust-lang#136951 (Use the right binder for rebinding `PolyTraitRef`) - rust-lang#136956 (add vendor directory to .gitignore) - rust-lang#136967 (Use `slice::fill` in `io::Repeat` implementation) - rust-lang#136976 (alloc boxed: docs: use MaybeUninit::write instead of as_mut_ptr) - rust-lang#136981 (ci: switch loongarch jobs to free runners) - rust-lang#136992 (Update backtrace) - rust-lang#136993 ([cg_llvm] Remove dead error message) r? `@ghost` `@rustbot` modify labels: rollup

rust-log-analyzer · 2025-02-14T03:17:27Z

The job x86_64-gnu-aux failed! Check out the build log: (web) (plain)

Click to see the possible cause of the failure (guessed by this bot)

     Running unittests src/lib.rs (obj/build/x86_64-unknown-linux-gnu/stage1-std/miri/x86_64-unknown-linux-gnu/debug/deps/alloc-42cf5f79d9da7a10)
error[E0433]: failed to resolve: could not find `testing` in the crate root
##[error]  --> library/alloc/src/collections/btree/map/tests.rs:13:12
   |
13 | use crate::testing::crash_test::{CrashTestDummy, Panic};

error[E0433]: failed to resolve: could not find `testing` in the crate root
##[error]  --> library/alloc/src/collections/btree/map/tests.rs:13:12
   |
   |
13 | use crate::testing::crash_test::{CrashTestDummy, Panic};
   |
   |
   = note: duplicate diagnostic emitted due to `-Z deduplicate-diagnostics=no`
error[E0433]: failed to resolve: could not find `testing` in the crate root
##[error]  --> library/alloc/src/collections/btree/map/tests.rs:14:12
   |
   |
14 | use crate::testing::ord_chaos::{Cyclic3, Governed, Governor};

error[E0433]: failed to resolve: could not find `testing` in the crate root
##[error]  --> library/alloc/src/collections/btree/map/tests.rs:14:12
   |
   |
14 | use crate::testing::ord_chaos::{Cyclic3, Governed, Governor};
   |
   |
   = note: duplicate diagnostic emitted due to `-Z deduplicate-diagnostics=no`
error[E0433]: failed to resolve: could not find `testing` in the crate root
##[error]  --> library/alloc/src/collections/btree/map/tests.rs:14:12
   |
   |
14 | use crate::testing::ord_chaos::{Cyclic3, Governed, Governor};
   |
   |
   = note: duplicate diagnostic emitted due to `-Z deduplicate-diagnostics=no`
error[E0433]: failed to resolve: could not find `testing` in the crate root
##[error]  --> library/alloc/src/collections/btree/map/tests.rs:15:12
   |
   |
15 | use crate::testing::rng::DeterministicRng;

error[E0433]: failed to resolve: could not find `testing` in the crate root
##[error] --> library/alloc/src/collections/btree/set/tests.rs:5:12
  |
  |
5 | use crate::testing::crash_test::{CrashTestDummy, Panic};

error[E0433]: failed to resolve: could not find `testing` in the crate root
##[error] --> library/alloc/src/collections/btree/set/tests.rs:5:12
  |
  |
5 | use crate::testing::crash_test::{CrashTestDummy, Panic};
  |
  |
  = note: duplicate diagnostic emitted due to `-Z deduplicate-diagnostics=no`
error[E0433]: failed to resolve: could not find `testing` in the crate root
##[error] --> library/alloc/src/collections/btree/set/tests.rs:6:12
  |
  |
6 | use crate::testing::rng::DeterministicRng;

error[E0433]: failed to resolve: could not find `testing` in the crate root
##[error]  --> library/alloc/src/collections/linked_list/tests.rs:10:12
   |
   |
10 | use crate::testing::crash_test::{CrashTestDummy, Panic};

error[E0433]: failed to resolve: could not find `testing` in the crate root
##[error]  --> library/alloc/src/collections/linked_list/tests.rs:10:12
   |
   |
10 | use crate::testing::crash_test::{CrashTestDummy, Panic};
   |
   |
   = note: duplicate diagnostic emitted due to `-Z deduplicate-diagnostics=no`
error[E0433]: failed to resolve: use of unresolved module or unlinked crate `realalloc`
##[error]  --> library/alloc/src/collections/mod.rs:75:9
   |
75 | pub use realalloc::collections::TryReserveError;
---

error[E0433]: failed to resolve: use of unresolved module or unlinked crate `std`
##[error] --> library/alloc/src/collections/btree/map/tests.rs:3:5
  |
3 | use std::ops::Bound::{Excluded, Included, Unbounded};
  |     ^^^ use of unresolved module or unlinked crate `std`
  = help: if you wanted to use a crate named `std`, use `cargo add std` to add it to your `Cargo.toml`

error[E0433]: failed to resolve: use of unresolved module or unlinked crate `std`
##[error] --> library/alloc/src/collections/btree/map/tests.rs:3:5
##[error] --> library/alloc/src/collections/btree/map/tests.rs:3:5
  |
3 | use std::ops::Bound::{Excluded, Included, Unbounded};
  |     ^^^ use of unresolved module or unlinked crate `std`
  = help: if you wanted to use a crate named `std`, use `cargo add std` to add it to your `Cargo.toml`
  = help: if you wanted to use a crate named `std`, use `cargo add std` to add it to your `Cargo.toml`
  = note: duplicate diagnostic emitted due to `-Z deduplicate-diagnostics=no`
error[E0433]: failed to resolve: use of unresolved module or unlinked crate `std`
##[error] --> library/alloc/src/collections/btree/map/tests.rs:3:5
  |
  |
3 | use std::ops::Bound::{Excluded, Included, Unbounded};
  |     ^^^ use of unresolved module or unlinked crate `std`
  = help: if you wanted to use a crate named `std`, use `cargo add std` to add it to your `Cargo.toml`
  = help: if you wanted to use a crate named `std`, use `cargo add std` to add it to your `Cargo.toml`
  = note: duplicate diagnostic emitted due to `-Z deduplicate-diagnostics=no`
error[E0433]: failed to resolve: use of unresolved module or unlinked crate `std`
##[error] --> library/alloc/src/collections/btree/map/tests.rs:4:5
  |
4 | use std::panic::{AssertUnwindSafe, catch_unwind};
---
  |
4 | use std::panic::{AssertUnwindSafe, catch_unwind};
  |     ^^^ use of unresolved module or unlinked crate `std`
  |
  = help: if you wanted to use a crate named `std`, use `cargo add std` to add it to your `Cargo.toml`
  = note: duplicate diagnostic emitted due to `-Z deduplicate-diagnostics=no`
error[E0433]: failed to resolve: use of unresolved module or unlinked crate `std`
##[error] --> library/alloc/src/collections/btree/map/tests.rs:5:5
  |
5 | use std::sync::atomic::AtomicUsize;
---

error[E0433]: failed to resolve: use of unresolved module or unlinked crate `std`
##[error] --> library/alloc/src/collections/btree/set/tests.rs:1:5
  |
1 | use std::ops::Bound::{Excluded, Included};
  |     ^^^ use of unresolved module or unlinked crate `std`
  = help: if you wanted to use a crate named `std`, use `cargo add std` to add it to your `Cargo.toml`

error[E0433]: failed to resolve: use of unresolved module or unlinked crate `std`
##[error] --> library/alloc/src/collections/btree/set/tests.rs:1:5
##[error] --> library/alloc/src/collections/btree/set/tests.rs:1:5
  |
1 | use std::ops::Bound::{Excluded, Included};
  |     ^^^ use of unresolved module or unlinked crate `std`
  = help: if you wanted to use a crate named `std`, use `cargo add std` to add it to your `Cargo.toml`
  = help: if you wanted to use a crate named `std`, use `cargo add std` to add it to your `Cargo.toml`
  = note: duplicate diagnostic emitted due to `-Z deduplicate-diagnostics=no`
error[E0433]: failed to resolve: use of unresolved module or unlinked crate `std`
##[error] --> library/alloc/src/collections/btree/set/tests.rs:2:5
  |
2 | use std::panic::{AssertUnwindSafe, catch_unwind};
---
  |
2 | use std::panic::{AssertUnwindSafe, catch_unwind};
  |     ^^^ use of unresolved module or unlinked crate `std`
  |
  = help: if you wanted to use a crate named `std`, use `cargo add std` to add it to your `Cargo.toml`
  = note: duplicate diagnostic emitted due to `-Z deduplicate-diagnostics=no`
error[E0433]: failed to resolve: use of unresolved module or unlinked crate `std`
##[error] --> library/alloc/src/collections/linked_list/tests.rs:4:5
  |
4 | use std::panic::{AssertUnwindSafe, catch_unwind};
---
  |
4 | use std::panic::{AssertUnwindSafe, catch_unwind};
  |     ^^^ use of unresolved module or unlinked crate `std`
  |
  = help: if you wanted to use a crate named `std`, use `cargo add std` to add it to your `Cargo.toml`
  = note: duplicate diagnostic emitted due to `-Z deduplicate-diagnostics=no`
error[E0432]: unresolved import `std`
##[error] --> library/alloc/src/collections/btree/map/tests.rs:2:5
  |
2 | use std::iter;
---

error[E0433]: failed to resolve: could not find `test_helpers` in the crate root
##[error]   --> library/alloc/src/collections/linked_list/tests.rs:527:26
    |
527 |     let mut rng = crate::test_helpers::test_rng();
    |                          ^^^^^^^^^^^^ could not find `test_helpers` in the crate root
error[E0433]: failed to resolve: use of unresolved module or unlinked crate `std`
##[error]  --> library/alloc/src/raw_vec/tests.rs:96:16
   |
   |
96 |     assert_eq!(std::mem::size_of::<ZST>(), 0);
   |                ^^^ use of unresolved module or unlinked crate `std`
   = help: if you wanted to use a crate named `std`, use `cargo add std` to add it to your `Cargo.toml`
help: consider importing this module
   |
1  + use core::mem;
1  + use core::mem;
   |
help: if you import `mem`, refer to it directly
   |
96 -     assert_eq!(std::mem::size_of::<ZST>(), 0);
96 +     assert_eq!(mem::size_of::<ZST>(), 0);

error[E0425]: cannot find value `CapacityOverflow` in this scope
##[error]   --> library/alloc/src/raw_vec/mod.rs:463:34
    |
    |
28  | fn capacity_overflow() -> ! {
    | --------------------------- similarly named function `capacity_overflow` defined here
...
463 |             Err(_) => return Err(CapacityOverflow.into()),

error[E0422]: cannot find struct, variant or union type `AllocError` in this scope
##[error]   --> library/alloc/src/raw_vec/mod.rs:482:34
    |
    |
482 |             Err(_) => return Err(AllocError { layout, non_exhaustive: () }.into()),
    |
help: consider importing one of these structs
    |
7   + use crate::alloc::AllocError;
---
    |
28  | fn capacity_overflow() -> ! {
    | --------------------------- similarly named function `capacity_overflow` defined here
...
651 |             return Err(CapacityOverflow.into());

error[E0425]: cannot find value `CapacityOverflow` in this scope
##[error]   --> library/alloc/src/raw_vec/mod.rs:655:62
    |
    |
28  | fn capacity_overflow() -> ! {
    | --------------------------- similarly named function `capacity_overflow` defined here
...
655 |         let required_cap = len.checked_add(additional).ok_or(CapacityOverflow)?;

error[E0425]: cannot find value `CapacityOverflow` in this scope
##[error]   --> library/alloc/src/raw_vec/mod.rs:680:24
    |
    |
28  | fn capacity_overflow() -> ! {
    | --------------------------- similarly named function `capacity_overflow` defined here
...
680 |             return Err(CapacityOverflow.into());

error[E0425]: cannot find value `CapacityOverflow` in this scope
##[error]   --> library/alloc/src/raw_vec/mod.rs:683:53
    |
    |
28  | fn capacity_overflow() -> ! {
    | --------------------------- similarly named function `capacity_overflow` defined here
...
683 |         let cap = len.checked_add(additional).ok_or(CapacityOverflow)?;

error[E0422]: cannot find struct, variant or union type `AllocError` in this scope
##[error]   --> library/alloc/src/raw_vec/mod.rs:737:34
    |
    |
737 |                     .map_err(|_| AllocError { layout: new_layout, non_exhaustive: () })?
    |
help: consider importing one of these structs
    |
7   + use crate::alloc::AllocError;
7   + use crate::alloc::AllocError;
    |
7   + use core::alloc::AllocError;
    |

error[E0422]: cannot find struct, variant or union type `AllocError` in this scope
##[error]   --> library/alloc/src/raw_vec/mod.rs:787:24
    |
787 |     memory.map_err(|_| AllocError { layout: new_layout, non_exhaustive: () }.into())
    |
help: consider importing one of these structs
    |
7   + use crate::alloc::AllocError;
7   + use crate::alloc::AllocError;
    |
7   + use core::alloc::AllocError;
    |

error[E0422]: cannot find struct, variant or union type `AllocError` in this scope
##[error]   --> library/alloc/src/raw_vec/mod.rs:798:9
    |
798 |         AllocError { layout, .. } => handle_alloc_error(layout),
    |
help: consider importing one of these structs
    |
7   + use crate::alloc::AllocError;
---
    |
28  | fn capacity_overflow() -> ! {
    | --------------------------- similarly named function `capacity_overflow` defined here
...
813 |         Err(CapacityOverflow.into())

error[E0425]: cannot find value `CapacityOverflow` in this scope
##[error]   --> library/alloc/src/raw_vec/mod.rs:821:70
    |
    |
28  | fn capacity_overflow() -> ! {
    | --------------------------- similarly named function `capacity_overflow` defined here
...
821 |     elem_layout.repeat(cap).map(|(layout, _pad)| layout).map_err(|_| CapacityOverflow.into())

error: use of unstable library feature `test`: `bench` is a part of custom test frameworks which are unstable
##[error] --> library/alloc/src/collections/vec_deque/tests.rs:8:3
  |
---

error[E0433]: failed to resolve: use of unresolved module or unlinked crate `test`
##[error] --> library/alloc/src/collections/vec_deque/tests.rs:9:32
  |
9 | fn bench_push_back_100(b: &mut test::Bencher) {
  |                                ^^^^ use of unresolved module or unlinked crate `test`
  = help: if you wanted to use a crate named `test`, use `cargo add test` to add it to your `Cargo.toml`

error[E0433]: failed to resolve: use of unresolved module or unlinked crate `test`
##[error]  --> library/alloc/src/collections/vec_deque/tests.rs:21:33
##[error]  --> library/alloc/src/collections/vec_deque/tests.rs:21:33
   |
21 | fn bench_push_front_100(b: &mut test::Bencher) {
   |                                 ^^^^ use of unresolved module or unlinked crate `test`
   = help: if you wanted to use a crate named `test`, use `cargo add test` to add it to your `Cargo.toml`

error[E0433]: failed to resolve: use of unresolved module or unlinked crate `test`
##[error]  --> library/alloc/src/collections/vec_deque/tests.rs:33:31
##[error]  --> library/alloc/src/collections/vec_deque/tests.rs:33:31
   |
33 | fn bench_pop_back_100(b: &mut test::Bencher) {
   |                               ^^^^ use of unresolved module or unlinked crate `test`
   = help: if you wanted to use a crate named `test`, use `cargo add test` to add it to your `Cargo.toml`

error[E0433]: failed to resolve: use of unresolved module or unlinked crate `test`
##[error]  --> library/alloc/src/collections/vec_deque/tests.rs:44:13
##[error]  --> library/alloc/src/collections/vec_deque/tests.rs:44:13
   |
44 |             test::black_box(deq.pop_back());
   |             ^^^^ use of unresolved module or unlinked crate `test`
   = help: if you wanted to use a crate named `test`, use `cargo add test` to add it to your `Cargo.toml`

error[E0433]: failed to resolve: use of unresolved module or unlinked crate `test`
##[error]  --> library/alloc/src/collections/vec_deque/tests.rs:50:37
##[error]  --> library/alloc/src/collections/vec_deque/tests.rs:50:37
   |
50 | fn bench_retain_whole_10000(b: &mut test::Bencher) {
   |                                     ^^^^ use of unresolved module or unlinked crate `test`
   = help: if you wanted to use a crate named `test`, use `cargo add test` to add it to your `Cargo.toml`

error[E0433]: failed to resolve: use of unresolved module or unlinked crate `test`
##[error]  --> library/alloc/src/collections/vec_deque/tests.rs:61:35
##[error]  --> library/alloc/src/collections/vec_deque/tests.rs:61:35
   |
61 | fn bench_retain_odd_10000(b: &mut test::Bencher) {
   |                                   ^^^^ use of unresolved module or unlinked crate `test`
   = help: if you wanted to use a crate named `test`, use `cargo add test` to add it to your `Cargo.toml`

error[E0433]: failed to resolve: use of unresolved module or unlinked crate `test`
##[error]  --> library/alloc/src/collections/vec_deque/tests.rs:72:36
##[error]  --> library/alloc/src/collections/vec_deque/tests.rs:72:36
   |
72 | fn bench_retain_half_10000(b: &mut test::Bencher) {
   |                                    ^^^^ use of unresolved module or unlinked crate `test`
   = help: if you wanted to use a crate named `test`, use `cargo add test` to add it to your `Cargo.toml`

error[E0433]: failed to resolve: use of unresolved module or unlinked crate `test`
##[error]  --> library/alloc/src/collections/vec_deque/tests.rs:83:32
##[error]  --> library/alloc/src/collections/vec_deque/tests.rs:83:32
   |
83 | fn bench_pop_front_100(b: &mut test::Bencher) {
   |                                ^^^^ use of unresolved module or unlinked crate `test`
   = help: if you wanted to use a crate named `test`, use `cargo add test` to add it to your `Cargo.toml`

error[E0433]: failed to resolve: use of unresolved module or unlinked crate `test`
##[error]  --> library/alloc/src/collections/vec_deque/tests.rs:94:13
##[error]  --> library/alloc/src/collections/vec_deque/tests.rs:94:13
   |
94 |             test::black_box(deq.pop_front());
   |             ^^^^ use of unresolved module or unlinked crate `test`
   = help: if you wanted to use a crate named `test`, use `cargo add test` to add it to your `Cargo.toml`

error: aborting due to 61 previous errors


Some errors have detailed explanations: E0152, E0422, E0425, E0432, E0433.
For more information about an error, try `rustc --explain E0152`.
error: test failed, to rerun pass `-p alloc --lib`
Caused by:
Caused by:
  process didn't exit successfully: `/checkout/obj/build/x86_64-unknown-linux-gnu/stage0-tools-bin/cargo-miri runner /checkout/obj/build/x86_64-unknown-linux-gnu/stage1-std/miri/x86_64-unknown-linux-gnu/debug/deps/alloc-42cf5f79d9da7a10 -Z unstable-options --format json` (exit status: 1)
note: test exited abnormally; to see the full output pass --nocapture to the harness.
Build completed unsuccessfully in 0:03:15
make: *** [Makefile:53: check-aux] Error 1
  network time: Fri, 14 Feb 2025 03:17:14 GMT
##[error]Process completed with exit code 2.
Post job cleanup.

bors · 2025-02-14T03:18:45Z

💔 Test failed - checks-actions

real-eren and others added 30 commits February 2, 2025 21:51

Simplify SSE2 implementation

3c7c38a

Remove dead control char logic

d6ca7ad

Only newlines and multibyte characters are actually relevant

expect EINVAL for pthread_mutex_destroy for aix

4b086d4

Use the right binder for rebinding PolyTraitRef

88193aa

add IntoBounds trait

9c03369

for `range_into_bounds` feature, rust-lang#136903

ignore vendor directory in git status

51b105d

Use slice::fill in io::Repeat implementation

1a3efd2

Use the existing `fill` methods on slices instead of manually writing the fill loop.

Trace execution of bootstrap commands

d7eca8a

Add export of bootstrap tracing to Chrome events

447a6a0

Document bootstrap profiling

521cbd3

Move all alloc integration tests to a new alloctests crate

ce9bf4a

Move most Rc tests to alloctests

4a01dcc

Move last remaining Rc test to alloctests

8c9fee0

Fully test the alloc crate through alloctests

69ac9fc

For the tests that make use of internal implementation details, we include the module to test using #[path] in alloctests now.

Add comments

1726670

alloc boxed: docs: use MaybeUninit::write instead of as_mut_ptr

2f27236

In the deferred initialization pattern, the docs were needlessly going through as_mut_ptr().write() to initialize, which is unnecessary use of a pointer, needs to be inside an unsafe block, and may weaken alias analysis.

ci: switch loongarch jobs to free runners

fc5ff7f

Make -O mean -C opt-level=3

2966256

Update backtrace

06524b5

[cg_llvm] Remove dead error message

bfdc961

Rollup merge of rust-lang#136904 - pitaj:range-into_bounds, r=tgross35

b44251d

add `IntoBounds` trait for `range_into_bounds` feature Tracking issue: rust-lang#136903 ACP: rust-lang/libs-team#538

Rollup merge of rust-lang#136951 - compiler-errors:clause-binder, r=lqd

ed4a63b

Use the right binder for rebinding `PolyTraitRef` Fixes rust-lang#136940 I committed a slightly different test which still demonstrates the issue.

Rollup merge of rust-lang#136956 - jyn514:ignore-vendor, r=Noratrieb

c5a1b4b

add vendor directory to .gitignore

Rollup merge of rust-lang#136967 - DaniPopes:io-repeat-fill, r=joboet

a72aa95

Use `slice::fill` in `io::Repeat` implementation Use the existing `fill` methods on slices instead of manually writing the fill loop.

workingjubilee added 3 commits February 13, 2025 17:09

Rollup merge of rust-lang#136981 - marcoieni:no-largedisk-loongarch, …

3080384

…r=Kobzol ci: switch loongarch jobs to free runners try-job: dist-loongarch64-linux try-job: dist-loongarch64-musl

Rollup merge of rust-lang#136993 - dpaoliello:cleanllvm4, r=workingju…

f431f11

…bilee [cg_llvm] Remove dead error message Part of rust-lang#135502 Discovered a dead error message in rustc_codegen_llvm, so removing it. r? `@Zalathar`

bors added S-waiting-on-bors Status: Waiting on bors to run and complete tests. Bors will change the label on completion. and removed S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. labels Feb 14, 2025

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 Feb 14, 2025

workingjubilee mentioned this pull request Feb 14, 2025

Put the alloc unit tests in a separate alloctests package #136642

Open

workingjubilee closed this Feb 14, 2025

workingjubilee deleted the rollup-b2v8qrc branch February 14, 2025 05:34

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Rollup of 13 pull requests #136998

Rollup of 13 pull requests #136998

workingjubilee commented Feb 14, 2025

workingjubilee commented Feb 14, 2025

bors commented Feb 14, 2025

bors commented Feb 14, 2025

rust-log-analyzer commented Feb 14, 2025

bors commented Feb 14, 2025

Rollup of 13 pull requests #136998

Rollup of 13 pull requests #136998

Conversation

workingjubilee commented Feb 14, 2025

workingjubilee commented Feb 14, 2025

bors commented Feb 14, 2025

bors commented Feb 14, 2025

rust-log-analyzer commented Feb 14, 2025

bors commented Feb 14, 2025