Skip to content

[ci] Run the valgrind job against clang-20 and runtime 22. - #1850

Open
vgvassilev wants to merge 2 commits into
masterfrom
vg-runtime22
Open

[ci] Run the valgrind job against clang-20 and runtime 22.#1850
vgvassilev wants to merge 2 commits into
masterfrom
vg-runtime22

Conversation

@vgvassilev

Copy link
Copy Markdown
Owner

No description provided.

@github-actions

Copy link
Copy Markdown
Contributor

clang-tidy review says "All clean, LGTM! 👍"

The valgrind row trailed the support window at clang-19 / runtime 20.
Bump it to clang-20 / runtime 22 so memory checking tracks the newest
supported toolchain, matching the existing ubu24-clang20-runtime22 row.
Nearly fifty tests carried XFAIL: valgrind, which hid every memcheck
result for them -- both clad's own (now-fixed) leaks and clang's
uninitialised-value false positives in its own type machinery. A blanket
expected-failure also flips to an XPASS the moment the underlying noise
is suppressed, so it can no longer tell a real regression from a stale
marker.

Remove the markers so the refreshed clang-20 / runtime 22 valgrind row
reports each test's actual state; genuine clang-internal noise is better
handled with a targeted suppression file than by silencing whole tests.
@github-actions

Copy link
Copy Markdown
Contributor

clang-tidy review says "All clean, LGTM! 👍"

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.

1 participant