hw-matlab.yml: pass --skip-boot to adi-lg-matlab run (#206)

The lab's coordinator places are tagged with
boot-strategy=BootZynq7000JTAGRecovery, whose template does not yet
expose the consumer-supplied kernel/uboot/initramfs/bitstream paths a
real transition needs. Without --skip-boot, the matrix shard fails at
get_driver(boot_strategy) / strategy.transition() before MATLAB ever
starts.

With --skip-boot the shard still acquires the place and resolves the
booted board's NetworkService URI into IIO_URI; the toolbox's
test/HardwareTests.m CheckDevice gracefully reports
'No device found' when the board is not reachable. The full launcher
pipeline (acquire, resolve, MATLAB launch, JUnit, release) is
exercised. Drop the flag once the lab template carries the recovery
inputs.

Needs tfcollins/labgrid-plugins#33 (now merged); @v2 ref includes the
--skip-boot flag.

Author: tfcollins

.github/workflows/hw-matlab.yml

@@ -96,12 +96,21 @@ jobs:
         run: |
           # Place is already acquired by the composite action above, so do
           # NOT pass --acquire here (avoids double-acquire).
+          # --skip-boot: the lab's coordinator places are tagged with
+          # boot-strategy=BootZynq7000JTAGRecovery, whose template does
+          # not yet expose the consumer-supplied kernel/uboot/initramfs/
+          # bitstream paths needed for a real transition. Acquire the
+          # place and resolve its NetworkService URI; let the toolbox's
+          # CheckDevice handle reachability gracefully via assumeFail
+          # until the lab supplies those inputs (see adi-labgrid-plugins
+          # #33 for the --skip-boot mechanic).
           "$VENV_DIR/bin/adi-lg-matlab" run \
             --coord "$LG_COORDINATOR" \
             --place "${{ matrix.place }}" \
             --board-map test/hw_ci/board_map.yaml \
             --repo-dir "$GITHUB_WORKSPACE" \
             --matlab "$MATLAB_BIN" \
+            --skip-boot \
             --junit "junit-${{ matrix.place }}.xml"
 
       - name: Release place