2025-01-31 15:56:31 |
136350 |
@bors retry |
2025-01-31 14:06:29 |
135763 |
I don't think windows-2025 is going to make a difference here. I'm seeing max-rss of ~2G on that TableGen invocation locally, so it does seem plausible that this could go OOM on i686, especially if parallelism is involved.
Testing a patch to cut memory usage down a bit, though it's only by about 100MB...
@bors retry |
2025-01-30 20:20:41 |
135763 |
Let's see if we can get past the OOM...
@bors retry |
2025-01-30 11:38:13 |
134824 |
@bors retry |
2025-01-30 11:36:24 |
134824 |
@bors r- retry
Job looks stuck |
2025-01-29 08:59:10 |
136227 |
@bors retry |
2025-01-29 05:46:24 |
136117 |
@bors retry runner crash |
2025-01-25 17:19:13 |
136050 |
@bors retry |
2025-01-25 15:19:57 |
119286 |
probably spurious?
```
Compiling rustc-std-workspace-core v1.99.0 (D:\a\rust\rust\library\rustc-std-workspace-core)
thread 'main' has overflowed its stack
```
@bors retry |
2025-01-25 12:39:08 |
119286 |
https://github.com/rust-lang/rust/pull/136023 was merged.
@bors retry |
2025-01-25 05:38:07 |
136038 |
bors why
@bors r- retry |
2025-01-24 08:57:56 |
135272 |
@bors retry |
2025-01-23 19:59:58 |
135925 |
@bors retry |
2025-01-23 18:43:42 |
119286 |
@bors retry spurious failed to remove file `C:\a\rust\rust\build\x86_64-pc-windows-msvc\stage1-rustc\x86_64-pc-windows-msvc\release\rustc-main.exe` |
2025-01-22 18:45:32 |
135164 |
@bors retry Network error |
2025-01-20 12:47:33 |
135632 |
@bors retry |
2025-01-20 07:51:50 |
135754 |
Really.
@bors retry |
2025-01-20 06:14:05 |
135754 |
```
[1m[31merror[0m[1m:[0m failed to remove file `C:\a\rust\rust\build\x86_64-pc-windows-msvc\stage1-rustc\x86_64-pc-windows-msvc\release\rustc-main.exe`
```
@bors retry |
2025-01-18 10:09:32 |
135675 |
@bors retry fucking hell msvc |
2025-01-18 05:31:04 |
135290 |
@bors retry
fuchsia not working
|
2025-01-18 05:24:59 |
134455 |
@bors retry
fuchsia not working |
2025-01-18 05:24:25 |
135633 |
@bors retry
fuchsia not working |
2025-01-18 05:23:46 |
135667 |
@bors retry
fuchsia not working |
2025-01-16 16:05:47 |
135483 |
@bors retry |
2025-01-16 08:42:55 |
135483 |
Well, this PR has actually changed what gets executed in the CI job that has failed :sweat_smile: But the failure is indeed spurious :)
@bors retry |
2025-01-14 17:01:17 |
132397 |
@bors retry |
2025-01-14 09:14:17 |
135442 |
> fatal: unable to access 'https://github.com/rust-lang/rust/': The requested URL returned error: 502
Today's github outage maybe?
@bors retry |
2025-01-12 17:39:00 |
135371 |
unrelated?
@bors retry rollup=maybe |
2025-01-12 08:19:28 |
135262 |
@bors retry |
2025-01-12 00:01:24 |
135262 |
Yeah, that's sadly a known flaky failure.
@bors retry |
2025-01-11 22:00:17 |
135336 |
@bors retry (#134351) |
2025-01-10 06:20:29 |
134732 |
@bors retry |
2025-01-10 00:57:33 |
135275 |
@bors retry |
2025-01-09 19:39:50 |
135297 |
@bors retry |
2025-01-09 19:39:08 |
135273 |
> downloading https://ci-artifacts.rust-lang.org/rustc-builds-alt/824759493246ee383beb9cd5ceffa0e15deb9fa4/rust-dev-nightly-x86_64-unknown-linux-gnu.tar.xz
> curl: (22) The requested URL returned error: 404
@bors retry network issue |
2025-01-09 19:31:07 |
134732 |
@bors retry
```
curl: (22) The requested URL returned error: 404
curl: (22) The requested URL returned error: 404
curl: (22) The requested URL returned error: 404
curl: (22) The requested URL returned error: 404
ERROR: failed to download llvm from ci
HELP: There could be two reasons behind this:
1) The host triple is not supported for `download-ci-llvm`.
2) Old builds get deleted after a certain time.
HELP: In either case, disable `download-ci-llvm` in your config.toml:
[llvm]
download-ci-llvm = false
``` |
2025-01-09 05:20:37 |
132607 |
@bors retry |
2025-01-09 00:39:34 |
134925 |
@bors retry r- |
2025-01-09 00:39:08 |
135001 |
This is already merged, bors.
@bors retry r- |
2025-01-08 20:56:02 |
135260 |
@bors retry |
2025-01-07 19:23:38 |
135163 |
Whoops that commit was on my work laptop, not my personal laptop :sweat_smile:
@bors retry r+ p=100 rollup=never |
2025-01-07 18:49:39 |
134523 |
@bors retry |
2025-01-07 16:04:03 |
133461 |
@bors retry
dist-aarch64-linux died in the exact same place? Maybe related to the ongoing incident? I'm really confused.
https://www.githubstatus.com/incidents/dk61qxd21mtl
|
2025-01-07 12:25:49 |
133461 |
@bors retry
dist-aarch64-linux died somewhere during the upload stage
The hosted runner: GitHub Actions 55 lost communication with the server. Anything in your workflow that terminates the runner process, starves it for CPU/Memory, or blocks its network access can cause this error.
|
2025-01-06 22:39:27 |
135162 |
Seems like the Windows file locking/removal spurious error again.
@bors retry |
2025-01-06 21:35:24 |
135173 |
@bors retry
Yield priority to the stable release. |
2025-01-06 21:35:08 |
135162 |
@bors retry
Seems like a spurious failure. |
2025-01-06 21:16:05 |
135163 |
Congrats bors you're broken.
@bors retry |
2025-01-06 19:14:38 |
135161 |
@bors retry
Yield priority to the stable release. |
2025-01-06 16:20:24 |
135159 |
@bors retry
Yielding priority to the stable release. Also, closing and opening kinda messed up bors:
![image](https://github.com/user-attachments/assets/cf3bb048-d803-42c0-84f8-0027a27711b4)
|
2025-01-06 16:20:03 |
133461 |
@bors retry
Yielding priority to the stable release. |
2025-01-06 05:26:27 |
135112 |
```text
Attempting with retry: curl -f https://ci-mirrors.rust-lang.org/rustc/clang%2Bllvm-15.0.7-x86_64-apple-darwin21.0.tar.xz -o clang+llvm-15.0.7-x86_64-apple-darwin21.0.tar.xz
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0
...
100 694M 100 694M 0 0 88.1M 0 0:00:07 0:00:07 --:--:-- 97.8M
clang+llvm-15.0.7-x86_64-apple-darwin21.0/bin/mlir-reduce: Lzma library error: Corrupted input data
```
@bors retry |
2025-01-05 23:33:11 |
135133 |
@bors retry (msvc) |
2025-01-05 17:09:59 |
135111 |
@bors retry no |
2025-01-04 02:43:32 |
135057 |
That looks very spurious. The test doesn't even have any associated types that are local.
@bors retry |
2025-01-03 14:15:37 |
135034 |
@bors retry get better at deleting files, my friend |
2025-01-02 13:28:44 |
135014 |
@bors retry (msvc link.exe spurious failure) |
2025-01-01 16:13:03 |
134080 |
@bors retry |
2025-01-01 15:20:23 |
134964 |
Looks spurious, or at least definitely unrelated to this PR.
@bors retry |
2024-12-31 22:55:11 |
134982 |
@bors retry |
2024-12-31 11:09:38 |
134620 |
@bors retry spurious i686-mingw `couldn't create a temp dir: Access is denied.` |
2024-12-30 13:03:27 |
134911 |
@bors retry 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-ccdec2f115cfff29.exe'␍ |
2024-12-30 11:56:08 |
134885 |
@bors retry tests/mir-opt/strip_debuginfo.rs#TINY "File exists" |
2024-12-29 10:17:06 |
133460 |
Looks spurious
@bors retry |
2024-12-28 01:20:15 |
131244 |
@bors retry
https://github.com/rust-lang/rust/issues/117097 |
2024-12-27 16:52:45 |
131244 |
```
= 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-03a98b8d95adfc8a.exe'␍
```
@bors retry |
2024-12-27 10:39:08 |
134816 |
@bors retry spurious apple #134220 rollup=always |
2024-12-26 20:32:09 |
134728 |
@bors retry |
2024-12-25 09:43:51 |
134703 |
You could have retried, you have the rights too on this PR normally. ;)
@bors retry |
2024-12-23 17:34:25 |
134689 |
Somehow this does not show up in the queue?
@bors retry |
2024-12-23 16:38:54 |
134687 |
@bors retry |
2024-12-22 22:53:30 |
134666 |
@bors retry |
2024-12-22 11:00:23 |
134326 |
Looks like `dist-apple-various` just got stuck?
@bors retry |
2024-12-21 22:08:29 |
130733 |
@bors retry |
2024-12-20 14:50:50 |
134559 |
Need to do another bors deploy, sorry!
@bors treeclosed=1000 retry |