Skip to content

workflows: update lava-test-plans to 3544131#1821

Open
qcom-anilyada wants to merge 1 commit intoqualcomm-linux:masterfrom
qcom-anilyada:test/update-ref
Open

workflows: update lava-test-plans to 3544131#1821
qcom-anilyada wants to merge 1 commit intoqualcomm-linux:masterfrom
qcom-anilyada:test/update-ref

Conversation

@qcom-anilyada
Copy link
Copy Markdown
Contributor

@qcom-anilyada qcom-anilyada commented Mar 27, 2026

here's the list of changes that comes with this ref update:

  • fix: correct device path for EXCLUDED_TESTPLANS extraction
  • workflows: upgrade actions/checkout to v6
  • devices: re-enable AudioRecord test for iq-9075-evk
  • refractor: remove test_name override capability
  • testcases: Make camera postprocessing conditional on camera testplan
  • devices: Support per-device testplan exclusion using Jinja2 template engine
  • testcases: Pass LAVA_TESTCASE_ID to prevent result collisions
  • projects: meta-qcom: fix flasher_device_type for qcs9100
  • devices: Use extensible postprocess steps for iq-x7181-evk
  • Add support for adding steps in postprocess.jinja2
  • projects: meta-qcom: disable fastrpc_test for qcs615
  • testcases: Add GStreamer video encode/decode test plan
  • templates: Add iq-x7181-evk device support
  • Add pre-merge-audio test for LAVA audio validation
  • meta-qcom-distro: add more devices
  • Fix "black" formatting warning
  • meta-qcom: disable BT tests for qcs615-ride
  • testcases: Add support for excluding all testcases in a set
  • Enable jinja2 loopcontrols extension
  • Add missing submit_to_lava function
  • projects: add flasher_device_type to devices
  • include: move flasher_device_type to internal variable

Signed-off-by: Anil Yadav anilyada@qti.qualcomm.com

@qcom-anilyada
Copy link
Copy Markdown
Contributor Author

Unit testing for all these commits has already been completed and merged. However, integration testing is still pending. I would like to request the maintainers to push this change to the next branch so it can be validated.

@ricardosalveti ricardosalveti requested a review from mwasilew March 28, 2026 05:26
@mwasilew
Copy link
Copy Markdown
Contributor

I'll push it to next. In theory the main fix we're merging is Hamoa flashing. The rest is just adding/removing tests.

@mwasilew
Copy link
Copy Markdown
Contributor

mwasilew commented Mar 30, 2026

I ran the update through next.
https://github.com/qualcomm-linux/meta-qcom/actions/runs/23736020747
There are other issues with the workflow, but I'm presenting the list of failed tests below:

"qcs9100"
    "GStreamer_Video_Encode_h264_480p",
    "core_auth",
    "AudioRecord_Config03",
    "AudioRecord_Config09",
    "OpenCV",
    "weston-simple-egl",
    "Interrupts",
    "hotplug",
    "CPUFreq_Validation",
    "GStreamer_Video_Decode_h264_480p",
    "AudioRecord",
    "GStreamer_Video_Decode_h265_480p",
    "GStreamer_Video_Encode_h265_480p",
    "BT_ON_OFF",
    "Ethernet",
    "irq",
    "WiFi_Firmware_Driver",
    "AudioRecord_Config01",
    "AudioRecord_Config07",
    "KMSCube",
    "AudioRecord_Config05",
    "fastrpc_test",
    "BT_SCAN",
    "cdsp_remoteproc",
    "DSP_AudioPD",
    "BT_FW_KMD_Service",
    "WiFi_OnOff",
    "adsp_remoteproc"

"qrb2210-rb1"
    "GStreamer_Video_Encode_h264_480p",
    "AudioRecord_Config07",
    "AudioRecord_Config01",
    "GStreamer_Video_Encode_h265_480p",
    "GStreamer_Video_Decode_h265_480p",
    "AudioRecord_Config05",
    "AudioRecord_Config03",
    "AudioRecord_Config09",
    "irq",
    "Interrupts",
    "GStreamer_Video_Decode_h264_480p"

"qcs9100-rb8"
    "BT_SCAN",
    "GStreamer_Video_Encode_h264_480p",
    "AudioRecord_Config07",
    "AudioRecord_Config01",
    "GStreamer_Video_Encode_h265_480p",
    "GStreamer_Video_Decode_h265_480p",
    "AudioRecord_Config05",
    "AudioRecord_Config03",
    "AudioRecord_Config09",
    "GStreamer_Video_Decode_h264_480p"

"qcs615-adp-air"
    "GStreamer_Video_Encode_h264_480p",
    "GStreamer_Video_Decode_h265_480p",
    "GStreamer_Video_Encode_h265_480p",
    "AudioRecord_Config01",
    "AudioRecord_Config07",
    "AudioRecord_Config05",
    "core_auth",
    "AudioRecord_Config03",
    "AudioRecord_Config09",
    "GStreamer_Video_Decode_h264_480p"

"qcs8300"
    "GStreamer_Video_Encode_h264_480p",
    "AudioRecord_Config01",
    "GStreamer_Video_Encode_h265_480p",
    "GStreamer_Video_Decode_h265_480p",
    "AudioRecord_Config07",
    "AudioRecord_Config05",
    "AudioRecord_Config03",
    "AudioRecord_Config09",
    "GStreamer_Video_Decode_h264_480p"

"qcs6490"
    "GStreamer_Video_Encode_h264_480p",
    "AudioRecord_Config01",
    "GStreamer_Video_Encode_h265_480p",
    "GStreamer_Video_Decode_h265_480p",
    "AudioRecord_Config07",
    "KMSCube",
    "AudioRecord_Config05",
    "core_auth",
    "AudioRecord_Config03",
    "AudioRecord_Config09",
    "weston-simple-egl",
    "hotplug",
    "irq",
    "GStreamer_Video_Decode_h264_480p"

If it was my call I would NAK this PR until all the issues with tests are resolved. A word of clarification - if the test result is missing, it's marked as failed.

Copy link
Copy Markdown
Contributor

@lumag lumag left a comment

Choose a reason for hiding this comment

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

@mwasilew it's definitely your call, please feel free to NAK ("request changes") for such PRs in future.

Copy link
Copy Markdown
Contributor

@mwasilew mwasilew left a comment

Choose a reason for hiding this comment

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

@qcom-anilyada please fix the reported issues:

"qcs9100"
    "GStreamer_Video_Encode_h264_480p",
    "core_auth",
    "AudioRecord_Config03",
    "AudioRecord_Config09",
    "OpenCV",
    "weston-simple-egl",
    "Interrupts",
    "hotplug",
    "CPUFreq_Validation",
    "GStreamer_Video_Decode_h264_480p",
    "AudioRecord",
    "GStreamer_Video_Decode_h265_480p",
    "GStreamer_Video_Encode_h265_480p",
    "BT_ON_OFF",
    "Ethernet",
    "irq",
    "WiFi_Firmware_Driver",
    "AudioRecord_Config01",
    "AudioRecord_Config07",
    "KMSCube",
    "AudioRecord_Config05",
    "fastrpc_test",
    "BT_SCAN",
    "cdsp_remoteproc",
    "DSP_AudioPD",
    "BT_FW_KMD_Service",
    "WiFi_OnOff",
    "adsp_remoteproc"

"qrb2210-rb1"
    "GStreamer_Video_Encode_h264_480p",
    "AudioRecord_Config07",
    "AudioRecord_Config01",
    "GStreamer_Video_Encode_h265_480p",
    "GStreamer_Video_Decode_h265_480p",
    "AudioRecord_Config05",
    "AudioRecord_Config03",
    "AudioRecord_Config09",
    "irq",
    "Interrupts",
    "GStreamer_Video_Decode_h264_480p"

"qcs9100-rb8"
    "BT_SCAN",
    "GStreamer_Video_Encode_h264_480p",
    "AudioRecord_Config07",
    "AudioRecord_Config01",
    "GStreamer_Video_Encode_h265_480p",
    "GStreamer_Video_Decode_h265_480p",
    "AudioRecord_Config05",
    "AudioRecord_Config03",
    "AudioRecord_Config09",
    "GStreamer_Video_Decode_h264_480p"

"qcs615-adp-air"
    "GStreamer_Video_Encode_h264_480p",
    "GStreamer_Video_Decode_h265_480p",
    "GStreamer_Video_Encode_h265_480p",
    "AudioRecord_Config01",
    "AudioRecord_Config07",
    "AudioRecord_Config05",
    "core_auth",
    "AudioRecord_Config03",
    "AudioRecord_Config09",
    "GStreamer_Video_Decode_h264_480p"

"qcs8300"
    "GStreamer_Video_Encode_h264_480p",
    "AudioRecord_Config01",
    "GStreamer_Video_Encode_h265_480p",
    "GStreamer_Video_Decode_h265_480p",
    "AudioRecord_Config07",
    "AudioRecord_Config05",
    "AudioRecord_Config03",
    "AudioRecord_Config09",
    "GStreamer_Video_Decode_h264_480p"

"qcs6490"
    "GStreamer_Video_Encode_h264_480p",
    "AudioRecord_Config01",
    "GStreamer_Video_Encode_h265_480p",
    "GStreamer_Video_Decode_h265_480p",
    "AudioRecord_Config07",
    "KMSCube",
    "AudioRecord_Config05",
    "core_auth",
    "AudioRecord_Config03",
    "AudioRecord_Config09",
    "weston-simple-egl",
    "hotplug",
    "irq",
    "GStreamer_Video_Decode_h264_480p"

@qcom-anilyada qcom-anilyada changed the title workflows: update lava-test-plans to c708b8f workflows: update lava-test-plans to 69d58b2 Mar 31, 2026
@qcom-anilyada qcom-anilyada changed the title workflows: update lava-test-plans to 69d58b2 workflows: update lava-test-plans to 55ad0c6 Apr 3, 2026
@lumag lumag requested review from lumag and mwasilew April 3, 2026 11:12
@ricardosalveti
Copy link
Copy Markdown
Contributor

@github-actions
Copy link
Copy Markdown

github-actions Bot commented Apr 6, 2026

Test run workflow

Test jobs for commit 133c664

Test dragonboard-820c qcs615-adp-air qcs6490 qcs8300 qcs9100 qcs9100-rb8 qrb2210-rb1
boot pass pass pass pass pass pass pass

All jobs summary

Job ID Device State Health
171161 dragonboard-820c Finished Incomplete
171145 dragonboard-820c Finished Incomplete
171142 qcs9100 Finished Complete
171155 qcs8300 Finished Complete
171166 qcs615-adp-air Finished Complete
171144 qcs8300 Finished Complete
171167 qcs9100 Finished Complete
171165 dragonboard-820c Finished Complete
171168 qrb2210-rb1 Finished Complete
171148 qcs9100 Finished Complete
171154 qcs6490 Finished Complete
171164 qcs9100-rb8 Finished Complete
171157 qcs8300 Finished Complete
171153 qcs615-adp-air Finished Complete
171162 qcs6490 Finished Complete
171159 qcs9100-rb8 Finished Complete
171156 qcs6490 Finished Complete
171151 qcs9100-rb8 Finished Complete
171158 qcs615-adp-air Finished Complete
171163 qcs8300 Finished Complete
171143 qrb2210-rb1 Finished Complete
171152 qcs9100-rb8 Finished Complete
171150 dragonboard-820c Finished Complete
171146 qrb2210-rb1 Finished Complete
171169 qcs6490 Finished Complete
171149 qcs615-adp-air Finished Complete
171160 qcs9100 Finished Complete
171147 qrb2210-rb1 Finished Complete

@test-reporting-app
Copy link
Copy Markdown

test-reporting-app Bot commented Apr 6, 2026

Test Results

 28 files   -    33   28 suites   - 236   1h 5m 51s ⏱️ - 2h 4m 12s
 14 tests  -    45    8 ✅  -    48  0 💤 ± 0   6 ❌ +3 
224 runs   - 2 257  214 ✅  - 2 247  0 💤  - 16  10 ❌ +6 

For more details on these failures, see this check.

Results for commit 7d718b3. ± Comparison against base commit f5875af.

This pull request removes 48 and adds 3 tests. Note that renamed tests count towards both.
0_BT_FW_KMD_Service ‑ BT_FW_KMD_Service
0_core_auth ‑ core_auth
0_hotplug ‑ hotplug
10_AudioRecord ‑ AudioRecord
10_Ethernet ‑ Ethernet
11_DSP_AudioPD ‑ DSP_AudioPD
11_Ethernet ‑ Ethernet
12_DSP_AudioPD ‑ DSP_AudioPD
12_fastrpc_test ‑ fastrpc_test
13_fastrpc_test ‑ fastrpc_test
…
lava ‑ auto-login-action
lava ‑ fastboot-boot
lava ‑ minimal-boot

♻️ This comment has been updated with latest results.

@mwasilew
Copy link
Copy Markdown
Contributor

mwasilew commented Apr 7, 2026

All BT tests are disabled on qcs615 and it results in a "boot test" job. This job doesn't have any overlay produced by LAVA so it fails on the postprocess step: https://lava.infra.foundries.io/scheduler/job/171231

BT_SCAN test still fails in Hyd. Possibly the Hyd devices need to have the "has-bt" tag removed.

@qcom-anilyada please address these issues.

@qcom-anilyada
Copy link
Copy Markdown
Contributor Author

BT_SCAN issue is fixed now in hyd lab, we have kept some BT devices around the setup.

Regarding qcs615, with existing setup, there's no way to deal with this. I'm trying to implement testplan exclusion, if that works it will handle such scenarios. PR#27

@ricardosalveti
Copy link
Copy Markdown
Contributor

BT_SCAN issue is fixed now in hyd lab, we have kept some BT devices around the setup.

Regarding qcs615, with existing setup, there's no way to deal with this. I'm trying to implement testplan exclusion, if that works it will handle such scenarios. PR#27

So we need qualcomm-linux/lava-test-plans#46 then, right? I would really like to get these changes in, we have way too many known failures atm.

@mwasilew
Copy link
Copy Markdown
Contributor

mwasilew commented Apr 7, 2026

So we need qualcomm-linux/lava-test-plans#46 then, right? I would really like to get these changes in, we have way too many known failures atm.

yes, pretty much. It fails unit tests at the moment. I'm waiting for the version with unit tests fixed.

@qcom-anilyada
Copy link
Copy Markdown
Contributor Author

yes, pretty much. It fails unit tests at the moment. I'm waiting for the version with unit tests fixed.

Got this fixed. All unit tests are passing now.

@ricardosalveti
Copy link
Copy Markdown
Contributor

yes, pretty much. It fails unit tests at the moment. I'm waiting for the version with unit tests fixed.

Got this fixed. All unit tests are passing now.

Please update this pr then, as the pending change was merged.

@ricardosalveti
Copy link
Copy Markdown
Contributor

Pushed to next: https://github.com/qualcomm-linux/meta-qcom/actions/runs/24284405188

Several BT failures still :-(

@bhargav0610
Copy link
Copy Markdown

Pushed to next: https://github.com/qualcomm-linux/meta-qcom/actions/runs/24284405188

Several BT failures still :-(

BT Failures looks valid from build side

[WARN] 2026-04-11 23:46:21 - bluetoothd not running, retrying in 5s...
[FAIL] 2026-04-11 23:46:26 - Bluetooth daemon not detected after 3 attempts.

@smuppand
Copy link
Copy Markdown

Pushed to next: https://github.com/qualcomm-linux/meta-qcom/actions/runs/24284405188

Several BT failures still :-(

BT Failures looks valid from build side

[WARN] 2026-04-11 23:46:21 - bluetoothd not running, retrying in 5s... [FAIL] 2026-04-11 23:46:26 - Bluetooth daemon not detected after 3 attempts.

BT failures have been noticed on RB4, and CI does not currently include RB4. Please check this as a priority and fix the environment if necessary.

@bhargav0610
Copy link
Copy Markdown

Pushed to next: https://github.com/qualcomm-linux/meta-qcom/actions/runs/24284405188

Several BT failures still :-(

BT Failures looks valid from build side
[WARN] 2026-04-11 23:46:21 - bluetoothd not running, retrying in 5s... [FAIL] 2026-04-11 23:46:26 - Bluetooth daemon not detected after 3 attempts.

BT failures have been noticed on RB4, and CI does not currently include RB4. Please check this as a priority and fix the environment if necessary.

this is new issue which is random and seeing on all targets and tracking with #1938

systemd failed while setting up Linux namespaces / sandboxing for the Bluetooth service, systemd kills the launch before bluetoothd properly starts. Further debug is in progress.

[[0;1;31mFAILED[0m] Failed to start [0;1;39mBluetooth service[0m.
See 'systemctl status bluetooth.service' for details.

systemctl status bluetooth -l
x bluetooth.service - Bluetooth service
Loaded: loaded (/usr/lib/systemd/system/bluetooth.service; enabled; preset: enabled)
Active: failed (Result: exit-code) since Thu 1970-01-01 00:02:28 UTC; 45s ago
Invocation: 3161e0c5e75748759fd1c54dc1ff4f36
Docs: man:bluetoothd(8)
Process: 699 ExecStart=/usr/libexec/bluetooth/bluetoothd (code=exited, status=226/NAMESPACE)
Main PID: 699 (code=exited, status=226/NAMESPACE)
Mem peak: 2.1M
CPU: 46ms

@smuppand
Copy link
Copy Markdown

Pushed to next: https://github.com/qualcomm-linux/meta-qcom/actions/runs/24284405188

Several BT failures still :-(

BT Failures looks valid from build side
[WARN] 2026-04-11 23:46:21 - bluetoothd not running, retrying in 5s... [FAIL] 2026-04-11 23:46:26 - Bluetooth daemon not detected after 3 attempts.

BT failures have been noticed on RB4, and CI does not currently include RB4. Please check this as a priority and fix the environment if necessary.

this is new issue which is random and seeing on all targets and tracking with #1938

systemd failed while setting up Linux namespaces / sandboxing for the Bluetooth service, systemd kills the launch before bluetoothd properly starts. Further debug is in progress.

[[0;1;31mFAILED[0m] Failed to start [0;1;39mBluetooth service[0m. See 'systemctl status bluetooth.service' for details.

systemctl status bluetooth -l x bluetooth.service - Bluetooth service Loaded: loaded (/usr/lib/systemd/system/bluetooth.service; enabled; preset: enabled) Active: failed (Result: exit-code) since Thu 1970-01-01 00:02:28 UTC; 45s ago Invocation: 3161e0c5e75748759fd1c54dc1ff4f36 Docs: man:bluetoothd(8) Process: 699 ExecStart=/usr/libexec/bluetooth/bluetoothd (code=exited, status=226/NAMESPACE) Main PID: 699 (code=exited, status=226/NAMESPACE) Mem peak: 2.1M CPU: 46ms

Thank you for bringing up the issue. Since it occurs randomly, should we proceed with the next steps?

@lumag
Copy link
Copy Markdown
Contributor

lumag commented Apr 14, 2026

Thank you for bringing up the issue. Since it occurs randomly, should we proceed with the next steps?

Yes. Once the PR is merged please rebase and retest in next.

@smuppand
Copy link
Copy Markdown

smuppand commented Apr 14, 2026

Thank you for bringing up the issue. Since it occurs randomly, should we proceed with the next steps?

Yes. Once the PR is merged please rebase and retest in next.

Thank you for bringing up the issue. Since it occurs randomly, should we proceed with the next steps?

Yes. Once the PR is merged please rebase and retest in next.

@qcom-anilyada Could you please rebase since #1919 has been merged?

@qcom-anilyada
Copy link
Copy Markdown
Contributor Author

Yes. Once the PR is merged please rebase and retest in next.

@qcom-anilyada Could you please rebase since #1919 has been merged?

did rebase and push

@smuppand smuppand requested a review from shoudil April 16, 2026 04:24
@github-actions
Copy link
Copy Markdown

Test run workflow

Test jobs for commit 862cf9e

Test dragonboard-820c qcs615-adp-air qcs6490 qcs8300 qcs9100 qcs9100-rb8 qrb2210-rb1
boot pass pass pass pass pass pass pass

All jobs summary

Job ID Device State Health
179352 qcs6490 Finished Incomplete
179358 qcs9100-rb8 Finished Complete
179359 qcs9100 Finished Complete
179351 qcs9100 Finished Complete
179342 qcs615-adp-air Finished Complete
179353 qrb2210-rb1 Finished Complete
179348 qcs615-adp-air Finished Complete
179339 dragonboard-820c Finished Complete
179356 qcs8300 Finished Complete
179355 qcs9100-rb8 Finished Complete
179349 qcs615-adp-air Finished Complete
179350 qcs9100 Finished Incomplete
179336 qcs9100-rb8 Finished Complete
179341 qcs8300 Finished Complete
179354 dragonboard-820c Finished Complete
179340 qrb2210-rb1 Finished Complete
179335 qcs6490 Finished Complete
179345 qcs6490 Finished Complete
179346 qcs8300 Finished Complete
179337 dragonboard-820c Finished Complete
179347 qcs9100-rb8 Finished Complete
179334 dragonboard-820c Finished Complete
179360 qrb2210-rb1 Finished Complete
179344 qcs9100 Finished Complete
179361 qcs8300 Finished Complete
179343 qcs615-adp-air Finished Complete
179338 qcs6490 Finished Complete
179357 qrb2210-rb1 Finished Complete

@mwasilew
Copy link
Copy Markdown
Contributor

I pushed to next https://github.com/qualcomm-linux/meta-qcom/actions/runs/24502167506
It's using the latest ref from lava-test-plans: qualcomm-linux/lava-test-plans@3544131

@qcom-anilyada qcom-anilyada changed the title workflows: update lava-test-plans to 396e0b1 workflows: update lava-test-plans to 3544131 Apr 16, 2026
@qcom-anilyada
Copy link
Copy Markdown
Contributor Author

I pushed to next https://github.com/qualcomm-linux/meta-qcom/actions/runs/24502167506 It's using the latest ref from lava-test-plans: qualcomm-linux/lava-test-plans@3544131

I've updated the ref as well in this PR.

@github-actions
Copy link
Copy Markdown

Test run workflow

Test jobs for commit 942a576

Test dragonboard-820c qcs615-adp-air qcs6490 qcs8300 qcs9100 qcs9100-rb8 qrb2210-rb1
boot pass pass pass pass pass pass pass

All jobs summary

Job ID Device State Health
179628 qcs9100 Finished Complete
179615 dragonboard-820c Finished Complete
179624 qcs615-adp-air Finished Complete
179607 qcs615-adp-air Finished Complete
179609 qcs8300 Finished Complete
179605 dragonboard-820c Finished Complete
179632 qcs9100 Finished Complete
179620 qcs6490 Finished Complete
179622 qcs6490 Finished Complete
179616 qcs615-adp-air Finished Complete
179623 qcs9100-rb8 Finished Complete
179619 dragonboard-820c Finished Complete
179630 qcs6490 Finished Complete
179618 qcs9100 Finished Complete
179626 qrb2210-rb1 Finished Complete
179611 qcs8300 Finished Complete
179631 qcs615-adp-air Finished Complete
179606 qrb2210-rb1 Finished Complete
179608 qrb2210-rb1 Finished Complete
179614 qcs6490 Finished Complete
179610 qcs8300 Finished Complete
179621 dragonboard-820c Finished Complete
179617 qcs8300 Finished Complete
179627 qcs9100 Finished Complete
179625 qcs9100-rb8 Finished Complete
179629 qrb2210-rb1 Finished Complete
179613 qcs9100-rb8 Finished Complete

@mwasilew
Copy link
Copy Markdown
Contributor

Hamoa fails to boot. I'll exclude it from the list in next

here's the list of changes that comes with this ref update:
- fix: correct device path for EXCLUDED_TESTPLANS extraction
- workflows: upgrade actions/checkout to v6
- devices: re-enable AudioRecord test for iq-9075-evk
- refractor: remove test_name override capability
- testcases: Make camera postprocessing conditional on camera testplan
- devices: Support per-device testplan exclusion using Jinja2 template engine
- testcases: Pass LAVA_TESTCASE_ID to prevent result collisions
- projects: meta-qcom: fix flasher_device_type for qcs9100
- devices: Use extensible postprocess steps for iq-x7181-evk
- Add support for adding steps in postprocess.jinja2
- projects: meta-qcom: disable fastrpc_test for qcs615
- testcases: Add GStreamer video encode/decode test plan
- templates: Add iq-x7181-evk device support
- Add pre-merge-audio test for LAVA audio validation
- meta-qcom-distro: add more devices
- Fix "black" formatting warning
- meta-qcom: disable BT tests for qcs615-ride
- testcases: Add support for excluding all testcases in a set
- Enable jinja2 loopcontrols extension
- Add missing submit_to_lava function
- projects: add flasher_device_type to devices
- include: move flasher_device_type to internal variable

Signed-off-by: Anil Yadav <anilyada@qti.qualcomm.com>
@qcom-anilyada
Copy link
Copy Markdown
Contributor Author

did rebase.

Hamoa fails to boot. I'll exclude it from the list in next

the workflow failed on build step for some targets:
https://github.com/qualcomm-linux/meta-qcom/actions/runs/24511752498

@github-actions
Copy link
Copy Markdown

Test run workflow

Test jobs for commit 7d718b3

Test dragonboard-820c qcs615-adp-air qcs6490 qcs8300 qcs9100 qcs9100-rb8 qrb2210-rb1
boot pass pass pass pass pass pass pass

All jobs summary

Job ID Device State Health
180639 qcs8300 Finished Complete
180635 qcs615-adp-air Finished Complete
180647 qcs9100 Finished Complete
180651 qcs9100-rb8 Finished Complete
180636 dragonboard-820c Finished Complete
180644 qcs9100 Finished Complete
180643 qcs8300 Finished Complete
180632 qrb2210-rb1 Finished Complete
180633 qcs615-adp-air Finished Complete
180655 qcs6490 Finished Incomplete
180658 qrb2210-rb1 Finished Complete
180638 qcs9100-rb8 Finished Complete
180642 qcs6490 Finished Complete
180634 qrb2210-rb1 Finished Complete
180659 qcs6490 Finished Complete
180649 qcs615-adp-air Finished Complete
180656 dragonboard-820c Finished Complete
180657 qcs8300 Finished Complete
180645 qcs9100-rb8 Finished Complete
180653 dragonboard-820c Finished Incomplete
180652 qcs9100 Finished Complete
180648 qcs9100-rb8 Finished Complete
180650 qrb2210-rb1 Finished Complete
180640 dragonboard-820c Finished Complete
180637 qcs615-adp-air Finished Complete
180654 qcs8300 Finished Complete
180641 qcs9100 Finished Complete
180646 qcs6490 Finished Complete

@bhargav0610
Copy link
Copy Markdown

did rebase.

Hamoa fails to boot. I'll exclude it from the list in next

the workflow failed on build step for some targets: https://github.com/qualcomm-linux/meta-qcom/actions/runs/24511752498

rb3gen2 bootup issue https://lava.infra.foundries.io/results/180655
18.214791] Calling EFI runtime from NMI context
[ 18.614149] ---[ end Kernel panic - not syncing: Asynchronous SError Interrupt ]---

but other things went well

@smuppand
Copy link
Copy Markdown

did rebase.

Hamoa fails to boot. I'll exclude it from the list in next

the workflow failed on build step for some targets: https://github.com/qualcomm-linux/meta-qcom/actions/runs/24511752498

rb3gen2 bootup issue https://lava.infra.foundries.io/results/180655 18.214791] Calling EFI runtime from NMI context [ 18.614149] ---[ end Kernel panic - not syncing: Asynchronous SError Interrupt ]---

The nightly jobs do not display this crash for Kodiak.

but other things went well

@bhargav0610
Copy link
Copy Markdown

did rebase.

Hamoa fails to boot. I'll exclude it from the list in next

the workflow failed on build step for some targets: https://github.com/qualcomm-linux/meta-qcom/actions/runs/24511752498

rb3gen2 bootup issue https://lava.infra.foundries.io/results/180655 18.214791] Calling EFI runtime from NMI context [ 18.614149] ---[ end Kernel panic - not syncing: Asynchronous SError Interrupt ]---

The nightly jobs do not display this crash for Kodiak.

but other things went well

yes, correct we are not seeing this issue in nightly builds

@mwasilew
Copy link
Copy Markdown
Contributor

Here are the current issues:

[INFO] 2026-03-13 15:38:33 - ------------------------------------------------------------
[INFO] 2026-03-13 15:38:33 - Starting BT_ON_OFF Testcase
[INFO] 2026-03-13 15:38:33 - Checking dependency: bluetoothctl
[INFO] 2026-03-13 15:38:33 - Checking if bluetoothd is running...
[INFO] 2026-03-13 15:38:33 - bluetoothd is running
[INFO] 2026-03-13 15:38:33 - Using adapter: hci0
[WARN] 2026-03-13 15:38:33 - bluetoothctl list returned no controllers in non-interactive mode.
[WARN] 2026-03-13 15:38:33 - On minimal/ramdisk images this can be normal; interactive bluetoothctl may still work.
[INFO] 2026-03-13 15:38:33 - Proceeding with interactive bluetoothctl for controller queries (non-interactive output incomplete on some images).
[WARN] 2026-03-13 15:38:33 - Bluetooth diagnostics: controller visibility is inconsistent
[WARN] 2026-03-13 15:38:33 - Adapter: hci0
[WARN] 2026-03-13 15:38:33 - hciconfig output:
[BT-DIAG] hci0:	Type: Primary  Bus: UART
[BT-DIAG] 	BD Address: 44:F7:9F:BB:67:AC  ACL MTU: 1024:7  SCO MTU: 240:4
[BT-DIAG] 	DOWN 
[BT-DIAG] 	RX bytes:2299 acl:0 sco:0 events:94 errors:0
[BT-DIAG] 	TX bytes:166801 acl:0 sco:0 commands:721 errors:0
[WARN] 2026-03-13 15:38:33 - systemctl status bluetooth:
[BT-DIAG] * bluetooth.service - Bluetooth service
[BT-DIAG]      Loaded: loaded (/usr/lib/systemd/system/bluetooth.service; enabled; preset: enabled)
[BT-DIAG]      Active: active (running) since Fri 2026-03-13 15:35:15 UTC; 3min 18s ago
[BT-DIAG]  Invocation: 211d632a4df14e91950327d3c0f880f9
[BT-DIAG]        Docs: man:bluetoothd(8)
[BT-DIAG]    Main PID: 730 (bluetoothd)
[BT-DIAG]      Status: "Running"
[BT-DIAG]       Tasks: 1 (limit: 40613)
[BT-DIAG]      Memory: 2.9M (peak: 3.4M)
[BT-DIAG]         CPU: 34ms
[BT-DIAG]      CGroup: /system.slice/bluetooth.service
[BT-DIAG]              `-730 /usr/libexec/bluetooth/bluetoothd
[BT-DIAG] 
[BT-DIAG] Mar 13 15:35:15 iq-9075-evk bluetoothd[730]: Endpoint registered: sender=:1.10 path=/MediaEndpoint/A2DPSource/aptx_ll_0
[BT-DIAG] Mar 13 15:35:15 iq-9075-evk bluetoothd[730]: Endpoint registered: sender=:1.10 path=/MediaEndpoint/A2DPSource/aptx_ll_duplex_1
[BT-DIAG] Mar 13 15:35:15 iq-9075-evk bluetoothd[730]: Endpoint registered: sender=:1.10 path=/MediaEndpoint/A2DPSource/aptx_ll_duplex_0
[BT-DIAG] Mar 13 15:35:15 iq-9075-evk bluetoothd[730]: Endpoint registered: sender=:1.10 path=/MediaEndpoint/A2DPSource/faststream
[BT-DIAG] Mar 13 15:35:15 iq-9075-evk bluetoothd[730]: Endpoint registered: sender=:1.10 path=/MediaEndpoint/A2DPSource/faststream_duplex
[BT-DIAG] Mar 13 15:35:15 iq-9075-evk bluetoothd[730]: Endpoint registered: sender=:1.10 path=/MediaEndpoint/A2DPSink/opus_05
[BT-DIAG] Mar 13 15:35:15 iq-9075-evk bluetoothd[730]: Endpoint registered: sender=:1.10 path=/MediaEndpoint/A2DPSource/opus_05
[BT-DIAG] Mar 13 15:35:15 iq-9075-evk bluetoothd[730]: Endpoint registered: sender=:1.10 path=/MediaEndpoint/A2DPSink/opus_05_duplex
[BT-DIAG] Mar 13 15:35:15 iq-9075-evk bluetoothd[730]: Endpoint registered: sender=:1.10 path=/MediaEndpoint/A2DPSource/opus_05_duplex
[BT-DIAG] Mar 13 15:35:17 iq-9075-evk bluetoothd[730]: Failed to set mode: Authentication Failed (0x05)
[WARN] 2026-03-13 15:38:33 - journalctl -u bluetooth -b (tail):
[BT-DIAG] Mar 13 15:35:14 iq-9075-evk systemd[1]: Starting Bluetooth service...
[BT-DIAG] Mar 13 15:35:14 iq-9075-evk (bluetoothd)[730]: bluetooth.service: ConfigurationDirectory 'bluetooth' already exists but the mode is different. (File system: 755 ConfigurationDirectoryMode: 555)
[BT-DIAG] Mar 13 15:35:14 iq-9075-evk bluetoothd[730]: Bluetooth daemon 5.86
[BT-DIAG] Mar 13 15:35:15 iq-9075-evk bluetoothd[730]: Starting SDP server
[BT-DIAG] Mar 13 15:35:15 iq-9075-evk bluetoothd[730]: Bluetooth management interface 1.23 initialized
[BT-DIAG] Mar 13 15:35:15 iq-9075-evk bluetoothd[730]: Battery Provider Manager created
[BT-DIAG] Mar 13 15:35:15 iq-9075-evk bluetoothd[730]: Failed to set default system config for hci0
[BT-DIAG] Mar 13 15:35:15 iq-9075-evk systemd[1]: Started Bluetooth service.
[BT-DIAG] Mar 13 15:35:15 iq-9075-evk bluetoothd[730]: /usr/src/debug/bluez5/5.86/src/profile.c:register_profile() :1.10 tried to register 0000111e-0000-1000-8000-00805f9b34fb which is already registered
[BT-DIAG] Mar 13 15:35:15 iq-9075-evk bluetoothd[730]: Endpoint registered: sender=:1.10 path=/MediaEndpoint/A2DPSink/aptx_hd
[BT-DIAG] Mar 13 15:35:15 iq-9075-evk bluetoothd[730]: Endpoint registered: sender=:1.10 path=/MediaEndpoint/A2DPSource/aptx_hd
[BT-DIAG] Mar 13 15:35:15 iq-9075-evk bluetoothd[730]: Endpoint registered: sender=:1.10 path=/MediaEndpoint/A2DPSink/aptx
[BT-DIAG] Mar 13 15:35:15 iq-9075-evk bluetoothd[730]: Endpoint registered: sender=:1.10 path=/MediaEndpoint/A2DPSource/aptx
[BT-DIAG] Mar 13 15:35:15 iq-9075-evk bluetoothd[730]: Endpoint registered: sender=:1.10 path=/MediaEndpoint/A2DPSink/opus_g
[BT-DIAG] Mar 13 15:35:15 iq-9075-evk bluetoothd[730]: Endpoint registered: sender=:1.10 path=/MediaEndpoint/A2DPSource/opus_g
[BT-DIAG] Mar 13 15:35:15 iq-9075-evk bluetoothd[730]: Endpoint registered: sender=:1.10 path=/MediaEndpoint/A2DPSink/sbc
[BT-DIAG] Mar 13 15:35:15 iq-9075-evk bluetoothd[730]: Endpoint registered: sender=:1.10 path=/MediaEndpoint/A2DPSource/sbc
[BT-DIAG] Mar 13 15:35:15 iq-9075-evk bluetoothd[730]: Endpoint registered: sender=:1.10 path=/MediaEndpoint/A2DPSource/aptx_ll_1
[BT-DIAG] Mar 13 15:35:15 iq-9075-evk bluetoothd[730]: Endpoint registered: sender=:1.10 path=/MediaEndpoint/A2DPSource/aptx_ll_0
[BT-DIAG] Mar 13 15:35:15 iq-9075-evk bluetoothd[730]: Endpoint registered: sender=:1.10 path=/MediaEndpoint/A2DPSource/aptx_ll_duplex_1
[BT-DIAG] Mar 13 15:35:15 iq-9075-evk bluetoothd[730]: Endpoint registered: sender=:1.10 path=/MediaEndpoint/A2DPSource/aptx_ll_duplex_0
[BT-DIAG] Mar 13 15:35:15 iq-9075-evk bluetoothd[730]: Endpoint registered: sender=:1.10 path=/MediaEndpoint/A2DPSource/faststream
[BT-DIAG] Mar 13 15:35:15 iq-9075-evk bluetoothd[730]: Endpoint registered: sender=:1.10 path=/MediaEndpoint/A2DPSource/faststream_duplex
[BT-DIAG] Mar 13 15:35:15 iq-9075-evk bluetoothd[730]: Endpoint registered: sender=:1.10 path=/MediaEndpoint/A2DPSink/opus_05
[BT-DIAG] Mar 13 15:35:15 iq-9075-evk bluetoothd[730]: Endpoint registered: sender=:1.10 path=/MediaEndpoint/A2DPSource/opus_05
[BT-DIAG] Mar 13 15:35:15 iq-9075-evk bluetoothd[730]: Endpoint registered: sender=:1.10 path=/MediaEndpoint/A2DPSink/opus_05_duplex
[BT-DIAG] Mar 13 15:35:15 iq-9075-evk bluetoothd[730]: Endpoint registered: sender=:1.10 path=/MediaEndpoint/A2DPSource/opus_05_duplex
[BT-DIAG] Mar 13 15:35:17 iq-9075-evk bluetoothd[730]: Failed to set mode: Authentication Failed (0x05)
[WARN] 2026-03-13 15:38:33 - bluetoothctl list returned no controllers in non-interactive mode.
[WARN] 2026-03-13 15:38:33 - On minimal/ramdisk images this can be normal; interactive bluetoothctl may still work.
[INFO] 2026-03-13 15:38:33 - Proceeding with interactive bluetoothctl for controller queries (non-interactive output incomplete on some images).
[INFO] 2026-03-13 15:38:36 - Initial Powered = no
[INFO] 2026-03-13 15:38:36 - Powering OFF...
[INFO] 2026-03-13 15:38:37 - btpower: hci0 already Powered=no; skipping 'power off'.
[PASS] 2026-03-13 15:38:38 - Post-OFF verification: Powered=no (as expected).
[INFO] 2026-03-13 15:38:38 - Powering ON...
[INFO] 2026-03-13 15:38:39 - btpower: requesting 'on' on hci0 (current=no)
[  219.970272] Bluetooth: hci0: Opcode 0x0c03 failed: -110
[WARN] 2026-03-13 15:39:10 - btpower: hci0 state after request is 'no' (wanted on). (PowerState last='on')

My call would be to disable all failing tests (or fix issues) before merging. The problem with insufficient number of devices is hard to crack. The easiest solution is to limit the number of tests. Second one is to increase the timeout a bit. We need to find a balance between test feedback and test execution time. This problem has no good solution.

@smuppand
Copy link
Copy Markdown

smuppand commented Apr 20, 2026

Here are the current issues:

[INFO] 2026-03-13 15:38:33 - ------------------------------------------------------------
[INFO] 2026-03-13 15:38:33 - Starting BT_ON_OFF Testcase
[INFO] 2026-03-13 15:38:33 - Checking dependency: bluetoothctl
[INFO] 2026-03-13 15:38:33 - Checking if bluetoothd is running...
[INFO] 2026-03-13 15:38:33 - bluetoothd is running
[INFO] 2026-03-13 15:38:33 - Using adapter: hci0
[WARN] 2026-03-13 15:38:33 - bluetoothctl list returned no controllers in non-interactive mode.
[WARN] 2026-03-13 15:38:33 - On minimal/ramdisk images this can be normal; interactive bluetoothctl may still work.
[INFO] 2026-03-13 15:38:33 - Proceeding with interactive bluetoothctl for controller queries (non-interactive output incomplete on some images).
[WARN] 2026-03-13 15:38:33 - Bluetooth diagnostics: controller visibility is inconsistent
[WARN] 2026-03-13 15:38:33 - Adapter: hci0
[WARN] 2026-03-13 15:38:33 - hciconfig output:
[BT-DIAG] hci0:	Type: Primary  Bus: UART
[BT-DIAG] 	BD Address: 44:F7:9F:BB:67:AC  ACL MTU: 1024:7  SCO MTU: 240:4
[BT-DIAG] 	DOWN 
[BT-DIAG] 	RX bytes:2299 acl:0 sco:0 events:94 errors:0
[BT-DIAG] 	TX bytes:166801 acl:0 sco:0 commands:721 errors:0
[WARN] 2026-03-13 15:38:33 - systemctl status bluetooth:
[BT-DIAG] * bluetooth.service - Bluetooth service
[BT-DIAG]      Loaded: loaded (/usr/lib/systemd/system/bluetooth.service; enabled; preset: enabled)
[BT-DIAG]      Active: active (running) since Fri 2026-03-13 15:35:15 UTC; 3min 18s ago
[BT-DIAG]  Invocation: 211d632a4df14e91950327d3c0f880f9
[BT-DIAG]        Docs: man:bluetoothd(8)
[BT-DIAG]    Main PID: 730 (bluetoothd)
[BT-DIAG]      Status: "Running"
[BT-DIAG]       Tasks: 1 (limit: 40613)
[BT-DIAG]      Memory: 2.9M (peak: 3.4M)
[BT-DIAG]         CPU: 34ms
[BT-DIAG]      CGroup: /system.slice/bluetooth.service
[BT-DIAG]              `-730 /usr/libexec/bluetooth/bluetoothd
[BT-DIAG] 
[BT-DIAG] Mar 13 15:35:15 iq-9075-evk bluetoothd[730]: Endpoint registered: sender=:1.10 path=/MediaEndpoint/A2DPSource/aptx_ll_0
[BT-DIAG] Mar 13 15:35:15 iq-9075-evk bluetoothd[730]: Endpoint registered: sender=:1.10 path=/MediaEndpoint/A2DPSource/aptx_ll_duplex_1
[BT-DIAG] Mar 13 15:35:15 iq-9075-evk bluetoothd[730]: Endpoint registered: sender=:1.10 path=/MediaEndpoint/A2DPSource/aptx_ll_duplex_0
[BT-DIAG] Mar 13 15:35:15 iq-9075-evk bluetoothd[730]: Endpoint registered: sender=:1.10 path=/MediaEndpoint/A2DPSource/faststream
[BT-DIAG] Mar 13 15:35:15 iq-9075-evk bluetoothd[730]: Endpoint registered: sender=:1.10 path=/MediaEndpoint/A2DPSource/faststream_duplex
[BT-DIAG] Mar 13 15:35:15 iq-9075-evk bluetoothd[730]: Endpoint registered: sender=:1.10 path=/MediaEndpoint/A2DPSink/opus_05
[BT-DIAG] Mar 13 15:35:15 iq-9075-evk bluetoothd[730]: Endpoint registered: sender=:1.10 path=/MediaEndpoint/A2DPSource/opus_05
[BT-DIAG] Mar 13 15:35:15 iq-9075-evk bluetoothd[730]: Endpoint registered: sender=:1.10 path=/MediaEndpoint/A2DPSink/opus_05_duplex
[BT-DIAG] Mar 13 15:35:15 iq-9075-evk bluetoothd[730]: Endpoint registered: sender=:1.10 path=/MediaEndpoint/A2DPSource/opus_05_duplex
[BT-DIAG] Mar 13 15:35:17 iq-9075-evk bluetoothd[730]: Failed to set mode: Authentication Failed (0x05)
[WARN] 2026-03-13 15:38:33 - journalctl -u bluetooth -b (tail):
[BT-DIAG] Mar 13 15:35:14 iq-9075-evk systemd[1]: Starting Bluetooth service...
[BT-DIAG] Mar 13 15:35:14 iq-9075-evk (bluetoothd)[730]: bluetooth.service: ConfigurationDirectory 'bluetooth' already exists but the mode is different. (File system: 755 ConfigurationDirectoryMode: 555)
[BT-DIAG] Mar 13 15:35:14 iq-9075-evk bluetoothd[730]: Bluetooth daemon 5.86
[BT-DIAG] Mar 13 15:35:15 iq-9075-evk bluetoothd[730]: Starting SDP server
[BT-DIAG] Mar 13 15:35:15 iq-9075-evk bluetoothd[730]: Bluetooth management interface 1.23 initialized
[BT-DIAG] Mar 13 15:35:15 iq-9075-evk bluetoothd[730]: Battery Provider Manager created
[BT-DIAG] Mar 13 15:35:15 iq-9075-evk bluetoothd[730]: Failed to set default system config for hci0
[BT-DIAG] Mar 13 15:35:15 iq-9075-evk systemd[1]: Started Bluetooth service.
[BT-DIAG] Mar 13 15:35:15 iq-9075-evk bluetoothd[730]: /usr/src/debug/bluez5/5.86/src/profile.c:register_profile() :1.10 tried to register 0000111e-0000-1000-8000-00805f9b34fb which is already registered
[BT-DIAG] Mar 13 15:35:15 iq-9075-evk bluetoothd[730]: Endpoint registered: sender=:1.10 path=/MediaEndpoint/A2DPSink/aptx_hd
[BT-DIAG] Mar 13 15:35:15 iq-9075-evk bluetoothd[730]: Endpoint registered: sender=:1.10 path=/MediaEndpoint/A2DPSource/aptx_hd
[BT-DIAG] Mar 13 15:35:15 iq-9075-evk bluetoothd[730]: Endpoint registered: sender=:1.10 path=/MediaEndpoint/A2DPSink/aptx
[BT-DIAG] Mar 13 15:35:15 iq-9075-evk bluetoothd[730]: Endpoint registered: sender=:1.10 path=/MediaEndpoint/A2DPSource/aptx
[BT-DIAG] Mar 13 15:35:15 iq-9075-evk bluetoothd[730]: Endpoint registered: sender=:1.10 path=/MediaEndpoint/A2DPSink/opus_g
[BT-DIAG] Mar 13 15:35:15 iq-9075-evk bluetoothd[730]: Endpoint registered: sender=:1.10 path=/MediaEndpoint/A2DPSource/opus_g
[BT-DIAG] Mar 13 15:35:15 iq-9075-evk bluetoothd[730]: Endpoint registered: sender=:1.10 path=/MediaEndpoint/A2DPSink/sbc
[BT-DIAG] Mar 13 15:35:15 iq-9075-evk bluetoothd[730]: Endpoint registered: sender=:1.10 path=/MediaEndpoint/A2DPSource/sbc
[BT-DIAG] Mar 13 15:35:15 iq-9075-evk bluetoothd[730]: Endpoint registered: sender=:1.10 path=/MediaEndpoint/A2DPSource/aptx_ll_1
[BT-DIAG] Mar 13 15:35:15 iq-9075-evk bluetoothd[730]: Endpoint registered: sender=:1.10 path=/MediaEndpoint/A2DPSource/aptx_ll_0
[BT-DIAG] Mar 13 15:35:15 iq-9075-evk bluetoothd[730]: Endpoint registered: sender=:1.10 path=/MediaEndpoint/A2DPSource/aptx_ll_duplex_1
[BT-DIAG] Mar 13 15:35:15 iq-9075-evk bluetoothd[730]: Endpoint registered: sender=:1.10 path=/MediaEndpoint/A2DPSource/aptx_ll_duplex_0
[BT-DIAG] Mar 13 15:35:15 iq-9075-evk bluetoothd[730]: Endpoint registered: sender=:1.10 path=/MediaEndpoint/A2DPSource/faststream
[BT-DIAG] Mar 13 15:35:15 iq-9075-evk bluetoothd[730]: Endpoint registered: sender=:1.10 path=/MediaEndpoint/A2DPSource/faststream_duplex
[BT-DIAG] Mar 13 15:35:15 iq-9075-evk bluetoothd[730]: Endpoint registered: sender=:1.10 path=/MediaEndpoint/A2DPSink/opus_05
[BT-DIAG] Mar 13 15:35:15 iq-9075-evk bluetoothd[730]: Endpoint registered: sender=:1.10 path=/MediaEndpoint/A2DPSource/opus_05
[BT-DIAG] Mar 13 15:35:15 iq-9075-evk bluetoothd[730]: Endpoint registered: sender=:1.10 path=/MediaEndpoint/A2DPSink/opus_05_duplex
[BT-DIAG] Mar 13 15:35:15 iq-9075-evk bluetoothd[730]: Endpoint registered: sender=:1.10 path=/MediaEndpoint/A2DPSource/opus_05_duplex
[BT-DIAG] Mar 13 15:35:17 iq-9075-evk bluetoothd[730]: Failed to set mode: Authentication Failed (0x05)
[WARN] 2026-03-13 15:38:33 - bluetoothctl list returned no controllers in non-interactive mode.
[WARN] 2026-03-13 15:38:33 - On minimal/ramdisk images this can be normal; interactive bluetoothctl may still work.
[INFO] 2026-03-13 15:38:33 - Proceeding with interactive bluetoothctl for controller queries (non-interactive output incomplete on some images).
[INFO] 2026-03-13 15:38:36 - Initial Powered = no
[INFO] 2026-03-13 15:38:36 - Powering OFF...
[INFO] 2026-03-13 15:38:37 - btpower: hci0 already Powered=no; skipping 'power off'.
[PASS] 2026-03-13 15:38:38 - Post-OFF verification: Powered=no (as expected).
[INFO] 2026-03-13 15:38:38 - Powering ON...
[INFO] 2026-03-13 15:38:39 - btpower: requesting 'on' on hci0 (current=no)
[  219.970272] Bluetooth: hci0: Opcode 0x0c03 failed: -110
[WARN] 2026-03-13 15:39:10 - btpower: hci0 state after request is 'no' (wanted on). (PowerState last='on')

This PR qualcomm-linux/qcom-linux-testkit#412 resolves the BT issue on RB1. @bhargav0610, please remember to report similar issues for all SoCs whenever there are such failures.

https://github.com/qualcomm-linux/meta-qcom/actions/runs/24511752498/job/71850334280#step:3:4619 This is not an issue with the test script. The failure occurred because core 3 did not increment the events, and the final results were updated to FAIL.

My call would be to disable all failing tests (or fix issues) before merging. The problem with insufficient number of devices is hard to crack. The easiest solution is to limit the number of tests. Second one is to increase the timeout a bit. We need to find a balance between test feedback and test execution time. This problem has no good solution.

@qcom-anilyada
Copy link
Copy Markdown
Contributor Author

Here's the updated summary of the failed workflows along with their fixes, infra and script side issues have already been resolved.

Workflow Summary: 13 Failed Jobs

1. Device Crash (Build Issue)


2. Passed but Timed Out

  • Count: 5 jobs
  • Reason: Workflow timeout starts when the job is created, not when execution begins
  • Fix: As Milosz suggested either we have to increase device count in the pool, or increase the timeout

3. Infrastructure / Script Issues (Resolved)

  • Count: 3 jobs

a) Bluetooth Dongle Issue — rb3g2-hyd-01

b) Bluetooth Issue — rb1-04 and rb1-05 (Cambridge workers)


4. Genuine Test Failures

  • Count: 3 jobs

a) weston-simple-eglrb3gen2-core-kit

b) BT_ON_OFFiq-9075-evk

c) Irqqcs8300-ride-sx

  • Failure: CPU 3: Timer count has not incremented. Test FAILED

5. Workflow Configuration Issue

@bhargav0610
Copy link
Copy Markdown

Here's the updated summary of the failed workflows along with their fixes, infra and script side issues have already been resolved.

Workflow Summary: 13 Failed Jobs

1. Device Crash (Build Issue)

2. Passed but Timed Out

  • Count: 5 jobs
  • Reason: Workflow timeout starts when the job is created, not when execution begins
  • Fix: As Milosz suggested either we have to increase device count in the pool, or increase the timeout

3. Infrastructure / Script Issues (Resolved)

  • Count: 3 jobs

a) Bluetooth Dongle Issue — rb3g2-hyd-01

b) Bluetooth Issue — rb1-04 and rb1-05 (Cambridge workers)

4. Genuine Test Failures

  • Count: 3 jobs

a) weston-simple-eglrb3gen2-core-kit

b) BT_ON_OFFiq-9075-evk

c) Irqqcs8300-ride-sx

  • Failure: CPU 3: Timer count has not incremented. Test FAILED

5. Workflow Configuration Issue

@mwasilew can you pls review the PR now as most of the things has been addressed now

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.

6 participants