Skip to content

WIP: Validate PR #6322 dashboard cleanup on Azure CI#6323

Closed
hjmjohnson wants to merge 1 commit into
InsightSoftwareConsortium:mainfrom
hjmjohnson:wip/test-pr-6322-dashboard-cleanup
Closed

WIP: Validate PR #6322 dashboard cleanup on Azure CI#6323
hjmjohnson wants to merge 1 commit into
InsightSoftwareConsortium:mainfrom
hjmjohnson:wip/test-pr-6322-dashboard-cleanup

Conversation

@hjmjohnson
Copy link
Copy Markdown
Member

DO NOT MERGE. End-to-end validation rig for PR #6322 (the itk_common.cmake post-build/pre-test cleanup change).

The Azure pipelines clone the dashboard helper script from InsightSoftwareConsortium/ITK#dashboard in their "Download dashboard script" step. With #6322 still on the dashboard branch of my fork, Azure CI on a regular main PR would not exercise it. This WIP retargets that clone in every Azure YAML to hjmjohnson/ITK#dashboard-cleanup-objects-before-test, so the Azure pipelines on this PR's HEAD run with the modified itk_common.cmake.

What to look at in CI output

In each Azure pipeline log, between the Build and Test sections, look for the new collapsible fold:

##[group]Free build-tree object files
Removing N object/archive files from /.../ITK-build
##[endgroup]

When the fold is present, the cleanup matched files and removed them. When absent on a Windows MSVC pipeline, that's expected: this build either had no .o/.a/.obj/.lib to remove (e.g. partially-failed build) or the cleanup skipped due to dashboard_continuous/dashboard_do_coverage.

Cleanup checklist

When PR #6322 merges to upstream's dashboard branch:

  1. Close this WIP PR (or revert the single commit).
  2. Confirm the next Azure run uses upstream/dashboard again.

…cleanup branch

DO NOT MERGE.

Retargets the "Download dashboard script" step in every Azure
Pipelines YAML to clone hjmjohnson/ITK's
dashboard-cleanup-objects-before-test branch instead of
InsightSoftwareConsortium/ITK's dashboard branch.  This is the only
way to exercise the proposed itk_common.cmake change from PR InsightSoftwareConsortium#6322 on
Azure CI without first landing InsightSoftwareConsortium#6322 on the upstream dashboard branch.

When CI runs on this branch, the Azure pipelines will include the new
"Free build-tree object files" fold between ctest_build and
ctest_test.  Observing that fold (or its absence on Windows MSVC, or
on dashboard_continuous loops, or on coverage builds) validates the
production behavior end-to-end.

Revert this commit (or simply close this PR) once InsightSoftwareConsortium#6322 has been
merged onto upstream/dashboard.
@github-actions github-actions Bot added type:Infrastructure Infrastructure/ecosystem related changes, such as CMake or buildbots type:Testing Ensure that the purpose of a class is met/the results on a wide set of test cases are correct labels May 21, 2026
@hjmjohnson hjmjohnson closed this May 21, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

type:Infrastructure Infrastructure/ecosystem related changes, such as CMake or buildbots type:Testing Ensure that the purpose of a class is met/the results on a wide set of test cases are correct

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant