top

Recent failure results

OK: 0, NG: 13, 2026-01-01 02:01:23 +0900 ~ 2026-01-04 02:01:23 +0900

trunk_asan@ruby-sp1 2026-01-03 11:08:54 +0900 NG (2f4119eaea) [LOG] 8 min 46 sec
trunk_gcc14@ruby-sp2-noble-docker 2026-01-03 09:30:18 +0900 NG (2f4119eaea) [LOG] 10 min 58 sec
trunk-iseq_binary@ruby-sp2-noble-docker 2026-01-03 02:42:44 +0900 NG (c47a8052f6) [LOG] 9 min 53 sec
trunk-random2@ruby-sp2-noble-docker 2026-01-02 23:36:45 +0900 NG (b9819ad06c) [LOG] 32 min 42 sec
master@oci-aarch64 2026-01-02 22:30:47 +0900 NG (177949c8b2) [LOG] 3 min 56 sec
trunk-random1@ruby-sp2-noble-docker 2026-01-02 20:57:24 +0900 NG (11165495f4) [LOG] 27 min 53 sec
trunk-iseq_binary@ruby-sp2-noble-docker 2026-01-02 20:44:17 +0900 NG (11165495f4) [LOG] 10 min 16 sec
trunk_asan@ruby-sp1 2026-01-02 15:42:39 +0900 NG (dd34d6273a) [LOG] 7 min 1 sec
trunk_gcc14@ruby-sp2-noble-docker 2026-01-02 11:27:51 +0900 NG (acda63debc) [LOG] 9 min 23 sec
trunk_gcc11@ruby-sp2-noble-docker 2026-01-02 03:25:05 +0900 NG (acda63debc) [LOG] 10 min 13 sec
trunk-gc-asserts@ruby-sp2-noble-docker 2026-01-01 18:37:13 +0900 NG (9d37155cfc) [LOG] 34 hour 26 min 33 sec
trunk_clang_18@ruby-sp2-noble-docker 2026-01-01 17:17:18 +0900 NG (4129256214) [LOG] 9 min 38 sec
trunk-yjit@ruby-sp2-noble-docker 2026-01-01 07:28:10 +0900 NG (7cf6cc83f3) [LOG] 6 min 39 sec

prev 3 days, next 3 days