Enhance test workflow by capturing JLinkRemoteServer logs and ensuring proper exit status for network scan tests

Author: PaulFirs

.github/workflows/test.yml

@@ -42,8 +42,12 @@ jobs:
           nohup JLinkRemoteServer -select usb=771850347 -device STM32F103RE -endian little -speed 4000 -if swd > remote_server.log 2>&1 &
           sleep 3
           bmlab-scan --network 127.0.0.1/32 | tee scan3.txt
+          status=$?
+          cat remote_server.log
           grep -q "Target:  *STM32F103RE" scan3.txt
           grep -q "Serial: *771850347" scan3.txt
+          exit $status
+          
 
       - name: Test 4 — bmlab-scan --network 127.0.0.1/32 -p jlink
         run: |

JLinkRemoteServer.log

@@ -0,0 +1,6 @@
+SEGGER J-Link Remote Server V8.48 LogFile
+Logging started @ 2025-12-23 08:00
+00000000 - SERVER  (0x0015 bytes): Remote Server started
+00000001 - SERVER  (0x0015 bytes): TLV Protocol: V1.0.0 
+00000056 - SERVER  (0x0026 bytes): Connected to J-Link with S/N 771850347
+00000057 - SERVER  (0x0022 bytes): Waiting for client connections...