Skip to content

Conversation

@mcbarton
Copy link
Collaborator

With this change we will now only run the tests under Valgrind for ci jobs we choose. In this PR I have set it to only run for the latest llvm for Ubuntu arm and Ubuntu x86.

@mcbarton mcbarton force-pushed the Run-Valgrind-only-for-latest-llvm branch from 72644a6 to eb2fcde Compare November 27, 2025 20:56
@codecov
Copy link

codecov bot commented Nov 27, 2025

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 79.04%. Comparing base (5534f38) to head (0c1ba2e).
⚠️ Report is 1 commits behind head on main.

Additional details and impacted files

Impacted file tree graph

@@           Coverage Diff           @@
##             main     #760   +/-   ##
=======================================
  Coverage   79.04%   79.04%           
=======================================
  Files           9        9           
  Lines        3880     3880           
=======================================
  Hits         3067     3067           
  Misses        813      813           
🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

Copy link
Collaborator

@Vipul-Cariappa Vipul-Cariappa left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM!

Hi @mcbarton, in future, make sure that the oop-jit is running with Valgrind, even if it is not the latest LLVM. I believe with the next LLVM release, we can drop the LLVM patch we have. And things will become easy. You are the CI guy, and I may forgot about this 😄.

@Vipul-Cariappa Vipul-Cariappa merged commit 63fe46d into compiler-research:main Nov 28, 2025
34 checks passed
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.

2 participants