Skip to content

test(zigux): add lane16 bench build contract runner#15361

Draft
adybag14-cyber wants to merge 1 commit into
zigux-builder/lane16-phase1-bench-build-contract-20260529t1540zfrom
zigux-builder/lane16-bench-build-contract-runner-20260529t1632z
Draft

test(zigux): add lane16 bench build contract runner#15361
adybag14-cyber wants to merge 1 commit into
zigux-builder/lane16-phase1-bench-build-contract-20260529t1540zfrom
zigux-builder/lane16-bench-build-contract-runner-20260529t1632z

Conversation

@adybag14-cyber
Copy link
Copy Markdown
Owner

Summary

  • add zigux/tests/phase1_bench_build_contract_build.zig as a focused standalone Lane 16 build shard for the existing Phase 1 bench build contract on PR test(zigux): add lane16 phase1 bench build contract #15306
  • expose both a named phase1-bench-build-contract step and a plain test alias
  • keep the change one-file scoped and stacked, with no edits to the contract body, shared Phase 1 bench files, helper implementations, checker scripts, docs, fixtures, or workflows

Why This Lane

  • Lane 16 owns Phase 1 hardening gates around bench-sensitive helper packets
  • PR test(zigux): add lane16 phase1 bench build contract #15306 already carries zigux/tests/phase1_bench_build_contract.zig, but that new build-gate contract did not yet have the direct zig build route pattern used by nearby hardening follow-ups
  • this runner makes the contract directly runnable without reopening zigux/tests/phase1_bench_build.zig, zigux/tests/phase1_bench.zig, or active replay/checker fronts

Validation

  • authenticated base-branch reread confirmed zigux/tests/phase1_bench_build_contract.zig exists on branch zigux-builder/lane16-phase1-bench-build-contract-20260529t1540z
  • authenticated base-branch reread confirmed zigux/tests/phase1_bench_build_contract_build.zig returned 404 before publication
  • focused scratch validation used the attached Zigux-master.zip scaffold plus the attached Zig 0.17.0-dev.87+9b177a7d2 toolchain because direct live checkout remains unavailable in this scheduled runtime
  • overlaid the exact base-branch phase1_bench_build_contract.zig and phase1_bench_build.zig source from GitHub into scratch for the embedded-file contract check
  • zig fmt --check phase1_bench_build_contract.zig phase1_bench_build.zig phase1_bench_build_contract_build.zig
  • zig build --build-file phase1_bench_build_contract_build.zig --list-steps
    • result: step list includes phase1-bench-build-contract and test
  • zig build phase1-bench-build-contract --build-file phase1_bench_build_contract_build.zig --summary all
    • result: Build Summary: 3/3 steps succeeded; 2/2 tests passed
  • zig build test --build-file phase1_bench_build_contract_build.zig --summary all
    • result: Build Summary: 3/3 steps succeeded; 2/2 tests passed

Scope

Coordination

Validation Boundary

Direct live checkout remains unavailable in this scheduled container, so live repo grounding and publication used authenticated GitHub reads/writes plus focused scratch validation.

@coderabbitai
Copy link
Copy Markdown

coderabbitai Bot commented May 29, 2026

Important

Review skipped

Draft detected.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 8f288186-f8ed-4291-ad18-c33388473dc6

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

  • 🔍 Trigger review
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch zigux-builder/lane16-bench-build-contract-runner-20260529t1632z

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant