Skip to content

test(zero-rust): replay the restored zql vectors #189

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
tmm wants to merge 1 commit into from
Closed

test(zero-rust): replay the restored zql vectors #189

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
16 changes: 10 additions & 6 deletions .github/workflows/rust-nightly.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -47,11 +47,14 @@ jobs:
export SWEEP_IVM_SEED=$base SWEEP_IVM_CASES=15000
export HARDEN_IVM_SEED=$((base * 10)) HARDEN_IVM_SEEDS=5
export AGG_FUZZ_SEED=$base AGG_FUZZ_CASES=750
env | grep -E '_(SEED|SEEDS|CASES)=' | sort
# Not seeded: the restored chinook fuzzer's lane, with two-row pushes too.
export RESTORED_CHINOOK_PUSH_ROWS=1,2
env | grep -E '_(SEED|SEEDS|CASES|ROWS)=' | sort
# Five to ten times the cases outlast vitest's 10 s default; the
# job's timeout bounds them.
pnpm exec vitest run --test-timeout=600000 src/ivm/ivm.test.ts src/ivm/ivm-features.test.ts \
src/ivm/sweep-ivm.test.ts src/ivm/harden-ivm.test.ts src/client/bughunt.test.ts
src/ivm/sweep-ivm.test.ts src/ivm/harden-ivm.test.ts src/client/bughunt.test.ts \
src/ivm/restored-chinook.test.ts
- uses: actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02 # v4.6.2
with:
name: differential-vectors
Expand All @@ -78,14 +81,15 @@ jobs:
# rustup is preinstalled; rust-toolchain.toml picks the version.
- name: Install the toolchain
run: rustup show active-toolchain || rustup toolchain install
# Only the IVM corpora and the client aggregate scenarios are written,
# so the others are missing; the report still fails on any case that
# differs from JS. Both run, so one's failure doesn't hide the other's.
# Only the IVM corpora, the restored chinook lane and the client
# aggregate scenarios are written, so the others are missing; the report
# still fails on any case that differs from JS. Each runs, so one's
# failure doesn't hide another's.
- name: Compare with JS
run: |
cargo build --locked --release -p zero-conformance
status=0
for filter in ivm client-aggregates; do
for filter in ivm restored-chinook client-aggregates; do
cargo run --locked --release -p zero-conformance -- --summary "$GITHUB_STEP_SUMMARY" "$filter" || status=1
done
exit $status
Expand Down
Loading
Loading