| 2025-10-30 06:54:22 |
147935 |
@bors r- retry |
| 2025-10-30 02:05:47 |
147935 |
@bors retry |
| 2025-10-28 16:33:09 |
148177 |
@bors retry (yielding to a stable PR) |
| 2025-10-28 13:24:37 |
148178 |
Bors, these PRs have already been merged.
@bors r- retry |
| 2025-10-28 05:07:53 |
148181 |
@bors retry |
| 2025-10-28 03:15:41 |
148178 |
@bors retry
yeh looks spurious, no rustdoc chanpes in here |
| 2025-10-27 11:48:02 |
148154 |
@bors retry
Spurious CI failure, this PR did not touch rustc or mir tests in any way |
| 2025-10-26 11:16:01 |
148097 |
Failed in rollup in `aarch64-msvc-1`: https://github.com/rust-lang/rust/pull/148127#issuecomment-3448429957
@bors r- retry |
| 2025-10-25 16:29:09 |
148100 |
@bors retry |
| 2025-10-25 06:40:44 |
148075 |
No apparent error, just stopped while scraping licenses...
@bors retry |
| 2025-10-24 17:39:30 |
148073 |
Yielding to #148018 as it's release-relevant...
@bors retry |
| 2025-10-24 16:48:17 |
148065 |
Network.
> received unexpected HTTP status: 504 Gateway Timeout
@bors retry |
| 2025-10-24 09:45:17 |
147775 |
Bors why are you showing this as the current test
@bors r- retry |
| 2025-10-23 21:31:08 |
148018 |
@bors r- retry
Failed https://github.com/rust-lang/rust/pull/148041
|
| 2025-10-20 10:17:41 |
147734 |
Docker appears to be working again.
@bors retry |
| 2025-10-20 10:16:21 |
142696 |
Docker appears to be working again.
@bors retry |
| 2025-10-20 09:08:16 |
142696 |
@bors retry |
| 2025-10-20 05:15:40 |
146167 |
Yielding to enclosing rollup.
@bors retry |
| 2025-10-19 17:17:22 |
147575 |
@bors retry yield https://github.com/rust-lang/rust/pull/147884 |
| 2025-10-19 17:16:51 |
147884 |
@bors retry
https://github.com/rust-lang/rust/issues/147885 |
| 2025-10-19 09:45:08 |
147698 |
@bors retry Spurious. |
| 2025-10-17 16:35:41 |
147654 |
@bors retry |
| 2025-10-17 13:11:20 |
147654 |
Probably a spurious failure. See <https://rust-lang.zulipchat.com/#narrow/channel/242791-t-infra/topic/Repeated.20spurious.20failure.20of.20.60x86_64-mingw-1.60/with/545487472>.
@bors retry |
| 2025-10-17 05:34:41 |
147779 |
It looks like the test that made it fail is spuriously failing a lot.
@bors retry |
| 2025-10-17 01:55:48 |
147508 |
@bors retry |
| 2025-10-16 11:44:34 |
147775 |
@bors retry looks spurious
https://github.com/rust-lang/rust/pulls?q=is%3Apr+%22stress_recv_timeout_two_threads%22+is%3Aclosed |
| 2025-10-15 20:31:16 |
147508 |
@bors retry |
| 2025-10-15 14:33:11 |
147444 |
Yeah this should be retried
@bors retry |
| 2025-10-15 13:36:36 |
147720 |
Error response from daemon: Get "https://ghcr.io/v2/": context deadline exceeded (Client.Timeout exceeded while awaiting headers)
@bors retry |
| 2025-10-15 11:53:18 |
147378 |
@bors retry |
| 2025-10-15 10:17:17 |
147508 |
Uh, what?
@bors retry |
| 2025-10-15 09:49:41 |
147508 |
@bors retry |
| 2025-10-15 09:38:40 |
147508 |
Network error: @bors retry |
| 2025-10-15 09:31:29 |
147607 |
@bors retry r- |
| 2025-10-15 09:15:31 |
147378 |
@bors retry (download failure) |
| 2025-10-14 17:43:54 |
147689 |
https://github.com/rust-lang/rust/pull/147421 failed already
@bors retry r- |
| 2025-10-14 16:22:31 |
147056 |
Look like a spurious network issue?
@bors retry |
| 2025-10-14 08:55:56 |
146414 |
Hum weird. I can't access the logs. Oh well.
@bors retry |
| 2025-10-13 09:04:30 |
147502 |
@bors retry (bors seems to be stuck) |
| 2025-10-13 05:27:54 |
147502 |
@bors retry |
| 2025-10-12 20:24:31 |
147262 |
@bors retry r- |
| 2025-10-12 09:57:59 |
142390 |
Looks like a runner flaked out.
@bors retry (flaky runner) |
| 2025-10-11 15:25:05 |
147568 |
@bors retry |
| 2025-10-11 01:21:43 |
147574 |
@bors retry (clang: error: unsupported option '-print-multi-os-directory') |
| 2025-10-10 23:18:16 |
147568 |
Probably unrelated?
@bors retry
```
warning: libffi-sys@3.3.2: Configuring libffi failed with exit status: 1
error: failed to run custom build command for `libffi-sys v3.3.2`
Caused by:
process didn't exit successfully: `/checkout/obj/build/aarch64-unknown-linux-gnu/stage2-tools/release/build/libffi-sys-a7c6d49d23c92c87/build-script-build` (exit status: 101)
--- stdout
checking build system type... aarch64-unknown-linux-gnu
checking host system type... aarch64-unknown-linux-gnu
checking target system type... aarch64-unknown-linux-gnu
continue configure in default builddir "./aarch64-unknown-linux-gnu"
....exec /bin/bash .././configure "--srcdir=.." "--enable-builddir=aarch64-unknown-linux-gnu" "linux
gnu"
checking build system type... aarch64-unknown-linux-gnu
checking host system type... aarch64-unknown-linux-gnu
checking target system type... aarch64-unknown-linux-gnu
checking for gsed... sed
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for a race-free mkdir -p... ../install-sh -c -d
checking for gawk... no
checking for mawk... mawk
checking whether make sets $(MAKE)... yes
checking whether make supports nested variables... yes
checking for gcc... clang
checking whether the C compiler works... yes
checking for C compiler default output file name... a.out
checking for suffix of executables...
checking whether we are cross compiling... no
checking for suffix of object files... o
checking whether the compiler supports GNU C... yes
checking whether clang accepts -g... yes
checking for clang option to enable C11 features... none needed
checking whether clang understands -c and -o together... yes
checking whether make supports the include directive... yes (GNU style)
checking dependency style of clang... gcc3
checking for g++... g++
checking whether the compiler supports GNU C++... yes
checking whether g++ accepts -g... yes
checking for g++ option to enable C++11 features... none needed
checking dependency style of g++... gcc3
checking dependency style of clang... gcc3
checking for grep that handles long lines and -e... /usr/bin/grep
checking for egrep... /usr/bin/grep -E
checking how to print strings... printf
checking for a sed that does not truncate output... /usr/bin/sed
checking for fgrep... /usr/bin/grep -F
checking for ld used by clang... /usr/bin/ld
checking if the linker (/usr/bin/ld) is GNU ld... yes
checking for BSD- or MS-compatible name lister (nm)... /usr/bin/nm -B
checking the name lister (/usr/bin/nm -B) interface... BSD nm
checking whether ln -s works... yes
checking the maximum length of command line arguments... 3145728
checking how to convert aarch64-unknown-linux-gnu file names to aarch64-unknown-linux-gnu format... func_convert_file_noop
checking how to convert aarch64-unknown-linux-gnu file names to toolchain format... func_convert_file_noop
checking for /usr/bin/ld option to reload object files... -r
checking for file... file
checking for objdump... objdump
checking how to recognize dependent libraries... pass_all
checking for dlltool... no
checking how to associate runtime and link libraries... printf %s\n
checking for ar... ar
checking for archiver @FILE support... @
checking for strip... strip
checking for ranlib... ranlib
checking command to parse /usr/bin/nm -B output from clang object... ok
checking for sysroot... no
checking for a working dd... /usr/bin/dd
checking how to truncate binary pipes... /usr/bin/dd bs=4096 count=1
checking for mt... no
checking if : is a manifest tool... no
checking for stdio.h... yes
checking for stdlib.h... yes
checking for string.h... yes
checking for inttypes.h... yes
checking for stdint.h... yes
checking for strings.h... yes
checking for sys/stat.h... yes
checking for sys/types.h... yes
checking for unistd.h... yes
checking for dlfcn.h... yes
checking for objdir... .libs
checking if clang supports -fno-rtti -fno-exceptions... yes
checking for clang option to produce PIC... -fPIC -DPIC
checking if clang PIC flag -fPIC -DPIC works... yes
checking if clang static flag -static works... yes
checking if clang supports -c -o file.o... yes
checking if clang supports -c -o file.o... (cached) yes
checking whether the clang linker (/usr/bin/ld) supports shared libraries... yes
checking dynamic linker characteristics... GNU/Linux ld.so
checking how to hardcode library paths into programs... immediate
checking whether stripping libraries is possible... yes
checking if libtool supports shared libraries... yes
checking whether to build shared libraries... no
checking whether to build static libraries... yes
checking how to run the C++ preprocessor... g++ -E
checking for ld used by g++... /usr/bin/ld
checking if the linker (/usr/bin/ld) is GNU ld... yes
checking whether the g++ linker (/usr/bin/ld) supports shared libraries... yes
checking for g++ option to produce PIC... -fPIC -DPIC
checking if g++ PIC flag -fPIC -DPIC works... yes
checking if g++ static flag -static works... yes
checking if g++ supports -c -o file.o... yes
checking if g++ supports -c -o file.o... (cached) yes
checking whether the g++ linker (/usr/bin/ld) supports shared libraries... yes
checking dynamic linker characteristics... (cached) GNU/Linux ld.so
checking how to hardcode library paths into programs... immediate
checking for readelf... readelf
checking size of size_t... 8
checking for C compiler vendor... clang
checking CFLAGS for most reasonable warnings... -Wall
checking whether to enable maintainer-specific portions of Makefiles... no
checking for sys/memfd.h... no
checking for memfd_create... yes
checking for egrep... (cached) /usr/bin/grep -E
checking for memcpy... yes
checking for alloca.h... yes
checking size of double... 8
checking size of long double... 16
checking whether byte ordering is bigendian... no
checking assembler .cfi pseudo-op support... yes
checking whether compiler supports pointer authentication... no
checking for _ prefix in compiled symbols... no
checking whether C compiler accepts -fno-lto... yes
checking whether .eh_frame section should be read-only... yes
checking for __attribute__((visibility("hidden")))... yes
configure: versioning on shared library symbols is no
checking that generated files are newer than configure... done
configure: creating ./config.status
config.status: creating include/Makefile
config.status: creating include/ffi.h
config.status: creating Makefile
config.status: creating testsuite/Makefile
config.status: creating man/Makefile
config.status: creating doc/Makefile
config.status: creating libffi.pc
config.status: creating fficonfig.h
config.status: executing buildir commands
config.status: create top_srcdir/Makefile guessed from local Makefile
config.status: build in aarch64-unknown-linux-gnu (HOST=aarch64-unknown-linux-gnu)
config.status: executing depfiles commands
cargo:warning=Configuring libffi failed with exit status: 1
--- stderr
clang: error: unsupported option '-print-multi-os-directory'
clang: error: no input files
config.status: error: in `/checkout/obj/build/aarch64-unknown-linux-gnu/stage2-tools/aarch64-unknown-linux-gnu/release/build/libffi-sys-6562d98fd0e95724/out/libffi-build/aarch64-unknown-linux-gnu':
config.status: error: Something went wrong bootstrapping makefile fragments
for automatic dependency tracking. If GNU make was not used, consider
re-running the configure script with MAKE="gmake" (or whatever is
necessary). You can also try re-running configure with the
'--disable-dependency-tracking' option to at least be able to build
the package (albeit without support for automatic dependency tracking).
See `config.log' for more details
thread 'main' (98633) panicked at /cargo/registry/src/index.crates.io-1949cf8c6b5b557f/libffi-sys-3.3.2/build/not_msvc.rs:154:5:
Configuring libffi: exit status: 1 (cd "/checkout/obj/build/aarch64-unknown-linux-gnu/stage2-tools/aarch64-unknown-linux-gnu/release/build/libffi-sys-6562d98fd0e95724/out/libffi-build" && CC="clang" CFLAGS="-O3 -ffunction-sections -fdata-sections -fPIC -gdwarf-4 -fno-omit-frame-pointer --target=aarch64-unknown-linux-gnu -Wno-implicit-function-declaration" LC_ALL="C" "sh" "./configure" "--with-pic" "--disable-shared" "--disable-docs" "--prefix" "/checkout/obj/build/aarch64-unknown-linux-gnu/stage2-tools/aarch64-unknown-linux-gnu/release/build/libffi-sys-6562d98fd0e95724/out/libffi-root")
stack backtrace:
0: __rustc::rust_begin_unwind
at [/checkout/library/std/src/panicking.rs:698:5](https://github.com/rust-lang/rust/blob/bd928c94a5c41a0ce5f2edbf03644d239f7a50e7/library/std/src/panicking.rs#L698)
1: core::panicking::panic_fmt
at [/checkout/library/core/src/panicking.rs:80:14](https://github.com/rust-lang/rust/blob/bd928c94a5c41a0ce5f2edbf03644d239f7a50e7/library/core/src/panicking.rs#L80)
2: build_script_build::common::run_command
at ./build/common.rs:13:13
3: build_script_build::not_msvc::configure_libffi
at ./build/not_msvc.rs:154:5
4: build_script_build::not_msvc::build_and_link
at ./build/not_msvc.rs:39:5
5: build_script_build::main
at ./build/build.rs:16:9
6: core::ops::function::FnOnce::call_once
at [/checkout/library/core/src/ops/function.rs:250:5](https://github.com/rust-lang/rust/blob/bd928c94a5c41a0ce5f2edbf03644d239f7a50e7/library/core/src/ops/function.rs#L250)
note: Some details are omitted, run with `RUST_BACKTRACE=full` for a verbose backtrace.
```
|
| 2025-10-10 12:11:32 |
147551 |
What the...?^^
I don't see how this can be spurious but it also can't be this PR.^^
@bors retry libffi build script: clang: error: unsupported option '-print-multi-os-directory' |
| 2025-10-09 20:34:09 |
147508 |
@bors retry |
| 2025-10-09 07:44:10 |
146568 |
Yielding to enclosing rollup.
@bors retry (yield) |
| 2025-10-09 03:12:57 |
147492 |
@bors retry |
| 2025-10-07 20:35:21 |
147423 |
@bors retry |
| 2025-10-07 12:47:45 |
145608 |
Yielding to overarching rollup @bors retry |
| 2025-10-07 12:46:47 |
147440 |
Killed. Spurious.
@bors retry |
| 2025-10-07 11:44:51 |
145608 |
Yielding to enclosing rollup.
@bors retry |
| 2025-10-06 09:06:15 |
147392 |
@bors retry |
| 2025-10-05 06:00:11 |
147284 |
> collect2: fatal error: ld terminated with signal 7 [Bus error], core dumped
Hm, maybe spurious?
@bors retry |
| 2025-10-05 04:35:43 |
147310 |
Yielding to enclosing rollup.
@bors retry |
| 2025-10-04 22:40:45 |
147284 |
@bors retry |
| 2025-10-04 06:05:25 |
147308 |
@bors retry |
| 2025-10-04 02:54:49 |
147284 |
@bors retry |
| 2025-10-03 21:14:40 |
147284 |
Hmm, I don't see any CI changes on master for that kind of error -- maybe it was spurious?
@bors retry |
| 2025-10-03 09:02:02 |
142771 |
@bors retry (spurious network error) |
| 2025-10-02 22:55:39 |
146166 |
Looking at the rich GHA logs of the failed job `auto dist-x86_64-msvc-alt`,
I see an abrupt end at line 10655 simply containing ` Compiling rustc-main v0.0.0 (D:\a\rust\rust\compiler\rustc)`, I can't scroll further down; when I scroll back up, I can only go til line 9661; nothing suspicious except some C++ compiler warnings.
I tried to *view the raw logs* but that failed with *Failed to generate URL to download logs.*; I tried to *download log archive* but the download failed after several MBs transmitted.
This gotta be spurious!
@bors retry |
| 2025-10-01 18:16:43 |
147210 |
@bors retry |
| 2025-10-01 12:31:20 |
142771 |
> Canceling since a higher priority waiting request for CI-refs/heads/auto exists
@bors retry |
| 2025-10-01 11:26:55 |
147210 |
@bors retry bad day for MacOS? |
| 2025-10-01 04:45:09 |
147198 |
@bors retry |
| 2025-09-29 00:51:55 |
147090 |
Yielding to enclosing rollup.
@bors retry |
| 2025-09-27 09:35:58 |
147030 |
@bors retry (runner flaked out) |
| 2025-09-27 00:43:42 |
147074 |
@bors retry dist-x86_64-linux stuck after 5 hours |
| 2025-09-27 00:34:06 |
146355 |
@bors retry |
| 2025-09-25 14:16:02 |
146697 |
@bors retry (flaky) |
| 2025-09-25 07:23:56 |
146981 |
@bors retry |
| 2025-09-25 05:10:48 |
146981 |
@bors retry |
| 2025-09-25 03:38:08 |
146981 |
Still looks spurious but doesn't look like the same failure.
@bors retry |
| 2025-09-25 03:08:37 |
147003 |
@bors retry |
| 2025-09-25 00:31:36 |
146981 |
For after things get fixed,
@bors retry |
| 2025-09-24 09:54:15 |
146946 |
@bors retry |
| 2025-09-24 04:35:26 |
146946 |
@bors retry |
| 2025-09-23 18:13:05 |
146931 |
@bors retry |
| 2025-09-23 17:59:42 |
146931 |
@bors retry all the runners are aborted bc of github outage |
| 2025-09-22 10:24:22 |
145411 |
@bors retry (flaky) |
| 2025-09-22 09:47:11 |
146683 |
@bors retry curl: (35) Recv failure: Connection was reset |
| 2025-09-22 06:33:17 |
145411 |
@bors retry |
| 2025-09-22 06:32:52 |
146876 |
@bors retry (flaky) |
| 2025-09-22 06:15:03 |
145411 |
Yielding to enclosing rollup.
@bors retry |
| 2025-09-22 05:02:54 |
145411 |
Yielding to enclosing rollup.
@bors retry |
| 2025-09-22 04:12:15 |
145411 |
One of the jobs is stuck in a “queued” state with no runner, and will never complete.
@bors retry |
| 2025-09-21 21:28:33 |
145411 |
seems spurious, a codegen test can't make a rustc build fail.
@bors retry |
| 2025-09-21 04:44:05 |
144091 |
Yielding to rollup again. Sorry for the noise; CI has been flaking out.
@bors retry |
| 2025-09-21 00:35:29 |
144091 |
@bors retry same thing |
| 2025-09-21 00:35:05 |
146825 |
@bors retry timeout in rustdoc tests |
| 2025-09-20 23:09:12 |
144091 |
@bors retry rolled up |
| 2025-09-20 17:23:44 |
146744 |
@bors retry |
| 2025-09-20 16:34:42 |
146793 |
@bors retry |
| 2025-09-20 08:02:05 |
146771 |
@bors retry curl: (28) Operation too slow. Less than 10 bytes/sec transferred the last 30 seconds |
| 2025-09-19 20:54:45 |
146740 |
@bors retry r- |
| 2025-09-19 07:34:11 |
146687 |
One of the jobs flaked out and stopped making progress, hours ago. 😿
@bors retry |
| 2025-09-18 08:35:55 |
146434 |
@bors retry |