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?
I see the following note in the Usage with uv section.
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-uvstep I getI did build the
valgrind-codspeedlocally and I can see the version is correct. Even on the runner:When I run
codspeed run --mode instrumentation pytest ../testfrom 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?