top

Recent failure results

OK: 0, NG: 12, 2025-07-06 19:04:42 +0900 ~ 2025-07-09 19:04:42 +0900

trunk_clang_18@ruby-sp2-noble-docker 2025-07-09 18:45:06 +0900 NG (3f0e0d5c8b) [LOG] 6 min 0 sec
trunk-gc-asserts@ruby-sp2-noble-docker 2025-07-09 15:13:23 +0900 NG (5aaedc052c) [LOG] 3 hour 49 min 52 sec
trunk-gc-asserts@ruby-sp2-noble-docker 2025-07-09 09:50:58 +0900 NG (5aaedc052c) [LOG] 1 hour 28 min 19 sec
trunk-repeat50@ruby-sp2-noble-docker 2025-07-08 15:57:08 +0900 NG (482f4cad82) [LOG] 19 hour 26 min 14 sec
trunk-random0@ruby-sp2-noble-docker 2025-07-08 15:48:19 +0900 NG (7578655767) [LOG] 20 min 3 sec
trunk-random1@ruby-sp2-noble-docker 2025-07-08 14:32:16 +0900 NG (e0841a795b) [LOG] 23 min 54 sec
trunk-gc-asserts@ruby-sp2-noble-docker 2025-07-08 05:47:34 +0900 NG (c1937480ac) [LOG] 3 hour 38 min 24 sec
trunk-yjit@ruby-sp2-noble-docker 2025-07-08 01:05:02 +0900 NG (c1937480ac) [LOG] 4 min 54 sec
master@oci-aarch64 2025-07-07 18:57:45 +0900 NG (002d746418) [LOG] 3 min 51 sec
master-no-rjit@ruby-sp2-noble-docker 2025-07-07 18:31:55 +0900 NG (002d746418) [LOG] 7 min 31 sec
trunk-gc-asserts@ruby-sp2-noble-docker 2025-07-07 15:53:27 +0900 NG (4d7e622064) [LOG] 4 hour 23 min 43 sec
trunk-gc-asserts@ruby-sp2-noble-docker 2025-07-07 02:08:52 +0900 NG (4d7e622064) [LOG] 4 hour 0 min 31 sec

prev 3 days, next 3 days