Windows CI failing since 2023/11/15

[traversaro]

Last successful build: https://github.com/ami-iit/onnx-cpp-benchmark/actions/runs/6858310310/job/18648845494
First failing build: https://github.com/ami-iit/onnx-cpp-benchmark/actions/runs/6872051989/job/18698893038

It fails with:

D:\a\_temp\c4468d0a-44bf-4f2e-9a4b-9e12273e9b6d.sh: line 2: pixi: command not found
D:\a\_temp\c4468d0a-44bf-4f2e-9a4b-9e12273e9b6d.sh: line 4: pixi: command not found
D:\a\_temp\c4468d0a-44bf-4f2e-9a4b-9e12273e9b6d.sh: line 5: pixi: command not found

Perhaps something changed recently in the install script? The latest modification seem prefix-dev/pixi#449 by @ruben-arts, but I could not find anything wrong there.

[ruben-arts]

This is indeed moved in that pr. I'm not sure why you needed this line:

onnx-cpp-benchmark/.github/workflows/ci.yml

Line 37 in 5eddb07

"$env:LOCALAPPDATA\pixi\bin" >> $env:GITHUB_PATH

But that should now link $Env:USERPROFILE\.pixi\bin to that github path I guess.
The script should add it to the $PATH variable, is that different from the GITHUB_PATH?

[traversaro]

Thanks @ruben-arts, and sorry for the noise, I completely forgot that part. Indeed, GitHub Actions modification to the PATH are not propagated between different steps, and the .bashrc or similar is not reloaded for new steps. So that is the reason for the workaround. However, at this point I can just switch to use the setup-pixi action.

[traversaro]

Fixed by #13 .