ci: Fix after Gitlab pipelines got clean HOME directory

Author: colluca

.gitlab-ci.yml

@@ -12,17 +12,15 @@ variables:
   CARGO_TARGET_X86_64_UNKNOWN_LINUX_GNU_LINKER: /usr/pack/gcc-9.2.0-af/linux-x64/bin/gcc
   LLVM_SYS_120_PREFIX: /usr/pack/llvm-12.0.1-af
   CMAKE: cmake-3.18.1
-  UV_CACHE_DIR: $CI_BUILDS_DIR/../cache/uv
 
 default:
   # Allow interrupting long-running jobs when a new pipeline on the same branch is triggered
   interruptible: true
   timeout: 60m
   before_script:
-    # The CI is configured such that the uv cache directory (`UV_CACHE_DIR`),
-    # is located on the same file system outside of the build directory.
-    # `uv` should try to hardlink files instead of copying them to save space
-    - export UV_LINK_MODE=hardlink
+    # Prevent race condition in managed Python installation,
+    # see https://github.com/astral-sh/uv/issues/19329
+    - nfslock ${HOME}/uv-ci.lock uv sync --all-extras --locked
     - source iis-setup.sh
 
 ##############

iis-setup.sh

@@ -20,12 +20,6 @@ export PATH=$PWD/util/bin:$PATH
 # Add simulator binaries to PATH
 export PATH=$PWD/target/sim/build/bin:$PATH
 
-# We use `uv` for managing python dependencies and environments
-export PATH=$PATH:/usr/local/uv
-# Copy instead link packages from global cache, since the cache is typically
-# located on a different file system (e.g. your home directory).
-export UV_LINK_MODE=copy
-
 # Initialize submodules if needed
 if git submodule status --recursive 2>/dev/null | grep -q '^-'; then
     git submodule update --init --recursive