You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I see the following note in the Usage with uv section.
Using actions/setup-python to install python and not uv install is critical for tracing to work properly.
However, I'm running on RHEL, and the Github actions hosted python setup does not have a bin for RHEL.
When I use the astral-sh/setup-uv step I get
Error: Error: failed to setup NodeJS introspection. Permission denied (os error 13)
Error: Process completed with exit code 1.
I did build the valgrind-codspeed locally and I can see the version is correct. Even on the runner:
Warning: Unofficially supported system: rhel 9.5. Continuing with best effort support.
Preparing the environment
Valgrind is already installed with the correct version, skipping installation
Environment ready
When I run codspeed run --mode instrumentation pytest ../test from my user, it runs fine. I only get this error on the actions runner. Does this have something to do with using the uv setup instead of the python setup?
Activity
adiroiban commentedon Oct 6, 2026
I think that this is somehow duplicate of #21 if rocky linux will work, RHEL should also work.
But I don't think that this is an issue with codspeed itself... it this about preparing the right self-hosted runner
RHEL might mount the tmp folder as no-exec so some actions that extract and execute things from the temporary folder might fail