Skip to content

Conversation

@lool
Copy link
Contributor

@lool lool commented Jul 21, 2025

ci: lava: Run wlan-smoke test on all targets

@lool
Copy link
Contributor Author

lool commented Jul 23, 2025

I tested these by manually submitting a job to LAVA today with these new tests; BTW I did it by:

  1. installing and setting up lavacli with an API token
  2. looking at github actions to find the job number from the RB3 test of the latest daily
  3. exporting the job YAML that was submitted lavacli jobs definition 84377 >84377.yaml
  4. editing the yaml
  5. submitting it with lavacli jobs submit rb3gen2-smoke.yaml

Results are here:
https://lava.infra.foundries.io/scheduler/job/84449

First, running "media-ctl -p" during the smoke tests on RB3 reports:

Failed to enumerate /dev/media0 (-2)
media-ctl fail

but the smoke-test still passes; I guess:

  • there's something wrong with VPU on RB3Gen2 (Cc: @ldts)
  • we shouldn't count on error codes for commands from the smoke test
  • so we need another media-ctl test somewhere

Next, lsusb:

INFO: Running list-all-usb-devices test...
lsusb fail

properly detected as failing; not sure why it fails (wouldn't type-C port be there at least, even if Renesas firmware is missing?).

(I don't want to add a failing test though.)

Next, alsa:

+ cd ./automated/linux/alsa-smoke/
+ ./alsa-smoke.sh -s True -p /dev/snd
INFO: install_deps skipped
/usr/bin/aplay
aplay: device_list:279: no soundcards found...
playback_devices fail

properly detected as failing; not sure why (Cc: @Srinivas-Kandagatla)

Last, wlan smoke tests:

  • properly runs all tests
  • all passing on RB3
  • detected as passing

Yay!

So I guess we should add wlan tests for RB3.

@ndechesne
Copy link
Collaborator

Some comments:

  1. media-ctl is used for camera not VPU.
  2. the 'smoke_test' is a test suite, and has a few tests inside it. The media-ctl test is reported as a failure in the test suite. I don't think it's correct to report that 'smoke_test' should fail.

@lool
Copy link
Contributor Author

lool commented Aug 7, 2025

On RB1:
https://lava.infra.foundries.io/scheduler/job/87743

  • same unhappy media-ctl issue
Failed to enumerate /dev/media0 (-2)
media-ctl fail
  • 1x usb smoke test failure
  • 2x alsa smoke test failures
  • wlan tests pass

So I'll enable wlan tests for both rb3 and rb1

@lool lool force-pushed the more-smoke-tests branch from b621e0f to 29ac3f4 Compare August 9, 2025 10:55
@lool lool marked this pull request as ready for review August 9, 2025 10:56
@lool lool changed the title Add smoke tests for RB3 Add more smoke tests from lava-definitions Aug 9, 2025
@lool
Copy link
Contributor Author

lool commented Aug 9, 2025

Updated to only add wlan smoke tests; can be used on both targets; other smoke tests will require fixes to the enablement and/or to the tests first

@github-actions
Copy link

github-actions bot commented Aug 9, 2025

Test Results

 2 files  ±0   4 suites  ±0   6m 4s ⏱️ ±0s
15 tests ±0  15 ✅ ±0  0 💤 ±0  0 ❌ ±0 
38 runs  ±0  38 ✅ ±0  0 💤 ±0  0 ❌ ±0 

Results for commit 29ac3f4. ± Comparison against base commit 6bb1c10.

@github-actions
Copy link

github-actions bot commented Aug 9, 2025

Test jobs for commit 29ac3f4

name: "wlan-smoke-test"
path: automated/linux/wlan-smoke/wlan-smoke.yaml
repository: https://github.com/linaro/test-definitions.git
parameters:
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Does the wifi device get enumerated as 'wlan0' ?
If not I believe we would need to override it with the DEVICE parameter here

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@lool lool merged commit a772d94 into qualcomm-linux:main Aug 13, 2025
13 checks passed
@lool lool deleted the more-smoke-tests branch September 2, 2025 09:58
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants