Repository navigation
CI: the LDBC and explanation suites run once, against a release build - #987
Merged
frankmcsherry merged 1 commit intoOct 21, 2026
Merged
Conversation
The Ubuntu stable job took about 15.5 minutes, 9 of them the SNB steps against a debug server (the update-stream fixture alone about 8), and every matrix job also built and ran the release explanation sweep. The server- backed suites and the explanation sweep now run once, in their own job alongside the matrix, against one release build: they check answers, not timings, and the matrix keeps the debug build's assertions through `cargo test`. The update-stream fixture runs at four workers, strict and in replay mode (whose reuse check runs the other worker count); the one-worker strict run is dropped. Locally the job's LDBC steps take 16 s against the release server. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_019XsakwFGwtESwZ1gSYwG4o
frankmcsherry
force-pushed
the
ddir-ci-split
branch
from
October 21, 2026 01:34
7ae92e5 to
f74b392
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
One commit, on master-next with #985 merged, changing only
.github/workflows/test.yml.Where the time went. From #986's run, the Ubuntu stable job took about 15.5 minutes:
cargo testOf the SNB steps' 9.1 minutes, the update-stream fixture took about 8: 173 s at 1 worker, 177 s at 4 workers, and 130 s in replay mode. The suites took 15–20 s each. Every matrix job, the macOS ones included, also built and ran the release explanation sweep.
The change
ldbcjob, on ubuntu-latest with stable Rust, running alongside the matrix:ddir-serverin release once;cargo testand the doc tests, so the debug build's assertions still run there.Expected effect. Locally, the new job's LDBC steps take 16 s against the release server, against about 60 s against debug. On CI I'd expect the job to be roughly a release build plus 2–3 minutes, and the matrix jobs about 3 minutes, but this PR's own run is the real measurement.
Trade-off. The LDBC programs no longer run with debug assertions, such as overflow checks, in the server. The server's own integration tests still do, in the matrix.
🤖 Generated with Claude Code
https://claude.ai/code/session_019XsakwFGwtESwZ1gSYwG4o