Homu retry log - rust

Time (UTC) PR Message
2024-12-10 23:09:00 134137
@bors retry
2024-12-10 21:20:49 134058
Spurious, what the-. @bors retry
2024-12-10 18:24:35 134058
@bors retry
2024-12-09 16:38:58 134064
No idea what this is, npm temporarily unavailable...?

@bors retry
2024-12-09 14:06:10 134068
@bors retry (mingw)
2024-12-09 11:51:52 134064
@bors retry
2024-12-09 07:18:56 132789
@bors retry (msvc take 2)
2024-12-09 03:23:34 132789
@bors retry
2024-12-08 19:30:51 134039
@bors retry 
2024-12-08 15:40:43 133632
@bors retry
2024-12-08 10:59:57 133632
@bors retry
2024-12-08 06:57:30 134019
@bors retry
2024-12-08 01:13:43 133988
Doesn't seem relevant.

@bors retry
2024-12-07 20:57:53 134002
@bors retry
2024-12-07 14:51:48 134002
@bors retry
2024-12-07 07:59:40 133978
@bors retry
 lets see if this is spurious, I don't see any codegen related changes in the prs, cant repro locally
2024-12-07 07:10:07 134002
@bors retry (job failed to pick up)
2024-12-06 23:19:30 133978
@bors retry
2024-12-06 16:11:03 133089
@bors retry

This PR is having an unfortunate go of it.
2024-12-06 15:00:18 133956
@bors retry spurious msvc failure
2024-12-06 11:11:35 133089
@bors retry
2024-12-06 04:58:24 133089
Looks like more Windows flakiness.

@bors retry
2024-12-05 17:56:56 133559
:(

@bors retry
2024-12-05 16:45:46 133905
@bors retry (msvc)
2024-12-05 16:45:26 133906
@bors retry (msvc)
2024-12-05 15:30:55 132789
@bors retry r-
2024-12-05 04:18:53 133877
another spurious msvc failure

@bors retry
2024-12-05 02:53:29 133877
@bors retry
2024-12-04 23:30:01 133828
@bors retry
2024-12-04 01:22:16 133799
@bors retry
2024-12-03 11:00:56 133787
@bors retry
2024-12-02 09:19:25 133728
@bors retry
2024-12-01 16:57:53 133703
@bors retry
2024-11-30 12:07:49 133499
@bors retry
2024-11-30 12:07:40 133659
@bors retry
2024-11-30 12:07:28 133658
@bors retry
2024-11-30 10:50:47 133345
@bors retry
2024-11-30 05:14:25 132047
spurious

@bors retry
2024-11-29 05:42:25 133609
Can't tell if genuine, retrying
@bors retry
2024-11-29 01:34:46 133600
@bors retry
2024-11-28 16:22:22 133409
@bors retry
2024-11-28 11:53:55 133533
@bors retry

spurrious issue i hope? 
2024-11-26 10:42:04 133365
@bors retry
2024-11-26 10:11:01 133490
oh right p=28 is more than 20 lol...
@bors retry
2024-11-26 10:09:11 133490
@bors retry

yielding to a last minute stable release backport as there is only a couple days before release
2024-11-26 05:30:55 133442
@bors retry
2024-11-25 23:25:26 133465
@bors retry

tests\run-make\avr-rjmp-offset hung on x86_64-mingw
2024-11-25 19:19:51 133447
@bors retry msvc moment
2024-11-25 14:30:51 133442
@bors retry
Yield priority to the stable release.
2024-11-25 12:08:29 133445
@bors retry
2024-11-25 01:31:59 133299
@bors retry

Timed out?
2024-11-24 16:29:23 133369
@bors retry (failed to pay msvc taxes)
2024-11-24 15:11:39 133068
@bors retry (spurious miri failure)
2024-11-22 21:29:37 132329
@bors retry

this looks like some spurious miri crash ive seen in the past
2024-11-22 04:45:08 129238
Yield to rollup

@bors retry
2024-11-22 04:43:48 133322
@bors retry
2024-11-21 19:02:02 132362
@bors retry (not even trying)
2024-11-21 05:22:36 132629
@bors retry because it smells like a random linker crash
2024-11-21 01:18:26 132629
```
Run src/ci/scripts/setup-upstream-remote.sh
Configuring https://github.com/rust-lang/rust remote as upstream.
fatal: unable to access 'https://github.com/rust-lang/rust/': Failed to connect to github.com port 443: Connection timed out
```
@bors retry Failed to connect to github.com port 443: Connection timed out
2024-11-20 08:27:35 133227
@bors retry (msvc moment)
2024-11-19 13:37:47 133205
@bors retry (msvc)
2024-11-18 12:28:38 133160
@bors retry (msvc)
2024-11-18 04:26:48 128219
That doesn't look like a failure from this change

@bors retry
2024-11-17 21:19:09 128219
@bors retry
2024-11-17 08:55:38 133120
@bors retry p=9
2024-11-16 16:09:37 133094
@bors retry

msvc debuginfo issue: https://github.com/rust-lang/rust/issues/133107
2024-11-16 14:35:56 132566
@bors retry

msvc debuginfo issue
2024-11-16 14:29:37 132569
@bors retry
2024-11-16 14:26:45 133029
@bors retry
2024-11-16 14:25:57 133097
Seriously
@bors retry
2024-11-16 14:11:07 133094
debuginfo-cdb failure doesn't seem to be a Cargo issue

@bors retry
2024-11-16 12:21:20 133097
@bors retry
2024-11-15 08:07:05 132967
@bors retry
2024-11-13 20:03:33 132997
@bors retry
2024-11-13 18:14:09 132997
@bors retry
2024-11-13 12:23:41 132556
Pinned `cc` in `library` which seems to fix it. Will follow up and try and figure out the `cc` issue

@bors retry
2024-11-12 15:19:33 132870
```
  = note: LINK : fatal error LNK1104: cannot open file 'C:\a\rust\rust\build\x86_64-pc-windows-msvc\stage1-rustc\x86_64-pc-windows-msvc\release\deps\rustc_main-d22c8966e7ff84ff.exe'␍
```
@bors retry
2024-11-12 02:50:15 132919
@bors retry
2024-11-11 16:10:50 132902
@bors retry (msvc gaming)
2024-11-11 09:10:56 132880
seems spurious?

@bors retry
2024-11-10 15:29:27 132852
@bors r=onur-ozkan  retry
2024-11-10 12:39:13 132675
@bors r- retry
2024-11-10 12:07:27 132675
@bors retry r- (yielding priority to a revert to fix a bootstrap issue)
2024-11-10 09:48:54 132675
@bors retry (msvc job couldn’t create temp dir)
2024-11-09 23:32:50 132173
@bors retry
2024-11-09 05:00:14 132584
@bors retry (unrelated timeout)
2024-11-08 21:51:25 132757
lol that definitely has nothing to do with opaques

@bors retry
2024-11-08 07:58:58 132717
@bors retry
2024-11-08 02:19:33 132733
> ```
> xcode-select: error: invalid developer directory '/Applications/Xcode_14.3.1.app'
> ```

Possibly spurious?

@bors retry
2024-11-07 01:18:41 132705
@bors retry
2024-11-05 18:37:45 132631
@bors retry
2024-11-05 07:18:22 129884
The musl job timed out?

@bors retry
2024-11-05 04:40:29 132621
@bors retry
2024-11-04 17:39:59 132594
@bors retry
2024-11-03 16:25:36 132491
@bors retry r-
2024-11-01 15:41:14 132352
@bors retry LLVM rebuild timeout
2024-11-01 12:22:12 132446
@bors retry
2024-10-31 10:18:08 132356
@bors retry (msvc spurious linker failure)
2024-10-30 17:14:37 131186
@bors retry
2024-10-30 07:48:38 128219
It looks like some CI jobs are dying, perhaps related to @raoulstrackx's comment above

1000 threads _is_ a lot, are we actually spawning that many for any other tests? I took a quick look and it seemed like the max we had was around 10, that number probably needs to be cut down.

@bors r- retry
2024-10-29 00:38:18 132277
@bors retry