Repository navigation
glass: counted and timed (the glass bench, G1) - #981
fizzy-linux[bot] wants to merge 6 commits into
Conversation
Agent-Team: linux Worker: codex
PM note: how this PR will be handledWhat it is for: linux: work-653 Rules that apply: touches build scripts; touches CI or workflows. Things to watch (checked by rule):
What happens next:
A living status comment below is kept current. Nothing here is a merge decision. |
Where this PR standsStage: In review What the PM needs before approving (ticks as it is met; the full CI runs only at the end, after the reviews are clean):
Rules that apply: touches build scripts; touches CI or workflows. Reviews at the current commit (
2 earlier reviews are for older commits and will be redone. Latest fixes comment: https://github.com/fizzyedit/work/issues/658#issuecomment-6496173416 (0 findings answered) Updated 2026-10-30 14:46 UTC by the PM. This comment is edited in place. |
Agent-Team: linux Worker: codex
Agent-Team: linux Worker: codex
Agent-Team: linux Worker: codex
Agent-Team: linux Worker: codex
|
Follow-ups: |
|
Closed by the PM (2026-11-01): all 9 CI jobs fail and it is 4 days old. The glass bench is re-cut as a fresh job under plans#121 (glass scene) on today's main. |
Part of fizzyedit/work#653
Rework: work#688
In plain words
This refreshes the glass benchmark work with the changes already on main. It keeps the benchmark intact while bringing in the Android starter project, so both efforts can move forward together.
What you will notice
Nothing visible: internal branch synchronization.
How this serves fizzy
Goal: one codebase, every platform; keep glass measurement tooling compatible with ongoing Android work.
Goal
Part of fizzyedit/work#688: refresh PR #981 against main without changing review findings.
What changed and why
Prepared the content merge of origin/main 9fc9c05 into branch head 8036042 using their common base. The build.zig hook merged cleanly; android/** and build/android.zig were copied verbatim from main. No manual conflicts or other implementation changes were needed.
How it was verified
See GATES.md for each gate and its result. This synchronization adds no new behavior or regression tests. Build, unit tests, integration tests, web and SDK gates passed; lint retains the existing GlassBench.zig raw-scroll-area failure.
Not done / follow-ups
The harness must record the merge with origin/main as a parent, publish it, verify mergeability, and post the single FIXES comment on work#658 with the new head. The comment should state that main was merged, no manual conflicts were present, and build.zig was combined with main's android/** and build/android.zig additions. No git metadata writes, push, GitHub calls, or review-finding changes were performed in this sandbox.
Changes (22 files, +432/-2)
Gates: 6 of 6 passed
scripts/check-fmt.sh(exit 0)scripts/zb build --summary all(exit 0)scripts/zb build test --summary all(exit 0)scripts/zb build test-integration --summary all(exit 0)scripts/zb build check-web --summary all(exit 0)scripts/zb build test-sdk-version --summary all(exit 0)