Pixi list command in windows should never use cache

[tony-p]

Generated by Generative AI

No response

Operating System:

Windows

ROS version or commit hash:

rolling

RMW implementation (if applicable):

No response

RMW Configuration (if applicable):

No response

Client library (if applicable):

No response

'ros2 doctor --report' output

No response

Steps to reproduce issue

This build https://ci.ros2.org/job/ci_windows/26150/ from ament/ament_lint#563 PR

Look at output of in console/build logs

ci/windows_docker_resources/Dockerfile

Line 55 in 0ec7d4c

RUN pixi --color never --no-progress -q list

Expected behavior

The pixi list command should always run and display the output in the logs and never use a cache. list is not an expensive command, and the only purpose to run the command is to provide the list of packages in the case of debugging a failed run, so not returning the output nullifies its purpose

Actual behavior

Command only references a cached result

21:33:46 Step 18/36 : RUN pixi --color never --no-progress -q list
21:33:46  ---> Using cache
21:33:46  ---> edb348f4655b

Additional information

No response

[tony-p]

As something related, should

ci/windows_docker_resources/Dockerfile

Line 53 in 0ec7d4c

RUN powershell -noexit irm https://raw.githubusercontent.com/ros2/ros2/refs/heads/%ROS_DISTRO%/pixi.toml -OutFile pixi.toml

use an ADD command? then if the pixi.toml file changes it should know not to use the cache, whereas with the RUN command it won't actually check if the file has changed https://docs.docker.com/build/cache/invalidation/#run-instructions

[knmcguire]

Hi! just a quick comment here, now we actually add the pixi.toml file with ADD (#841), but I still see the cache issue you mentioned before in the some of the runs so that is not solving it I'm afraid

[tony-p]

Thanks, Yeah i don’t think it solves the cache issue, but i think there was also an issue where it wasn’t actually getting the last version of the pixi.toml, hopefully that should at least be fixed with using ADD (IE will always fetch latest version, but if it sees it is the same, will carry on with the cache).

I did have a bit of a look into how to force output, but seems like the only way is to basically force the cache to become dirty, but that would impact build performance I imagine