Closed eugene-yujinwu closed 2 months ago
Thank you for reporting us your feedback!
The internal ticket has been created: https://warthogs.atlassian.net/browse/CHECKBOX-1545.
This message was autogenerated
Can you please try the following:
checkbox.shell
sudo journalctl -f
checkbox-support-run_watcher insertion usb3
INSERT NOW
and insert the USB drivesudo journalctl -f
Also, can you try the same command with a USB-A drive and/or another USB-C USB stick?
Thanks,
@pieqq hi, I think I had find the root cause of this issue. This USB-c disks is a usb3.2 device with uas driver, it doesn't covered by the run_watcher.py. I will try to fix it and submit a PR for it. Thanks!
Bug Description
We had a Kingshare Portable SSD type-c usb disk which used to test the usb-c disk tests. It works well before, but recently, the Checkbox will fail the com.canonical.certification::usb-c/insert test.
[Checkbox job
com.canonical.certification::after-suspend-usb-c/insert
output]stdout
INSERT NOW
Timeout: 30 seconds
stderr
/bin/sh: 1: kill: Illegal number: - Traceback (most recent call last): File "/usr/bin/checkbox-support-run_watcher", line 8, in
sys.exit(main())
^^^^^^
File "/usr/lib/python3/dist-packages/checkbox_support/helpers/timeout.py", line 93, in _f
return run_with_timeout(f, timeout_s, *args, **kwargs)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/lib/python3/dist-packages/checkbox_support/helpers/timeout.py", line 78, in run_with_timeout
raise TimeoutError("Task unable to finish in {}s".format(timeout_s))
TimeoutError: Task unable to finish in 30s
To Reproduce
1.run commad: checkbox-cli run com.canonical.certification::usb-c/insert
Environment
Image: canonical-oem-sutton-noble-oem-24.04b-proposed-20240723-3 system-manufacturer: LENOVO system-product-name: 21M1SIT002 bios-version: R2NET18F (0.18 ) CPU: AMD Ryzen AI 7 PRO 160 w/ Radeon 870M (16x) GPU: c2:00.0 Display controller [0380]: Advanced Micro Devices, Inc. [AMD/ATI] Device [1002:150e] (rev d2) amd-vbios: 113-STRIXEMU-001["150E"] kernel-version: 6.10.0-1005-oem
Relevant log output
Additional context
No response