G-Ragghianti

I'm hitting an error where dplasma can't find a header from parsec. The parsec build isn't installing it: ``` 2025-05-07T20:55:12.6393336Z /tmp/parsec/parsec/dplasma/build/src/dplrnt_wrapper.c:14:10: fatal error: parsec/data_dist/matrix/apply.h: No such file or directory 2025-05-07T20:55:12.6394495Z...

I had a look at the cmake config, and I think I see where it would need to be added. I can create a patchfile to include in this PR...

I also found a problem in the CMakeLists.txt for DPLASMA where MPIEXEC_NUMPROC_FLAGS was used instead of MPIEXEC_NUMPROC_FLAG (resulting in a failure to launch the mpi job). Now it looks like...

Found another problem where dplasma can't find HIP if using an external parsec because the default rocm directory /opt/rocm isn't added to `CMAKE_SYSTEM_PREFIX_PATH` in PaRSECConfig.cmake. I just added it to...

``` 60: Test command: /apps/spacks/2024-07-19/github_env/var/spack/environments/dplasma/.spack-env/view/bin/mpiexec "-n" "4" "./testing_dgetrf_1d" "-N" "378" "-t" "19" "-P" "1" "-x" "-v=5" 60: Working Directory: /tmp/parsec/build/dplasma/build/tests 60: Environment variables: 60: PARSEC_MCA_device_cuda_enabled=0 60: PARSEC_MCA_device_hip_enabled=0 60: PARSEC_MCA_device_level_zero_enabled=0 60:...

After thinking more about the issue of hard-coding the path to the spack install, I've decided that we can require that the environment variable be defined by the compute environment...

We do not (thank goodness).

It looks like the github-hosted runners offer this windows instance (windows-latest). If we approve the PR, we can see if it will run on github's infrastructure. I don't know if...

There is an error on the organization level of the runner config: Runners are shut down due to spending limit caps being reached. Please try raising your Actions spending limit...

I think we need to create a CI test that targets gpu_nvidia and issues the job to that runner, correct?