2023-03-24 21:03:49 |
11883 |
MacOS test failure:
```
---- features::many_features_no_rebuilds stdout ----
running `/Users/runner/work/cargo/cargo/target/debug/cargo check`
running `/Users/runner/work/cargo/cargo/target/debug/cargo check -v`
thread 'features::many_features_no_rebuilds' panicked at '
test failed running `/Users/runner/work/cargo/cargo/target/debug/cargo check -v`
error: stderr did not match:
1 1 Fresh a v0.1.0 ([..]/a)
2 - Fresh b v0.1.0 ([..])
2 + Dirty b v0.1.0 (/Users/runner/work/cargo/cargo/target/tmp/cit/t1062/foo): the dependency a was rebuilt (1679672396.259504197s, 2s after last build at 1679672394.369533641s)
3 + Checking b v0.1.0 (/Users/runner/work/cargo/cargo/target/tmp/cit/t1062/foo)
4 + Running `rustc
```
@bors retry |
2023-03-22 16:33:38 |
11876 |
Unexpected test failure on macOS nightly:
```
---- rustc_info_cache::rustc_info_cache_with_wrappers stdout ----
running `/Users/runner/work/cargo/cargo/target/debug/cargo clean`
running `/Users/runner/work/cargo/cargo/target/debug/cargo build`
running `/Users/runner/work/cargo/cargo/target/debug/cargo build`
running `/Users/runner/work/cargo/cargo/target/debug/cargo build`
running `/Users/runner/work/cargo/cargo/target/debug/cargo build`
running `/Users/runner/work/cargo/cargo/target/debug/cargo build`
running `/Users/runner/work/cargo/cargo/target/debug/cargo build`
running `/Users/runner/work/cargo/cargo/target/debug/cargo clean`
running `/Users/runner/work/cargo/cargo/target/debug/cargo build`
running `/Users/runner/work/cargo/cargo/target/debug/cargo build`
running `/Users/runner/work/cargo/cargo/target/debug/cargo build`
running `/Users/runner/work/cargo/cargo/target/debug/cargo build`
running `/Users/runner/work/cargo/cargo/target/debug/cargo build`
thread 'rustc_info_cache::rustc_info_cache_with_wrappers' panicked at '
test failed running `/Users/runner/work/cargo/cargo/target/debug/cargo build`
error: process exited with code 0 (expected 101)
--- stdout
--- stderr
[2023-03-22T15:33:23Z DEBUG cargo::util::rustc] adding rustup info to rustc fingerprint
[2023-03-22T15:33:23Z DEBUG cargo::util::rustc] reusing existing rustc info cache
[2023-03-22T15:33:23Z DEBUG cargo::util::rustc] rustc info cache hit
[2023-03-22T15:33:23Z DEBUG cargo::util::rustc] rustc info cache hit
[2023-03-22T15:33:23Z DEBUG cargo::util::rustc] adding rustup info to rustc fingerprint
[2023-03-22T15:33:23Z DEBUG cargo::util::rustc] reusing existing rustc info cache
[2023-03-22T15:33:23Z DEBUG cargo::util::rustc] rustc info cache hit
Finished dev [unoptimized + debuginfo] target(s) in 0.02s
', tests/testsuite/rustc_info_cache.rs:175:14
```
I've never seen that test fail before. For some reason, the build call [here](https://github.com/rust-lang/cargo/blob/00030f6e42b98824368e369d9f8fba992cddf929/tests/testsuite/rustc_info_cache.rs#L167-L175) didn't catch that the mtime of the `rustc` wrapper changed. I'm a bit surprised, since I believe GitHub Actions is using APFS and that should have a relatively high resolution timestamps (roughly around 6µs on my system).
If this happens again in the future, it might be good to investigate more.
@bors retry
|
2023-03-14 01:01:44 |
11839 |
https://github.com/rust-lang/cargo/actions/runs/4410709210/jobs/7728460351
> warning: spurious network error (2 tries remaining): [6] Couldn't resolve host name (Could not resolve host: index.crates.io)
@bors retry |
2023-03-13 10:28:29 |
11835 |
Looks like a spurious failure due to network timeout not related to this PR.
@bors retry |
2023-03-11 17:28:43 |
11829 |
@bors retry
#10120 docscrape failure
|
2023-03-09 20:19:00 |
11820 |
@bors retry
#11821 |
2023-03-04 05:57:46 |
11799 |
Test failures look related to gitoxide? - cc @Byron. Trying again.
@bors retry |
2023-03-03 02:53:41 |
11794 |
@bors retry
The GitHub outage should be resolved. |
2023-02-25 07:39:04 |
11643 |
@bors retry |
2023-02-12 01:39:31 |
11618 |
@bors retry |