Skip to content

Check artifact paths in storage deletion tests - #2231

Open
doomfrawen wants to merge 1 commit into
fluxcd:mainfrom
doomfrawen:test/storage-deletion-assertions
Open

doomfrawen wants to merge 1 commit into
fluxcd:mainfrom
doomfrawen:test/storage-deletion-assertions

Conversation

@doomfrawen

@doomfrawen doomfrawen commented Nov 6, 2026 •

Copy link
Copy Markdown

Closes #2229.

Storage tests use a leading ! to mark artifacts expected to be absent. The assertion loops retain that marker in the filesystem path, so negative checks inspect a different location. Strip it before joining the path in the five controller storage test suites.

Validation:

  • make tidy fmt vet and git diff --check passed.
  • API tests and the standalone filesystem regression passed with the race detector.
  • Full make test passed in fork CI for commit c0e6439 (11m 8s total, using the upstream workflow configuration).
  • Local full-suite execution encountered proxy and API-server startup failures also reproduced on untouched upstream; the GitHub runner completed successfully.

Prepared with Codex assistance (Assisted-by: Codex/GPT-6).

Strip the absence marker before constructing artifact paths in the
storage test assertions, so negative checks inspect the intended files.

Assisted-by: Codex/GPT-6
Signed-off-by: Ernesto Honigmann <Ernest@honigmann.ca>

Signed-off-by: doomfrawen <doomfrawen@users.noreply.github.com>
@doomfrawen
doomfrawen marked this pull request as ready for review November 6, 2026 02:23
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Storage deletion assertions retain the ! marker

1 participant