Running Awkward test suite as part of Numba-CUDA CI

[gmarkall]

I'd like to ensure that Numba-CUDA changes don't break Awkward Array by having a CI job that tests Awkward with Numba-CUDA PR branches (and release tags). I'm not sure about the best way to go about doing this - I'd like to avoid building Awkward in CI if I can, and use the latest release, but I think I might need the source repo as well for the tests.

So far I have a locally-tried flow that works like:

mamba create -n awkward-test python=3.13 awkward cupy numba-cuda pyarrow pandas
git clone --recursive [email protected]:scikit-hep/awkward.git
cd awkward
git checkout <version of awkward that was installed by mamba>
cd tests-cuda
pytest -n auto .

For a CI flow I think it'd be a bit fiddly but I could get it to check out the right tag for the installed awkward version, but I wonder if there's a better way? Are there some improvements that can be made on the above steps?

Many thanks in advance!

[ariostas]

Hi Graham, that proposal sounds good to me.

There's also some auto-generated tests that you can use. If you run nox -s prepare -- --tests it will generate tests in the tests-cuda-kernels and tests-cuda-kernels-explicit directories.

So it could be something like this

mamba create -n awkward-test python=3.13 awkward cupy numba-cuda pyarrow pandas nox
git clone --recursive [email protected]:scikit-hep/awkward.git
cd awkward
git checkout <version of awkward that was installed by mamba>
nox -s prepare -- --tests
pytest -n auto tests-cuda/ tests-cuda-kernels/ tests-cuda-kernels-explicit/