Home-Network/home-network-k3s-impl
2
0 Fork 0
Code Issues 3 Pull Requests 4 Actions Packages Projects Releases Wiki Activity

Merge conformance report-path CWD fix

Browse Source
This commit is contained in:
jakman85 committed 2026-08-17 07:40:04 -05:00
2 parents 7a45eb105a 416e16bdbf
commit ee5ad90258
1 file changed
+6
Download Patch File Download Diff File Expand all files Collapse all files
conformance/run.sh
+6
View File
@@ -137,8 +137,14 @@ run_chainsaw() {
log "Running Chainsaw over ${#dirs[@]} test dir(s) with pinned ${CHAINSAW_VERSION}" log "Running Chainsaw over ${#dirs[@]} test dir(s) with pinned ${CHAINSAW_VERSION}"
# Chainsaw writes JUnit per config/chainsaw-config.yaml (report.* under _artifacts). # Chainsaw writes JUnit per config/chainsaw-config.yaml (report.* under _artifacts).
# --report-path is passed ABSOLUTE (overriding the config's relative `_artifacts`) so the report
# write succeeds regardless of the caller's CWD — otherwise chainsaw's relative path resolves
# against $PWD and fails ("open _artifacts/chainsaw-report.xml: no such file") when run.sh is
# invoked from the repo root instead of conformance/.
mkdir -p "${ARTIFACTS}"
chainsaw test \ chainsaw test \
--config "${CONF_ROOT}/config/chainsaw-config.yaml" \ --config "${CONF_ROOT}/config/chainsaw-config.yaml" \
--report-path "${ARTIFACTS}" \
"${test_dir_args[@]}" "${test_dir_args[@]}"
# Normalize whatever chainsaw named the report to a stable path CI collects. # Normalize whatever chainsaw named the report to a stable path CI collects.