[qli2.0][qcs8300-ride] Ethernet test case failed #1270

Activity

1. Salendarsingh Gaud (sgaud-quic)

   assigned

   Mohd Ayaan Anwar (ayaan-anwar)

   on Oct 10, 2026
2. ayaan-anwar commented on Oct 10, 2026

   

   Mohd Ayaan Anwar (ayaan-anwar)

   on Oct 10, 2026

   Contributor

   More actions

   [PASS] 2026-10-09 02:11:05 - eth0 interface presence: driver=st_gmac carrier=1 operstate=up
   [INFO] 2026-10-09 02:11:05 - ---- Testing interface: eth0 ----
   [PASS] 2026-10-09 02:11:05 - eth0 link and IPv4: ip=10.142.127.135 speed=1000Mb/s duplex=full
   [INFO] 2026-10-09 02:11:05 - eth0 ping attempt 1/3: target=10.142.126.1
   PING 10.142.126.1 (10.142.126.1): 56 data bytes
   --- 10.142.126.1 ping statistics ---
   4 packets transmitted, 0 packets received, 100% packet loss

   The logs show a successful IP assignment via DHCP (10.142.127.135) which would mean that the ethernet data path is working fine. The ping to gateway looks to be failing though, which I think is probably due to an IT firewall blocking new devices in the internal network. The qcs8300-ride has a semi-random MAC address managed by systemd, so each new build presents as a new device to the internal network.

   I guess we can try changing this test to ping something like 8.8.8.8 instead? That might not face these firewall restrictions since its outside the intranet.
3. qcom-anilyada commented on Oct 12, 2026

   

   Anil (qcom-anilyada)

   on Oct 12, 2026

   More actions

   The script was using the device gateway as the ping target, which may fail intermittently due to the firewall.
   The PR below changes the script to ping 8.8.8.8 by default:
   qualcomm-linux/qcom-linux-testkit#614

   Validated on one of the targets: https://lava.infra.foundries.io/scheduler/job/483195

   This commit will bring those changes to meta-qcom.