Add debugging output to CI test execution steps

Add diagnostic commands before running test scripts: - macOS/Linux: Show pwd, ls scripts directory, bash location/version - Windows: Show current location, list scripts directory, pwsh location/version This will help diagnose exit code 127 (command not found) errors on macOS and exit code 1 errors on Windows.
python-mode · diraol · Apr 18, 2026 · Jul 31, 2025 · Jul 31, 2025 · Nov 15, 2025
commit 872944fac6bcb53f78f30ecddb4d985795f11df2
diff --git a/.github/workflows/test.yml b/.github/workflows/test.yml
@@ -39,6 +39,10 @@ jobs:
 
     - name: Run Vader test suite
       run: |
+        pwd
+        ls -la scripts/cicd/
+        which bash
+        bash --version
         bash scripts/cicd/run_vader_tests_direct.sh
 
     - name: Upload test results
@@ -96,6 +100,10 @@ jobs:
 
     - name: Run Vader test suite
       run: |
+        pwd
+        ls -la scripts/cicd/
+        which bash
+        bash --version
         bash scripts/cicd/run_vader_tests_direct.sh
 
     - name: Upload test results
@@ -188,6 +196,10 @@ jobs:
     - name: Run Vader test suite
       shell: pwsh
       run: |
+        Get-Location
+        Get-ChildItem scripts\cicd\
+        Get-Command pwsh | Select-Object -ExpandProperty Source
+        pwsh --version
         pwsh scripts/cicd/run_vader_tests_windows.ps1
 
     - name: Upload test results