You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
test(e2e): re-point Tier-C kiln blocker to the durable umbrella kiln#375 (#297) (#330)
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>
/// before the defined run instance, so it overruns). kiln#375 (cross-core user
479
-
/// imports) is the *next* layer the seam hits once #382 lands. Un-ignore when
480
-
/// kiln#382 lands (then #375 if it re-blocks); it pins the meld-to-kiln seam green.
466
+
/// `#[ignore]`d: the meld→kiln seam runs a real meld-fused `--component` wrap
467
+
/// (stubs, fused, fixup, caller core modules) on kilnd, and kiln has been
468
+
/// clearing it one layer at a time — meld's output is spec-valid throughout
469
+
/// (the SAME artifact runs on wasmtime 41: "Hello wasm component world from
470
+
/// C!", Tier A/B green), so each blocker is kiln-side.
471
+
///
472
+
/// Progression (each resolved kiln-side, then the next layer surfaced):
473
+
/// kiln#364 (`_start` gate) resolved via kiln#374; kiln#382 (E5DC2 — the
474
+
/// `resolve_command_entry` `-K` instance-import offset) resolved in kiln v0.4.0;
475
+
/// current blocker `[Runtime][E0BBB] Export not found` (the run export resolves
476
+
/// but its function isn't found), tracked on the multi-core umbrella kiln#375.
477
+
///
478
+
/// Un-ignore when kiln#375 (and any E0BBB split) lands; it then pins the
479
+
/// meld-to-kiln behavioural seam green. Pointed at the durable umbrella so it
480
+
/// need not be re-pointed as kiln fixes each sub-layer.
481
481
#[test]
482
-
#[ignore = "blocked on kiln#382: kilnd's resolve_command_entry misses the -K instance-import offset, so the wasi:cli/run export resolves to an out-of-bounds component-instance index (E5DC2) for meld's multi-core fused component; then kiln#375 (cross-core user imports) is the next layer. kiln#364 (the _start gate) is resolved"]
482
+
#[ignore = "blocked on kiln#375: meld-fused --component fails on kilnd with [Runtime][E0BBB] Export not found (the run export resolves but its function isn't found); the same artifact runs on wasmtime 41 so meld's output is spec-valid. kiln#364 (_start) and kiln#382 (E5DC2) are resolved; E0BBB is the current kiln-side layer, tracked on the multi-core umbrella kiln#375"]
483
483
fntier_c_fused_executes_on_kiln(){
484
484
ifkilnd_path().is_none(){
485
485
eprintln!("skipping Tier C: kilnd not found (set MELD_KILND or build ../../kiln)");
0 commit comments