fix(foreign): resolve Windows PATH executables with PATHEXT
CI / fmt + clippy + test (Linux x86_64) (push) Waiting to run
CI / schema instance validation + consumers (push) Waiting to run
CI / runtime contract (macos-latest) (push) Waiting to run
CI / runtime contract (windows-latest) (push) Waiting to run
Linux strict security lane (G-C) / strict isolation escape matrix (push) Waiting to run
ci/woodpecker/push/woodpecker Pipeline was successful

The built-in Python provider scanned PATH for the extension-less token
python3; a Windows PATH contains python3.exe, so a working interpreter was
reported as kernel.unavailable and the semantic golden suite failed on
windows-latest. Expand candidates with PATHEXT (conservative default) and use
the same platform-aware resolver in the conformance test's availability probe.

Also make native failures diagnosable: strip ANSI before matching and emit the
panic/build context as public check annotations, and run Linux tests through
the same annotator. This fixes the Windows native lane and gives the macOS
failure the context needed to diagnose it.
This commit is contained in:
cflmy committed 2026-11-21 18:22:22 +08:00
1 parent d441d6f4cc
commit 3a29fce061
5 files changed
+151 -20

No files matched your search

+14 -11
View File
@@ -24,7 +24,17 @@ jobs:
- name: Clippy
run: cargo clippy --workspace --all-targets -- -D warnings
- name: Tests
run: cargo test --workspace
shell: bash
run: |
set +e
CARGO_TERM_COLOR=never cargo test --workspace 2>&1 | tee workspace-tests.log
status=${PIPESTATUS[0]}
set -e
if [ "$status" -ne 0 ]; then
python3 tools/ci/annotate_workspace_tests.py \
workspace-tests.log "Linux workspace tests"
fi
exit "$status"
- name: Documentation consistency
run: cargo test -p marqdo-cli --test docs_consistency
- name: Architecture boundaries
@@ -127,19 +137,12 @@ jobs:
shell: bash
run: |
set +e
cargo test --workspace 2>&1 | tee workspace-tests.log
CARGO_TERM_COLOR=never cargo test --workspace 2>&1 | tee workspace-tests.log
status=${PIPESTATUS[0]}
set -e
if [ "$status" -ne 0 ]; then
# Surface the failing test/build context as check annotations so a
# native-matrix failure is diagnosable without admin log access.
{
grep -n -A 18 -B 2 "panicked at" workspace-tests.log || true
grep -n -A 6 -B 2 "^error" workspace-tests.log || true
grep -n "test .* FAILED" workspace-tests.log || true
} | head -80 | while IFS= read -r line; do
echo "::error title=Workspace tests on ${{ matrix.os }}::$line"
done
python3 tools/ci/annotate_workspace_tests.py \
workspace-tests.log "Workspace tests on ${{ matrix.os }}"
fi
exit "$status"
- name: Portable CLI, analysis and trace smoke