The artifact hash prefix 0beb is ambiguous and might mean any of the following:
0beb5ea7e7aab8fecae97335f55cc5366a0161b007e7d0b1fe562eab7631074b -
- File
build.zig
— part of check-in
[fa78377389]
at
2026-09-18 12:31:12
on branch trunk
— soak: a nightly deep DST and fuzz run
scripts/soak.sh passed the optimize flag this Zig rejects, so it has been unrunnable since the toolchain moved; it takes --release=safe now. A scheduled workflow runs it at 03:00 UTC on the x64 runner with the script's nightly budgets, overridable from the dispatch form, keeps the log and any reproduce line as an artifact, and is pinned to the ci toolchain by ci_test like the other workflows. (user: dmestas, size: 36076) [annotate] [blame] [check-ins using]
- File
build.zig
— part of check-in
[fa78377389]
at
2026-09-18 12:31:12
on branch trunk
— soak: a nightly deep DST and fuzz run
0bebfabbd94e10808d7dfec0f12c4ed3f8d144c908526edfb02e60301eab0cb2 -
- File src/logstore.zig — part of check-in [f59234f6f1] at 2026-07-13 22:14:56 on branch trunk — Move the §C test asserting persisted RID order follows frame order after a phantom upgrade into the logstore sibling test file, leaving logstore.zig with only its file-private and fuzz-corpus declarations. (user: dmestas, size: 70254) [annotate] [blame] [check-ins using]