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 11 pull requests #82355

Closed
wants to merge 28 commits into from
Closed

Conversation

JohnTitor
Copy link
Member

Successful merges:

Failed merges:

r? @ghost
@rustbot modify labels: rollup

Create a similar rollup

ssomers and others added 28 commits February 9, 2021 11:21
Windows does not allow deleting currently running executables
Using `i32` is rather fragile because it has many implementations -
and indeed I'm about to add one.

TryFromSliceError is nice because it doesn't seem likely to grow new
conversions.  We still have one conversion, from Infallible.

Signed-off-by: Ian Jackson <ijackson@chiark.greenend.org.uk>
old:

```
real	0m11.123s
user	0m14.495s
sys	0m5.227s
```

new:

```
real	0m2.767s
user	0m13.014s
sys	0m1.691s
```
Pretty formatter when using multiple test threads displays test name twice on
timeout event. This implicitly suggest that those are two different events,
while in fact they are always printed together.

Print test name only once.

Before:

```
running 3 tests
test src/lib.rs - c (line 16) ... ok
test src/lib.rs - a (line 3) ... ok
test src/lib.rs - b (line 9) ... test src/lib.rs - b (line 9) has been running for over 60 seconds
test src/lib.rs - b (line 9) ... ok
```

After:

```
running 3 tests
test src/lib.rs - c (line 16) ... ok
test src/lib.rs - a (line 3) ... ok
test src/lib.rs - b (line 9) has been running for over 60 seconds
test src/lib.rs - b (line 9) ... ok
```
…=Mark-Simulacrum

BTree: share panicky test code & test panic during clear, clone

Bases almost all tests of panic on the same, richer definition, and extends it to cloning to test panic during clone.

r? ``@Mark-Simulacrum``
…e, r=Mark-Simulacrum

Document BinaryHeap unsafe functions

`BinaryHeap` contains some private safe functions but that are actually unsafe to call. This PR marks them `unsafe` and documents all the `unsafe` function calls inside them.

While doing this I might also have found a bug: some "SAFETY" comments in `sift_down_range` and `sift_down_to_bottom` are valid only if you assume that `child` doesn't overflow. However it may overflow if `end > isize::MAX` which can be true for ZSTs (but I think only for them). I guess the easiest fix would be to skip any sifting if `mem::size_of::<T> == 0`.

Probably conflicts with rust-lang#81127 but solving the eventual merge conflict should be pretty easy.
… r=Mark-Simulacrum

parallelize x.py test tidy

Running tidy on individual commits when rewriting git history was somewhat of an annoyance, so I have parallelized it a bit.

running `time ./x.py test tidy` with warm IO caches:

old:

```
real	0m11.123s
user	0m14.495s
sys	0m5.227s
```

new:

```
real	0m1.834s
user	0m13.545s
sys	0m3.094s
```

There's further room for improvement (<0.9s should be feasible) but that would require bigger changes.
…imulacrum

Avoid `cfg_if` in `std::os`

rust-analyzer cannot currently load the `cfg_if` crate, which means that rust-analyzer is unable to see `std::os::{unix, windows, linux}` here. This works around that by avoiding `cfg_if`; the `#[cfg]` expressions are simple enough to reasonably write by hand.

Fixes rust-lang/rust-analyzer#6038
Update RELEASES.md 1.50 to include methods stabilized in rust-lang#79342

I noticed that rust-lang#79342 was missing from the release notes for 1.50.
…r=Mark-Simulacrum

Do not delete bootstrap.exe on Windows during clean

Windows does not allow deleting currently running executables.

This an addition to ``@jyn514's`` change in rust-lang#80574.
…k-Simulacrum

Add check for ES5 in CI

Follow-up of rust-lang#82145.

r? ``@Mark-Simulacrum``
…ulacrum

Add [A-diagnostics] bug report template
…k-Simulacrum

try-back-block-type test: Use TryFromSliceError for From test

Using `i32` is rather fragile because it has many implementations.  Recently in an early draft of another MR (rust-lang#82228) I did something that introduced a new `i32 as From<something>` impl and this test broke.

TryFromSliceError is nice because it doesn't seem likely to grow new conversions.  We still have one conversion, from Infallible.

My other MR is going to be reworked and won't need this any more but having done it I thought I would submit it rather than just throw it away.  Sorry for the tiny MR.
…mulacrum

Remove unsafe impl Send for CompletedTest & TestResult
…-Simulacrum

test: Print test name only once on timeout

Pretty formatter when using multiple test threads displays test name twice on
timeout event. This implicitly suggest that those are two different events,
while in fact they are always printed together.

Print test name only once.

Before:

```
running 3 tests
test src/lib.rs - c (line 16) ... ok
test src/lib.rs - a (line 3) ... ok
test src/lib.rs - b (line 9) ... test src/lib.rs - b (line 9) has been running for over 60 seconds
test src/lib.rs - b (line 9) ... ok
```

After:

```
running 3 tests
test src/lib.rs - c (line 16) ... ok
test src/lib.rs - a (line 3) ... ok
test src/lib.rs - b (line 9) has been running for over 60 seconds
test src/lib.rs - b (line 9) ... ok
```
@rustbot rustbot added the rollup A PR which is a rollup label Feb 21, 2021
@JohnTitor
Copy link
Member Author

@bors r+ p=11 rollup=never

@bors
Copy link
Contributor

bors commented Feb 21, 2021

📌 Commit 9516484 has been approved by JohnTitor

@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 Feb 21, 2021
@bors
Copy link
Contributor

bors commented Feb 21, 2021

⌛ Testing commit 9516484 with merge 0bc1c85869368625a4958b688ec938959fadcddf...

@rust-log-analyzer
Copy link
Collaborator

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

Click to see the possible cause of the failure (guessed by this bot)
test src\net\udp.rs - net::udp::UdpSocket::take_error (line 599) ... ok
test src\net\udp.rs - net::udp::UdpSocket::try_clone (line 233) ... ok
test src\net\udp.rs - net::udp::UdpSocket::ttl (line 541) ... ok
test src\net\udp.rs - net::udp::UdpSocket::write_timeout (line 358) ... ok
test src\os\linux\fs.rs - os::linux::fs::MetadataExt::as_raw_stat (line 27) ... FAILED
test src\os\linux\fs.rs - os::linux::fs::MetadataExt::st_blocks (line 311) ... FAILED
test src\os\linux\fs.rs - os::linux::fs::MetadataExt::st_ctime (line 258) ... FAILED
test src\os\linux\fs.rs - os::linux::fs::MetadataExt::st_dev (line 47) ... FAILED
test src\os\linux\fs.rs - os::linux::fs::MetadataExt::st_ctime_nsec (line 277) ... FAILED
test src\os\linux\fs.rs - os::linux::fs::MetadataExt::st_blksize (line 294) ... FAILED
test src\os\linux\fs.rs - os::linux::fs::MetadataExt::st_atime_nsec (line 205) ... FAILED
test src\os\linux\fs.rs - os::linux::fs::MetadataExt::st_atime (line 186) ... FAILED
test src\os\linux\fs.rs - os::linux::fs::MetadataExt::st_gid (line 132) ... FAILED
test src\os\linux\fs.rs - os::linux::fs::MetadataExt::st_mode (line 81) ... FAILED
test src\os\linux\fs.rs - os::linux::fs::MetadataExt::st_nlink (line 98) ... FAILED
test src\os\linux\fs.rs - os::linux::fs::MetadataExt::st_rdev (line 149) ... FAILED
test src\os\linux\fs.rs - os::linux::fs::MetadataExt::st_mtime_nsec (line 241) ... FAILED
test src\os\linux\fs.rs - os::linux::fs::MetadataExt::st_mtime (line 222) ... FAILED
test src\os\linux\fs.rs - os::linux::fs::MetadataExt::st_size (line 169) ... FAILED
test src\os\linux\fs.rs - os::linux::fs::MetadataExt::st_ino (line 64) ... FAILED
test src\panic.rs - panic::AssertUnwindSafe (line 173) ... ok
test src\panic.rs - panic::AssertUnwindSafe (line 173) ... ok
test src\os\linux\fs.rs - os::linux::fs::MetadataExt::st_uid (line 115) ... FAILED
test src\panicking.rs - panicking::take_hook (line 150) ... ok
test src\path.rs - path (line 23) ... ok
test src\panicking.rs - panicking::set_hook (line 104) ... ok
test src\panic.rs - panic::catch_unwind (line 416) ... ok
---
test src\thread\mod.rs - thread::spawn (line 574) ... ok

failures:

---- src\os\linux\fs.rs - os::linux::fs::MetadataExt::as_raw_stat (line 27) stdout ----
error[E0433]: failed to resolve: could not find `linux` in `os`
 --> src\os\linux\fs.rs:30:14
5 | use std::os::linux::fs::MetadataExt;
5 | use std::os::linux::fs::MetadataExt;
  |              ^^^^^ could not find `linux` in `os`

error[E0599]: no method named `as_raw_stat` found for struct `Metadata` in the current scope
 --> src\os\linux\fs.rs:34:21
  |
9 |     let stat = meta.as_raw_stat();
  |                     ^^^^^^^^^^^ method not found in `Metadata`
error: aborting due to 2 previous errors

Some errors have detailed explanations: E0433, E0599.
For more information about an error, try `rustc --explain E0433`.
For more information about an error, try `rustc --explain E0433`.
Couldn't compile the test.
---- src\os\linux\fs.rs - os::linux::fs::MetadataExt::st_blocks (line 311) stdout ----
error[E0433]: failed to resolve: could not find `linux` in `os`
 --> src\os\linux\fs.rs:314:14
5 | use std::os::linux::fs::MetadataExt;
5 | use std::os::linux::fs::MetadataExt;
  |              ^^^^^ could not find `linux` in `os`

error[E0599]: no method named `st_blocks` found for struct `Metadata` in the current scope
 --> src\os\linux\fs.rs:318:25
  |
9 |     println!("{}", meta.st_blocks());
  |                         ^^^^^^^^^ method not found in `Metadata`
error: aborting due to 2 previous errors

Some errors have detailed explanations: E0433, E0599.
For more information about an error, try `rustc --explain E0433`.
For more information about an error, try `rustc --explain E0433`.
Couldn't compile the test.
---- src\os\linux\fs.rs - os::linux::fs::MetadataExt::st_ctime (line 258) stdout ----
error[E0433]: failed to resolve: could not find `linux` in `os`
 --> src\os\linux\fs.rs:261:14
5 | use std::os::linux::fs::MetadataExt;
5 | use std::os::linux::fs::MetadataExt;
  |              ^^^^^ could not find `linux` in `os`

error[E0599]: no method named `st_ctime` found for struct `Metadata` in the current scope
 --> src\os\linux\fs.rs:265:25
  |
9 |     println!("{}", meta.st_ctime());
  |                         ^^^^^^^^ method not found in `Metadata`
error: aborting due to 2 previous errors

Some errors have detailed explanations: E0433, E0599.
For more information about an error, try `rustc --explain E0433`.
For more information about an error, try `rustc --explain E0433`.
Couldn't compile the test.
---- src\os\linux\fs.rs - os::linux::fs::MetadataExt::st_dev (line 47) stdout ----
error[E0433]: failed to resolve: could not find `linux` in `os`
 --> src\os\linux\fs.rs:50:14
5 | use std::os::linux::fs::MetadataExt;
5 | use std::os::linux::fs::MetadataExt;
  |              ^^^^^ could not find `linux` in `os`

error[E0599]: no method named `st_dev` found for struct `Metadata` in the current scope
 --> src\os\linux\fs.rs:54:25
  |
9 |     println!("{}", meta.st_dev());
  |                         ^^^^^^ method not found in `Metadata`
error: aborting due to 2 previous errors

Some errors have detailed explanations: E0433, E0599.
For more information about an error, try `rustc --explain E0433`.
For more information about an error, try `rustc --explain E0433`.
Couldn't compile the test.
---- src\os\linux\fs.rs - os::linux::fs::MetadataExt::st_ctime_nsec (line 277) stdout ----
error[E0433]: failed to resolve: could not find `linux` in `os`
 --> src\os\linux\fs.rs:280:14
5 | use std::os::linux::fs::MetadataExt;
5 | use std::os::linux::fs::MetadataExt;
  |              ^^^^^ could not find `linux` in `os`

error[E0599]: no method named `st_ctime_nsec` found for struct `Metadata` in the current scope
 --> src\os\linux\fs.rs:284:25
  |
9 |     println!("{}", meta.st_ctime_nsec());
  |                         ^^^^^^^^^^^^^ method not found in `Metadata`
error: aborting due to 2 previous errors

Some errors have detailed explanations: E0433, E0599.
For more information about an error, try `rustc --explain E0433`.
For more information about an error, try `rustc --explain E0433`.
Couldn't compile the test.
---- src\os\linux\fs.rs - os::linux::fs::MetadataExt::st_blksize (line 294) stdout ----
error[E0433]: failed to resolve: could not find `linux` in `os`
 --> src\os\linux\fs.rs:297:14
5 | use std::os::linux::fs::MetadataExt;
5 | use std::os::linux::fs::MetadataExt;
  |              ^^^^^ could not find `linux` in `os`

error[E0599]: no method named `st_blksize` found for struct `Metadata` in the current scope
 --> src\os\linux\fs.rs:301:25
9 |     println!("{}", meta.st_blksize());
  |                         ^^^^^^^^^^ method not found in `Metadata`

error: aborting due to 2 previous errors
error: aborting due to 2 previous errors

Some errors have detailed explanations: E0433, E0599.
For more information about an error, try `rustc --explain E0433`.
Couldn't compile the test.
---- src\os\linux\fs.rs - os::linux::fs::MetadataExt::st_atime_nsec (line 205) stdout ----
error[E0433]: failed to resolve: could not find `linux` in `os`
 --> src\os\linux\fs.rs:208:14
5 | use std::os::linux::fs::MetadataExt;
5 | use std::os::linux::fs::MetadataExt;
  |              ^^^^^ could not find `linux` in `os`

error[E0599]: no method named `st_atime_nsec` found for struct `Metadata` in the current scope
 --> src\os\linux\fs.rs:212:25
  |
9 |     println!("{}", meta.st_atime_nsec());
  |                         ^^^^^^^^^^^^^ method not found in `Metadata`
error: aborting due to 2 previous errors

Some errors have detailed explanations: E0433, E0599.
For more information about an error, try `rustc --explain E0433`.
For more information about an error, try `rustc --explain E0433`.
Couldn't compile the test.
---- src\os\linux\fs.rs - os::linux::fs::MetadataExt::st_atime (line 186) stdout ----
error[E0433]: failed to resolve: could not find `linux` in `os`
 --> src\os\linux\fs.rs:189:14
5 | use std::os::linux::fs::MetadataExt;
5 | use std::os::linux::fs::MetadataExt;
  |              ^^^^^ could not find `linux` in `os`

error[E0599]: no method named `st_atime` found for struct `Metadata` in the current scope
 --> src\os\linux\fs.rs:193:25
  |
9 |     println!("{}", meta.st_atime());
  |                         ^^^^^^^^ method not found in `Metadata`
error: aborting due to 2 previous errors

Some errors have detailed explanations: E0433, E0599.
For more information about an error, try `rustc --explain E0433`.
For more information about an error, try `rustc --explain E0433`.
Couldn't compile the test.
---- src\os\linux\fs.rs - os::linux::fs::MetadataExt::st_gid (line 132) stdout ----
error[E0433]: failed to resolve: could not find `linux` in `os`
 --> src\os\linux\fs.rs:135:14
5 | use std::os::linux::fs::MetadataExt;
5 | use std::os::linux::fs::MetadataExt;
  |              ^^^^^ could not find `linux` in `os`

error[E0599]: no method named `st_gid` found for struct `Metadata` in the current scope
 --> src\os\linux\fs.rs:139:25
  |
9 |     println!("{}", meta.st_gid());
  |                         ^^^^^^ method not found in `Metadata`
error: aborting due to 2 previous errors

Some errors have detailed explanations: E0433, E0599.
For more information about an error, try `rustc --explain E0433`.
For more information about an error, try `rustc --explain E0433`.
Couldn't compile the test.
---- src\os\linux\fs.rs - os::linux::fs::MetadataExt::st_mode (line 81) stdout ----
error[E0433]: failed to resolve: could not find `linux` in `os`
 --> src\os\linux\fs.rs:84:14
5 | use std::os::linux::fs::MetadataExt;
5 | use std::os::linux::fs::MetadataExt;
  |              ^^^^^ could not find `linux` in `os`

error[E0599]: no method named `st_mode` found for struct `Metadata` in the current scope
 --> src\os\linux\fs.rs:88:25
  |
9 |     println!("{}", meta.st_mode());
  |                         ^^^^^^^ method not found in `Metadata`
error: aborting due to 2 previous errors

Some errors have detailed explanations: E0433, E0599.
For more information about an error, try `rustc --explain E0433`.
For more information about an error, try `rustc --explain E0433`.
Couldn't compile the test.
---- src\os\linux\fs.rs - os::linux::fs::MetadataExt::st_nlink (line 98) stdout ----
error[E0433]: failed to resolve: could not find `linux` in `os`
 --> src\os\linux\fs.rs:101:14
5 | use std::os::linux::fs::MetadataExt;
5 | use std::os::linux::fs::MetadataExt;
  |              ^^^^^ could not find `linux` in `os`

error[E0599]: no method named `st_nlink` found for struct `Metadata` in the current scope
 --> src\os\linux\fs.rs:105:25
  |
9 |     println!("{}", meta.st_nlink());
  |                         ^^^^^^^^ method not found in `Metadata`
error: aborting due to 2 previous errors

Some errors have detailed explanations: E0433, E0599.
For more information about an error, try `rustc --explain E0433`.
For more information about an error, try `rustc --explain E0433`.
Couldn't compile the test.
---- src\os\linux\fs.rs - os::linux::fs::MetadataExt::st_rdev (line 149) stdout ----
error[E0433]: failed to resolve: could not find `linux` in `os`
 --> src\os\linux\fs.rs:152:14
5 | use std::os::linux::fs::MetadataExt;
5 | use std::os::linux::fs::MetadataExt;
  |              ^^^^^ could not find `linux` in `os`

error[E0599]: no method named `st_rdev` found for struct `Metadata` in the current scope
 --> src\os\linux\fs.rs:156:25
  |
9 |     println!("{}", meta.st_rdev());
  |                         ^^^^^^^ method not found in `Metadata`
error: aborting due to 2 previous errors

Some errors have detailed explanations: E0433, E0599.
For more information about an error, try `rustc --explain E0433`.
For more information about an error, try `rustc --explain E0433`.
Couldn't compile the test.
---- src\os\linux\fs.rs - os::linux::fs::MetadataExt::st_mtime_nsec (line 241) stdout ----
error[E0433]: failed to resolve: could not find `linux` in `os`
 --> src\os\linux\fs.rs:244:14
5 | use std::os::linux::fs::MetadataExt;
5 | use std::os::linux::fs::MetadataExt;
  |              ^^^^^ could not find `linux` in `os`

error[E0599]: no method named `st_mtime_nsec` found for struct `Metadata` in the current scope
 --> src\os\linux\fs.rs:248:25
  |
9 |     println!("{}", meta.st_mtime_nsec());
  |                         ^^^^^^^^^^^^^ method not found in `Metadata`
error: aborting due to 2 previous errors

Some errors have detailed explanations: E0433, E0599.
For more information about an error, try `rustc --explain E0433`.
For more information about an error, try `rustc --explain E0433`.
Couldn't compile the test.
---- src\os\linux\fs.rs - os::linux::fs::MetadataExt::st_mtime (line 222) stdout ----
error[E0433]: failed to resolve: could not find `linux` in `os`
 --> src\os\linux\fs.rs:225:14
5 | use std::os::linux::fs::MetadataExt;
5 | use std::os::linux::fs::MetadataExt;
  |              ^^^^^ could not find `linux` in `os`

error[E0599]: no method named `st_mtime` found for struct `Metadata` in the current scope
 --> src\os\linux\fs.rs:229:25
  |
9 |     println!("{}", meta.st_mtime());
  |                         ^^^^^^^^ method not found in `Metadata`
error: aborting due to 2 previous errors

Some errors have detailed explanations: E0433, E0599.
For more information about an error, try `rustc --explain E0433`.
For more information about an error, try `rustc --explain E0433`.
Couldn't compile the test.
---- src\os\linux\fs.rs - os::linux::fs::MetadataExt::st_size (line 169) stdout ----
error[E0433]: failed to resolve: could not find `linux` in `os`
 --> src\os\linux\fs.rs:172:14
5 | use std::os::linux::fs::MetadataExt;
5 | use std::os::linux::fs::MetadataExt;
  |              ^^^^^ could not find `linux` in `os`

error[E0599]: no method named `st_size` found for struct `Metadata` in the current scope
 --> src\os\linux\fs.rs:176:25
  |
9 |     println!("{}", meta.st_size());
  |                         ^^^^^^^ method not found in `Metadata`
error: aborting due to 2 previous errors

Some errors have detailed explanations: E0433, E0599.
For more information about an error, try `rustc --explain E0433`.
For more information about an error, try `rustc --explain E0433`.
Couldn't compile the test.
---- src\os\linux\fs.rs - os::linux::fs::MetadataExt::st_ino (line 64) stdout ----
error[E0433]: failed to resolve: could not find `linux` in `os`
 --> src\os\linux\fs.rs:67:14
5 | use std::os::linux::fs::MetadataExt;
5 | use std::os::linux::fs::MetadataExt;
  |              ^^^^^ could not find `linux` in `os`

error[E0599]: no method named `st_ino` found for struct `Metadata` in the current scope
 --> src\os\linux\fs.rs:71:25
  |
9 |     println!("{}", meta.st_ino());
  |                         ^^^^^^ method not found in `Metadata`
error: aborting due to 2 previous errors

Some errors have detailed explanations: E0433, E0599.
For more information about an error, try `rustc --explain E0433`.
For more information about an error, try `rustc --explain E0433`.
Couldn't compile the test.
---- src\os\linux\fs.rs - os::linux::fs::MetadataExt::st_uid (line 115) stdout ----
error[E0433]: failed to resolve: could not find `linux` in `os`
 --> src\os\linux\fs.rs:118:14
5 | use std::os::linux::fs::MetadataExt;
5 | use std::os::linux::fs::MetadataExt;
  |              ^^^^^ could not find `linux` in `os`

error[E0599]: no method named `st_uid` found for struct `Metadata` in the current scope
 --> src\os\linux\fs.rs:122:25
  |
9 |     println!("{}", meta.st_uid());
  |                         ^^^^^^ method not found in `Metadata`
error: aborting due to 2 previous errors

Some errors have detailed explanations: E0433, E0599.
For more information about an error, try `rustc --explain E0433`.
For more information about an error, try `rustc --explain E0433`.
Couldn't compile the test.

failures:
    src\os\linux\fs.rs - os::linux::fs::MetadataExt::as_raw_stat (line 27)
    src\os\linux\fs.rs - os::linux::fs::MetadataExt::st_atime (line 186)
    src\os\linux\fs.rs - os::linux::fs::MetadataExt::st_atime_nsec (line 205)
    src\os\linux\fs.rs - os::linux::fs::MetadataExt::st_blksize (line 294)
    src\os\linux\fs.rs - os::linux::fs::MetadataExt::st_blocks (line 311)
    src\os\linux\fs.rs - os::linux::fs::MetadataExt::st_ctime (line 258)
    src\os\linux\fs.rs - os::linux::fs::MetadataExt::st_ctime_nsec (line 277)
    src\os\linux\fs.rs - os::linux::fs::MetadataExt::st_dev (line 47)
    src\os\linux\fs.rs - os::linux::fs::MetadataExt::st_gid (line 132)
    src\os\linux\fs.rs - os::linux::fs::MetadataExt::st_ino (line 64)
    src\os\linux\fs.rs - os::linux::fs::MetadataExt::st_mode (line 81)
    src\os\linux\fs.rs - os::linux::fs::MetadataExt::st_mtime (line 222)
    src\os\linux\fs.rs - os::linux::fs::MetadataExt::st_mtime_nsec (line 241)
    src\os\linux\fs.rs - os::linux::fs::MetadataExt::st_nlink (line 98)
    src\os\linux\fs.rs - os::linux::fs::MetadataExt::st_rdev (line 149)
    src\os\linux\fs.rs - os::linux::fs::MetadataExt::st_size (line 169)
    src\os\linux\fs.rs - os::linux::fs::MetadataExt::st_uid (line 115)
test result: FAILED. 1022 passed; 17 failed; 20 ignored; 0 measured; 0 filtered out; finished in 34.97s

error: test failed, to rerun pass '--doc'



command did not execute successfully: "\\\\?\\D:\\a\\rust\\rust\\build\\x86_64-pc-windows-msvc\\stage0\\bin\\cargo.exe" "test" "--target" "x86_64-pc-windows-msvc" "-Zbinary-dep-depinfo" "-j" "8" "--release" "--locked" "--color" "always" "--features" "panic-unwind backtrace profiler compiler-builtins-c" "--manifest-path" "D:\\a\\rust\\rust\\library/test/Cargo.toml" "-p" "std" "--"


failed to run: D:\a\rust\rust\build\bootstrap\debug\bootstrap test --stage 2 --exclude src/test/ui --exclude src/tools/linkchecker
Build completed unsuccessfully in 0:40:01
Build completed unsuccessfully in 0:40:01
make: *** [Makefile:72: ci-subset-1] Error 1

@bors
Copy link
Contributor

bors commented Feb 21, 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 Feb 21, 2021
@JohnTitor JohnTitor closed this Feb 21, 2021
@JohnTitor JohnTitor deleted the rollup-b61ps2f branch February 21, 2021 06:26
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.