Homu retry log - rust

Time (UTC) PR Message
2024-02-20 23:14:20 120904
I can't tell which is the test that timed out or if this has anything to do with this PR.

@bors retry
2024-02-20 15:50:32 120904
Possibly spurious

@bors retry
2024-02-17 18:58:25 120780
I think the retry didn't register
@bors retry
2024-02-17 01:12:16 120563
Can't tell what failed.

@bors retry
@bors delegate+
2024-02-16 01:03:38 120863
I don't see any output more informative than what rust-log-analyzer posted above:
>   Session terminated, killing shell... ...killed.

Uh...
@bors retry
2024-02-15 10:06:02 120931
@bors retry
2024-02-14 14:42:15 121069
@bors retry
2024-02-14 02:00:35 121055
@bors retry
2024-02-14 01:57:48 120454
@bors retry
2024-02-14 00:04:27 121055
@bors retry
2024-02-13 21:25:41 113026
CI is haunted
@bors retry
2024-02-13 15:16:25 120942
@bors retry
2024-02-11 13:17:31 120903
2024-02-11T10:09:32.4720900Z test library/std/src/thread/mod.rs - thread::Thread::unpark (line 1303) has been running for a long time
@bors retry
2024-02-11 09:55:03 120920
@bors retry ios_simulator_version_min
2024-02-11 07:56:06 120903
@bors retry ios_simulator_version_min
2024-02-11 05:38:38 120903
@bors retry r_symbolnum
2024-02-11 01:55:01 120405
@bors retry invalid r_symbolnum
2024-02-10 22:29:02 120405
@bors retry invalid r_symbolnum 
2024-02-10 21:23:21 117206
@bors retry apple failure
2024-02-10 16:05:20 120619
@bors retry invalid r_symbolnum=14
2024-02-10 15:58:05 120867
Yep, still working on it. Just keep trying until it passes.

@bors retry

`invalid r_symbolnum=14`
2024-02-10 15:55:31 117206
@bors retry spurious apple failure
2024-02-10 04:16:48 120712
Linker error on clif looks unrelated?

@bors retry
2024-02-10 04:13:48 120867
Looks unrelated to cargo.

@bors retry
2024-02-10 00:04:03 120712
That CI failure looks totally unrelated

@bors retry
2024-02-09 21:05:08 120806
@bors retry   yield rollup
2024-02-09 21:04:02 120852
@bors retry cranelift linkage error
2024-02-09 18:12:38 120806
@bors retry
2024-02-09 07:40:01 120238
@bors retry spurious network error
2024-02-09 04:38:47 120806
@bors retry
2024-02-09 03:59:39 120594
These linker errors seem spurious? https://rust-lang.zulipchat.com/#narrow/stream/242791-t-infra/topic/Weird.20CI.20failure.20on.20x86_64-apple-1.3A.20invalid.20r_symbolnum.3D14/near/419968478
@bors retry 
2024-02-08 17:20:21 120238
This issue has been randomly happening on several PR's ever since am update of the apple runner image. It is currently being investigated on zulip. (on mobile, so I can't easily link it, but it is currently the last topic in the t-infra stream)

@bors retry spurious apple r_symbolnum cranelift linker failure
2024-02-08 12:51:18 120238
@bors retry
2024-02-08 00:04:54 120755
@bors retry
2024-02-07 12:35:15 120060
> 2024-02-07T06:09:14.6844893Z thread 'main' panicked at src/tools/remote-test-client/src/main.rs:310:9:
2024-02-07T06:09:14.6845640Z client.read_exact(&mut header) failed with Connection reset by peer (os error 104)

https://github.com/rust-lang/rust/issues/97669

@bors retry
2024-02-07 12:31:27 120558
@bors retry spurious linker failure
2024-02-07 11:16:47 120527
I'm not sure if this is spurious or not.
@bors retry
2024-02-07 10:12:29 120579
Seems flaky.

@bors retry
2024-02-07 06:52:52 120550
@bors retry runner restart
2024-02-06 20:28:52 117905
@bors retry   ld: unknown options: -ios_simulator_version_min  
2024-02-06 20:03:20 120714
seems similar to the failure in https://github.com/rust-lang/rust/pull/117905#issuecomment-1929287227
@bors retry 
2024-02-06 13:38:51 118257
@bors retry
2024-02-06 12:35:47 120361
@bors retry apple cmake failure
2024-02-06 01:06:54 120326
Latest failure looks like an infra flake. I don't believe this caused https://github.com/rust-lang/rust/pull/120623#issuecomment-1926093319.

@bors retry 
2024-02-05 13:22:52 120671
@bors retry
2024-02-04 18:50:24 120620
@bors retry
  Error: fatal: unable to access 'https://github.com/rust-lang-ci/rust/': Could not resolve host: github.com
2024-02-04 13:24:32 120543
@bors retry

Hang in net::tcp::tests::close_read_wakes_up on x86_64-mingw.
2024-02-04 12:38:20 120627
@bors retry
2024-02-04 03:02:29 120627
@bors retry apple build hang at llvm
2024-02-03 21:42:28 120561
@bors retry yield to stable release
2024-02-03 18:22:44 120536
back to the queue with you

@bors retry
2024-02-03 18:08:28 120594
@bors retry
2024-02-01 22:33:54 120536
@bors retry


2024-02-01T22:15:17.3539633Z thread 'main' panicked at src/tools/remote-test-client/src/main.rs:310:9:
2024-02-01T22:15:17.3540351Z client.read_exact(&mut header) failed with Connection reset by peer (os error 104)
2024-02-01 15:28:14 120497
@bors retry
2024-02-01 04:13:01 120447
@bors retry

runners offline
2024-02-01 03:33:44 120463
@bors retry
2024-01-31 02:02:38 120463
@bors retry
2024-01-30 22:50:37 120512
@bors retry
2024-01-30 20:20:14 120227
@bors retry
2024-01-30 13:24:53 118533
@bors retry
2024-01-30 11:18:22 118533
@bors retry
2024-01-30 09:28:24 119101
@bors retry
2024-01-29 19:43:37 120466
Flaky.

@bors retry
2024-01-29 17:17:37 120238
@bors retry macos timeout again
2024-01-29 06:41:18 120451
@bors retry The runner has received a shutdown signal.
2024-01-29 03:47:23 120437
@bors retry one last time
2024-01-28 18:24:45 120437
@bors retry apple dist various not starting
2024-01-28 13:13:33 120437
@bors retry
2024-01-28 11:06:26 120165
@bors retry
2024-01-27 20:37:40 120165
@bors retry reoccurring timeout
2024-01-26 21:43:34 118636
@bors retry timeout (reoccurring)
2024-01-26 10:19:54 120365
@bors retry apple timeout
2024-01-25 22:13:10 116167
@bors retry timeout
we are seeing quite a few of these recently...
2024-01-25 16:43:11 116167
@bors retry timeout
2024-01-24 18:30:41 120269
@bors retry timeout
2024-01-24 10:16:05 118336
@bors retry
2024-01-24 01:23:58 120276
@bors retry
2024-01-23 19:36:41 118336
Same error, but it looks like the queued rollup might have gotten past the flaky spot now.
@bors retry
2024-01-23 16:45:41 118336
>  Error: Internal server error occurred while resolving "actions/checkout@v4". Internal server error occurred while resolving "actions/upload-artifact@v3"

@bors retry
2024-01-23 16:43:14 120271
@bors retry
2024-01-23 10:08:51 116152
@bors retry 
2024-01-22 09:32:26 118578
@bors retry
2024-01-22 06:23:31 120196
@bors retry
2024-01-21 22:52:15 120196
@bors retry
2024-01-21 16:42:45 120196
@bors retry
2024-01-21 09:23:39 85528
Apple runner hanging.

@bors retry
2024-01-21 00:43:15 120111
Somehow unrelated?

@bors retry
2024-01-21 00:16:44 120100
@bors retry runner shutdown
2024-01-20 09:14:13 120157
@bors retry curl: (35) Recv failure: Connection reset by peer
2024-01-20 01:55:53 120136
@bors retry (timeout, no failures otherwise)
2024-01-19 16:41:13 120123
Identified as spurious network error.
@bors retry
2024-01-19 07:00:29 120112
@bors retry
2024-01-19 04:45:46 120069
> Error: fatal: unable to access 'https://github.com/rust-lang-ci/rust/': Could not resolve host: github.com

@bors retry
2024-01-18 05:51:41 120071
@bors retry timeout 
2024-01-18 01:19:02 120006
@bors retry
2024-01-18 00:46:01 120068
@bors retry
2024-01-17 10:33:20 119670
Failure looks spurious.
@bors retry
2024-01-17 05:10:36 120034
@bors retry
2024-01-16 16:07:30 116520
@bors retry apple timeout
2024-01-16 08:30:15 119672
@bors retry apple builder timeout
2024-01-16 00:08:10 119439
Shutdown signal, no visible reason.
@bors retry
2024-01-15 21:47:10 119439
@bors retry Could not resolve host: github.com
2024-01-15 16:59:31 119988
@bors retry #117097
2024-01-15 15:48:19 119987
@bors retry apple timeout again
2024-01-15 11:17:30 119610
@bors retry
2024-01-15 09:29:31 119987
@bors retry
2024-01-15T09:13:04.9086160Z client.read_exact(&mut header) failed with Connection reset by peer (os error 104)
2024-01-15 00:06:05 119878
[auto - aarch64-gnu](https://github.com/rust-lang-ci/rust/actions/runs/7522311570/job/20474163867#logs) "received a shutdown signal", but no other jobs show as having an issue

@bors retry 
2024-01-14 20:51:58 119878
I don't understand how this change could have broken the `__rust_{begin,end}_short_backtrace` markers.  The test is using `-Z treat-err-as-bug=1`, which I wouldn't think even uses `Result::unwrap` to trigger it?  So since the queue isn't long, I'll try a 

@bors retry  
2024-01-14 17:12:24 119561
@bors retry

dist-apple took too long
2024-01-14 04:36:39 119934
@bors retry
2024-01-12 17:43:46 118947
@bors retry
2024-01-12 00:04:53 119430
@bors retry
2024-01-11 23:38:00 119861
@bors retry
2024-01-11 00:08:08 119677
@bors retry
2024-01-10 18:02:46 119528
@bors retry

timeout on two apple runners
2024-01-10 15:31:57 119677
@bors retry 
2024-01-10 12:49:30 119528
@bors retry

timeout on dist-apple-various
2024-01-09 14:49:09 119767
CI didn't start because of a github CI incident. Let's put it as retry once it will fail.

@bors retry
2024-01-09 14:17:03 119654
> remote: Internal Server Error
fatal: unable to access 'https://github.com/BurntSushi/xsv/': The requested URL returned error: 500

@bors retry
2024-01-09 00:52:35 119732
@bors retry runner quit