Skip to content

test(e2e): re-point Tier-C kiln blocker to the durable umbrella kiln#375 (#297)#330

Merged
avrabe merged 3 commits into
mainfrom
test/297-tierc-repoint-e0bbb
Jul 10, 2026
Merged

test(e2e): re-point Tier-C kiln blocker to the durable umbrella kiln#375 (#297)#330
avrabe merged 3 commits into
mainfrom
test/297-tierc-repoint-e0bbb

Conversation

@avrabe

@avrabe avrabe commented Jul 10, 2026

Copy link
Copy Markdown
Contributor

What

Re-points tier_c_fused_executes_on_kiln's ignore reason off the now-closed kiln#382 to the durable umbrella kiln#375, with the full kiln-side layer progression documented. Test-annotation only; stays #[ignore]d.

Why

kiln#382 (E5DC2) shipped in kiln v0.4.0, so the annotation referenced a closed issue. Re-verified on post-#382 kilnd: E5DC2 is gone (component "initialized and running"), but the run export now fails [Runtime][E0BBB] Export not found. Same fused.wasm still runs on wasmtime 41 → meld's output is spec-valid; E0BBB is the next kiln-side layer, on kiln#375. Pointing at the umbrella avoids re-pointing again as kiln clears each sub-layer.

Refs #297, kiln#375.

🤖 Generated with Claude Code

…375 (#297)

kiln#382 (E5DC2) is now resolved (kiln v0.4.0), so the ignore reason pointed at
a closed issue — a future reader would wrongly try to un-ignore it. Re-verified
the seam on post-#382 kilnd: E5DC2 is gone (the component "initialized and
running"), but invoking the run export now fails with `[Runtime][E0BBB] Export
not found`. The SAME fused artifact still runs on wasmtime 41, so meld's output
stays spec-valid; E0BBB is the next kiln-side layer, documented on the
multi-core umbrella kiln#375.

Re-point the `tier_c_fused_executes_on_kiln` annotation to kiln#375 (the durable
umbrella) with the full layer progression (kiln#364 -> #382 -> E0BBB) in the
docstring, so it need not be re-pointed again as kiln fixes each sub-layer. Test
stays #[ignore]d; un-ignores when the seam fully executes.

Refs #297, kiln#375.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
@github-actions

Copy link
Copy Markdown

LS-N verification gate

58/58 approved LS entries verified

count
Passed (≥1 test, all green) 58
Failed (≥1 test failure) 0
Missing (no ls_*_NN_* test found) 0

Approved loss-scenarios.yaml entries are expected to have a
regression test named ls_<letter>_<num>_* (e.g. LS-A-11
ls_a_11_*). The gate runs each prefix via cargo test --lib --no-fail-fast and aggregates pass/fail/missing.

Failed LS entries

(none)

Missing regression tests

(none)

Updated automatically by tools/post_verification_comment.py.
Source of truth: safety/stpa/loss-scenarios.yaml.

@avrabe avrabe merged commit c216830 into main Jul 10, 2026
14 checks passed
@avrabe avrabe deleted the test/297-tierc-repoint-e0bbb branch July 10, 2026 15:19
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