| 2022-11-25 07:21:25 |
11417 |
@bors retry again plz |
| 2022-11-25 06:58:16 |
10343 |
@bors retry |
| 2022-11-25 03:07:20 |
11417 |
@bors retry |
| 2022-11-24 16:30:40 |
10343 |
I am not sure if it is related to https://github.com/rust-lang/rust/issues/98302, but [it can be reproduced](https://github.com/weihanglo/cargo/actions/runs/3541971990/jobs/5946901773) so seems not a flaky test?
Anyway, let's try again.
@bors retry |
| 2022-11-12 20:31:07 |
11366 |
@bors retry
proptest #6258 |
| 2022-11-03 20:32:33 |
11331 |
@bors retry |
| 2022-11-03 18:38:24 |
11332 |
@bors retry
Cannot reproduce on my machine. There is a thread sleep in the test. Maybe that is causing a race?
Anyway, let's try it again.
```
running `/Users/runner/work/cargo/cargo/target/debug/cargo build -Z unstable-options --out-dir out`
running `/Users/runner/work/cargo/cargo/target/tmp/cit/t1625/foo/out/foo`
running `/Users/runner/work/cargo/cargo/target/debug/cargo build -Z unstable-options --out-dir out`
running `/Users/runner/work/cargo/cargo/target/tmp/cit/t1625/foo/out/foo`
thread 'out_dir::replaces_artifacts' panicked at '
test failed running `/Users/runner/work/cargo/cargo/target/tmp/cit/t1625/foo/out/foo`
error: stdout did not match:
error: test failed, to rerun pass `--test testsuite`
1 -bar
1 +foo
```
|
| 2022-11-03 18:07:51 |
11331 |
https://github.com/rust-lang/cargo/pull/11332 fixes [the failing semver-check](https://github.com/rust-lang/cargo/actions/runs/3387258044/jobs/5627752968)
@bors retry |
| 2022-11-01 09:21:10 |
11308 |
CI should be fixed this time. [REF](https://rust-lang.zulipchat.com/#narrow/stream/246057-t-cargo/topic/latest.20nightly.20broken)
@bors retry |
| 2022-10-31 22:13:00 |
11308 |
CI has been fixed. [REF](https://rust-lang.zulipchat.com/#narrow/stream/246057-t-cargo/topic/latest.20nightly.20broken)
@bors retry |
| 2022-10-20 03:54:21 |
11258 |
I don't know why bors got stuck and skipped.
@bors retry |