You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Test fail because dpkg --list does not show no packages found matching but the package is not installed
How reproducible
It was consistent on this device with this package
How to reproduce
I am not sure how to reproduce the exact situation. In the logs we can see that dpkg knew the name of the package, but nothing more. I think installing and then purging the package produces the same output, but why it was like that before installing the package is unknown to me. Doing either apt remove or apt purge will make the keyword produce false positives.
Expected behavior
The keyword should reliably check if the program is installed and can be run. False positives cost a lot of time.
Actual behavior
The keyword produces false positives if the package was removed
root@3mdeb:/home/ubuntu# sensors
Command 'sensors' not found, but can be installed with:
apt install lm-sensors
root@3mdeb:/home/ubuntu# sudo^C
root@3mdeb:/home/ubuntu# dpkg --list lm-sensors
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name Version Architecture Description
+++-==============-============-============-=================================
un lm-sensors <none> <none> (no description available)
root@3mdeb:/home/ubuntu# lm-sensors
lm-sensors: command not found
root@3mdeb:/home/ubuntu# sensors
Command 'sensors' not found, but can be installed with:
apt install lm-sensors
root@3mdeb:/home/ubuntu# dpkg --list lm-sensorsfdsf
dpkg-query: no packages found matching lm-sensorsfdsf
Additional context
Maybe using dpkg --get-selections would be more reliable? This way this keyword could be changed to fail by default, not pass. At this moment if dpkg --list prints anything other than nothing or no packages found matching the KW passes. Using --get-selections the keyword could only pass when the package is actually installed and fail on unforeseen situations which won't break the tests.
Device
Optiplex 7010
RTE version
OSFV version
develop
Affected component(s) or functionality
Appeared in CPT tests
Brief summary
Test fail because
dpkg --list
does not showno packages found matching
but the package is not installedHow reproducible
It was consistent on this device with this package
How to reproduce
I am not sure how to reproduce the exact situation. In the logs we can see that dpkg knew the name of the package, but nothing more. I think installing and then purging the package produces the same output, but why it was like that before installing the package is unknown to me. Doing either
apt remove
orapt purge
will make the keyword produce false positives.Expected behavior
The keyword should reliably check if the program is installed and can be run. False positives cost a lot of time.
Actual behavior
The keyword produces false positives if the package was removed
Link to screenshots or logs
dasharo-performance_log.zip
Additional context
Maybe using
dpkg --get-selections
would be more reliable? This way this keyword could be changed to fail by default, not pass. At this moment ifdpkg --list
prints anything other than nothing orno packages found matching
the KW passes. Using--get-selections
the keyword could only pass when the package is actually installed and fail on unforeseen situations which won't break the tests.Solutions you've tried
No response
The text was updated successfully, but these errors were encountered: