T27-49 — Run the bridge smoke against the release bytes with no skip

Aperta
  • Qualcosa non va?
#68 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
4/5
Tempo stimato
3-5 giorni
Idoneità per principianti
35/100
Tipo di issue
Bug
Chiarezza
Specificata chiaramente
Stato di attività
Attiva
Stack tecnologico
github-actions, rust, wasm
Ambito
release, testing

Direzione di ricerca

Read xtask/src/dist.rs around smoke_bridge and strip_script_bodies, then run cargo run -p xtask -- dist --web to inspect the bridge-smoke stage. The local smoke is already green; the remaining evidence is a green release-job log for run a67a760f-f404-4b4a-9c78-02bf4c4abfae on the authoritative CI host. The issue is marked IN PROGRESS and depends on that host and its release log.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

ci release

T27 row: T27-49
Work package: RP-05 — Web, CLI, source archives, production deployment
Priority: P0
Status: IN PROGRESS

Objective

Prove the exact bytes that will ship actually run in a browser — an open → apply → export round trip — rather than merely compiling.

Acceptance criteria: The release bytes complete an open → apply → exportPng → exportDocument round trip in headless Chromium; the smoke is not skipped; the verdict is read from the rendered DOM.

Inputs

The bundle from T27-48; headless Chromium; xtask/src/dist.rs (smoke_bridge, strip_script_bodies).

Authority

The repo's rule that a verdict string found in the page's own <script> source always matches and is therefore not evidence — DOM assertions must be made against the stripped page.

Stopping condition

A passing smoke run against the exact candidate bundle is recorded.

Verification

cargo run -p xtask -- dist --web (the bridge-smoke stage).

Evidence and blockers

xtask strips <script> bodies before its DOM assertions, so the verdict is read from the rendered page rather than from the page's own source — the repo's vacuous-verdict rule is honoured by construction. The bridge smoke is green locally: the 2026-11-10 xtask dist --web on branch ci/web-smoke-real-v2 reports "5 file(s), wasm 21261153 B (ceiling 21500000), manifest MANIFEST.sha256, smoke green", and the CI image now bakes chromium (156.0.8078.79).

The authoritative receipt is still outstanding: the GitForge release job log of run a67a760f-f404-4b4a-9c78-02bf4c4abfae (tag ci-smoke-20261110 → 1c7fede) must carry the smoke green verdict. Related: issue #35 tracks making the release path execute the smoke with no skip (board row T27-16).

Blocker: chromium on the authoritative CI host and a terminal, green release-job log.

Ledger: docs/tasks/T27-49-bridge-smoke-on-release-bytes.md and docs/release/EXECUTION-BOARD.md row T27-49 (these land with PR #12).
Campaign: docs/planning/release-compaign/Cross-Platform Releas.txt.

Lingua principale
Rust
Stelle
11
Fork
1
Merge medio
9h 48m
PR unite (30g)
13

Preparare l'ambiente

Questo progetto non fornisce container di sviluppo, Dockerfile né guida per i contributori, quindi l'ambiente è a tuo carico: parti dal suo README e consulta la nostra guida al primo contributo per i passaggi generali.

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di aliasfoxkde/FireCraft

Tutte le issue di aliasfoxkde/FireCraft

Issue simili

Altre issue su Rust

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.