Homu retry log - rust

Time (UTC) PR Message
2024-06-16 21:18:38 126543
@bors retry
2024-06-16 08:57:05 126192
@bors retry
2024-06-14 21:43:23 126486
@bors retry no logs 
2024-06-13 23:29:55 126446
@bors retry
2024-06-13 22:38:05 126441
@bors retry
2024-06-13 22:37:43 126439
@bors p=12 retry
2024-06-13 21:13:54 125347
#126430

@bors retry
2024-06-13 20:52:59 126433
@bors retry
2024-06-13 19:58:01 126238
@bors retry
2024-06-11 00:24:09 125347
@bors retry
2024-06-10 09:40:07 125017
@bors retry
2024-06-09 06:55:47 126163
@bors retry  Put "https://ghcr.io/v2/rust-lang-ci/rust-ci/manifests/9b7a697e64f469f5512dfaf34c1674d69ace7ff101833be85272d223d5506be0ed9a4fddb9ef40696aecd8142b0b6792811934eca96004c5d16ff761f5426666": EOF
2024-06-08 14:28:01 126097
pietro commanded me to:
@bors retry
2024-06-07 04:17:26 126093
@bors retry
2024-06-06 02:12:21 125958
@bors retry
2024-06-06 00:07:02 125958
@bors retry
2024-06-05 03:47:18 125958
@bors retry
2024-06-05 03:01:05 126007
@bors retry

solaris pthread issue, sticking this back on top of the queue
2024-06-05 02:46:04 126007
@bors retry

`ln: failed to create symbolic link './usr/lib/libpthread.so': File exists` for building solaris docker image. 
2024-06-05 02:26:28 125958
@bors retry yield to that nomicon pr
2024-06-05 02:25:54 126007
spurious?
@bors clean
@bors retry
2024-06-05 02:10:57 126001
@bors retry (yielding to toolstate fix)
2024-06-05 01:16:35 126002
@bors retry (for now)
2024-06-05 00:08:41 126001
spurious @bors retry
2024-06-04 00:05:21 125380
@bors retry
2024-06-03 18:15:32 125931
@bors retry
2024-06-03 02:15:08 125752
No bors, this is a *try* job, not a merge job!
@bors r- retry
2024-05-31 14:42:52 125817
> curl: (35) Recv failure: Software caused connection abort
@bors retry
2024-05-31 00:38:21 125786
@bors retry (yielding to #125794)
2024-05-31 00:16:11 125759
@bors retry
2024-05-29 00:04:54 125613
@bors retry The runner has received a shutdown signal
2024-05-28 00:07:43 125539
blaming this one on the internet

@bors retry
2024-05-26 22:06:32 124048
@bors retry
2024-05-26 21:50:28 125025
@bors retry r- (looks like bors is confused, this PR is not approved)
2024-05-26 21:49:18 125383
@bors retry r- (this PR is not approved)
2024-05-26 21:47:59 125588
what.

@bors retry
2024-05-26 19:06:57 125413
@bors retry
2024-05-26 19:04:46 125559
@bors retry
2024-05-26 18:23:05 125576
@bors treeclosed=100 retry
2024-05-26 17:15:46 125576
@bors retry failed retrieving file 'mingw-w64-i686-libgccjit-13.2.0-3-any.pkg.tar.zst' from mirror.msys2.org
2024-05-26 15:38:34 125576
@bors retry failed retrieving file 'mingw-w64-i686-libgccjit-13.2.0-3-any.pkg.tar.zst' from mirror.msys2.org

(I thought we have our own mirrors of everything to avoid exactly this?)
2024-05-26 13:36:33 125530
@bors retry
2024-05-26 10:57:02 125508
skill issue
@bors retry
2024-05-26 06:41:12 125546
@bors retry r-
2024-05-26 04:18:05 125563
@bors retry
2024-05-26 03:52:30 125070
@bors retry (yield to rollup which includes this PR)
2024-05-26 03:51:54 125563
@bors retry
2024-05-26 01:05:50 125518
@bors retry
2024-05-25 18:17:19 125515
> error: failed retrieving file 'mingw-w64-x86_64-headers-git-11.0.0.r547.g4c8123efb-1-any.pkg.tar.zst' from mirror.msys2.org : Operation too slow. Less than 1 bytes/sec transferred the last 10 seconds
> error: failed retrieving file 'mingw-w64-x86_64-gdb-14.1-1-any.pkg.tar.zst' from mirror.msys2.org : Operation too slow. Less than 1 bytes/sec transferred the last 10 seconds
> error: failed retrieving file 'mingw-w64-x86_64-crt-git-11.0.0.r547.g4c8123efb-1-any.pkg.tar.zst' from mirror.msys2.org : Operation too slow. Less than 1 bytes/sec transferred the last 10 seconds
> warning: too many errors from mirror.msys2.org, skipping for the remainder of this transaction
> error: failed retrieving file 'mingw-w64-x86_64-openssl-3.2.0-1-any.pkg.tar.zst.sig' from mirror.umd.edu : Operation too slow. Less than 1 bytes/sec transferred the last 10 seconds
>  mingw-w64-x86_64-python-3.11.7-1-any downloading...
>  mingw-w64-x86_64-gcc-ada-13.2.0-3-any downloading...
>  mingw-w64-x86_64-gcc-objc-13.2.0-3-any downloading...
> warning: failed to retrieve some files

Seems like a temporary network problem. @bors retry

2024-05-25 15:31:02 125468
thinking emoji

@bors retry
2024-05-25 13:27:35 121571
It looks like no PRs were merged for about 12 hours but one just got through.

@bors retry
2024-05-25 13:11:23 125468
@bors retry

i dont think "slow internet" is caused by this PR
2024-05-25 07:50:46 125524
@bors retry
2024-05-25 06:52:08 125383
@bors retry r-
2024-05-25 06:47:25 125529
@bors retry
2024-05-25 06:31:00 125524
Network nonsense.
@bors retry
2024-05-25 04:49:04 121571
@bors retry
2024-05-25 02:40:25 125524
Network error?

@bors retry
2024-05-25 00:15:26 124187
@bors retry
2024-05-24 19:14:25 125468
@bors retry
2024-05-24 18:15:11 125378
@bors retry
2024-05-24 17:59:58 125499
@bors retry
2024-05-24 15:20:18 125477
@bors retry yielding to rollup
2024-05-24 15:19:37 125491
@bors retry
2024-05-24 12:04:19 125483
@bors retry r- force
2024-05-24 01:16:42 125463
spurious
@bors retry
2024-05-23 01:06:14 125425
spurious @bors retry
2024-05-22 20:13:46 125414
Huh, very odd! Must be spurious.
@bors retry
2024-05-22 11:50:44 117329
@bors retry dist-apple: curl: (28) Operation too slow. Less than 100 bytes/sec transferred the last 5 seconds
2024-05-22 08:32:24 125335
@bors retry
2024-05-21 20:28:01 125202
rustfmt test failed??
@bors retry
2024-05-20 00:06:53 120593
@bors retry 

aarch64 runner reboot
2024-05-19 15:05:22 125278
@bors retry yield to a larger rollup (#125280) since this just started testing
2024-05-19 00:06:22 99969
Can't tell what failed.

@bors retry
2024-05-17 01:28:25 124129
@bors retry The runner has received a shutdown signal
2024-05-16 21:22:27 124129
Ah, `windows-gnu`, long time no see, old friend.

*Narrator* : [earlier that day](https://github.com/rust-lang/rust/pull/122362#issuecomment-2115024346).

---

I've relaunched that computer, and while it doesn't use the same full msys as CI, I still had a i686-pc-windows-gnu toolchain from that bug investigation, and the test passes there, as expected. 

I don't see an obvious reason how that target could have been modified by this PR, so let's see if it happens again.

@bors retry 
2024-05-16 21:16:38 125150
@bors retry
2024-05-16 16:21:49 123694
@bors retry
2024-05-15 21:45:06 125157
@bors r- retry (bors seems to think this PR is approved and is not running a try-only build?)
2024-05-15 18:15:55 125157
@bors retry
2024-05-15 18:02:08 125003
@bors retry
2024-05-15 09:18:38 124975
@bors retry
2024-05-15 02:48:14 124050
@bors retry
2024-05-13 06:29:20 125055
Clearly another CI issue.

@bors retry
2024-05-13 03:15:50 125055
...failed to download tidy-html?
Let's try again.
@bors retry
2024-05-11 06:32:04 124969
>   --- stderr -------------------------------
>   thread 'main' panicked at src/tools/remote-test-client/src/main.rs:310:9:
>   client.read_exact(&mut header) failed with Connection reset by peer (os error 104)
>   note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace


Suspicious and not related. @bors retry
2024-05-09 13:03:25 124850
@bors retry
2024-05-09 09:35:42 124850
@bors retry
2024-05-08 17:22:06 124788
@bors retry r-
2024-05-07 13:09:45 124738
@bors retry

DNS…
2024-05-07 02:45:28 124813
@bors retry remote-test-client failure
2024-05-07 00:11:49 124738
Failed to push the docker image.

@bors retry
2024-05-06 17:38:14 124771
@bors retry
2024-05-05 01:18:35 124730
> ##[error]The runner has received a shutdown signal. This can happen when the runner service is stopped, or a manually started runner is canceled

@bors retry
2024-05-05 01:08:38 122662
@bors retry Connection reset by peer in remote-test-client