Closed stanley31huang closed 3 months ago
Thank you for reporting us your feedback!
The internal ticket has been created: https://warthogs.atlassian.net/browse/CHECKBOX-1449.
This message was autogenerated
I found that when we catch other exceptions here, and the eddystone_scanner scripts will exits shortly with error. https://github.com/canonical/checkbox/blob/main/checkbox-support/checkbox_support/vendor/beacontools/scanner.py#L176
Thank you for your report. I now understand why this happens and why your fix works. The reason is that the exception is a custom un-picklable exception, so the decorator is unable to propagate it up, crashing silently (as it is doing so in a separate thread) when trying to push it. Subsequently the other process detects that the child is dead but not finding anything in the exception queue (as the child died while trying to push to it) it hangs waiting for a result. Will push a PR soon to fix this
Bug Description
While running a beacon eddystone test, the checkbox session would hanging there over 15 minutes, I just kill the process and did not check is that process will stuck forever.
It seems the bluetooth adapter is in an abnormal stage on the system, so it leads the eddystone_scanner crashed, but the scripts suppose to terminated automatically within 10 minutes.
the hciconfig logs
Error logs in a checkbox session.
Error logs while running eddystone_scanner directly
To Reproduce
I have reproduce this issue with following steps:
Launch checkbox and run eddystone directly.
iotuc@ubuntu:~$ checkbox-shiner.checkbox-cli run com.canonical.certification::device com.canonical.certification::bluetooth4/beacon_eddystone_url_hci0
Launch eddystone_scanner.py scripts directly
root@ubuntu:/home/iotuc# python3 /snap/checkbox20/current/lib/python3.8/site-packages/checkbox _support/scripts/eddystone_scanner.py -D hci0
Notes: also seen this issue with a checkbox remote session.
Environment
Also tested with checkbox20 4.0.0-dev270
Relevant log output
No response
Additional context
No response