Steps to replicate the issue (include links if applicable):
- push this content in ~/check.sh in a tool
#!/usr/bin/bash if [ -d "/data/project" ]; then echo "/data/project exists." else echo "/data/project isn't exist." fi if [ -d "/mnt/nfs/labstore-secondary-tools-project" ]; then echo "/mnt/nfs/labstore-secondary-tools-project exists." else echo "/mnt/nfs/labstore-secondary-tools-project isn't exist." fi
- run chmod +x ~/check.sh; toolforge jobs run test --image bullseye --command ~/check.sh -o ~/tmp.log -e ~/tmp.log --wait 10; cat ~/tmp.log
What happens?:
INFO: job 'test' completed /data/project exists. /mnt/nfs/labstore-secondary-tools-project isn't exist.
Since /data/project is a symbolic link to /mnt/nfs/labstore-secondary-tools-project on Toolforge, some tools such as pnpm will write /mnt/nfs/labstore-secondary-tools-project instead of /data/project to the file, so that it cannot be executed in the container.
What should have happened instead?:
If this is a feature that was removed on purpose, hopefully a label can be added to restore the previous behavior.