2.0 KiB
Frozen navigation source: failed Windows gate
This records the pre-correction implementation published in fdf756e6a41b1879760e45c2c263bd671b562fe3, copied from the frozen navigation checkout. Later corrections are not covered. The exact 561 input records in inputs.json were identical before and after execution. Git may normalize text line endings; this manifest identifies the actual local compiler inputs.
Command: cargo test -p oa-desktop --all-targets --locked --offline, Windows x86_64 GNU LLVM toolchain, Rust/Cargo 1.98.1, one Cargo build job, shared target directory, development debug info disabled. Raw output and process receipt are preserved. Compilation succeeded; execution finished with 876 passed, 3 failed, 1 ignored, exit 101. Test execution reported 784.33 seconds. Receipt wall time includes the host session interval and is not a compiler performance benchmark.
Failures:
app::diagram_usages::tests::port_navigation_selects_port_and_exact_visible_owner_without_editing_geometry: fixture construction returned None, unwrapped at line 175. This run did not reach its selection assertion.diagram_usage::tests::ports_are_found_at_the_visible_owner_and_unplaced_elements_do_not_match_names: fixture construction returned None, unwrapped at line 79. A direct rerun with runtime DLL paths configured reproduced the same assertion.tests::revealing_an_implicit_function_port_unfolds_its_visible_architecture_owner: the newly substitutedsaved_usages(&p, port).is_empty()assertion at line 1276 failed. The actual projected port representation must be inspected; a folded semantic owner alone is insufficient evidence that no port is painted.
This gate does not establish acceptance. Corrected fixtures/visibility and selection behavior require re-execution; core-specific outline tests, strict Clippy, a matching GUI build, and native workflows are separate pending checks. Linux/WSL remains paused by the user.