I'm working on a CIAT test to automate the removal and (re)installation of app fwk packages, but I noticed that it's impossible to tell from afm-util whether the package removal is successful or not:
afm-util remove <id> returns the same return value (zero) and the same stdout (null) whether the app is actually present or not.
I would like to see the app-lifecycle test added to flounder for future patch releases, but it is probably not necessary. Even if we do not apply the tests themselves, I think we want to apply the fixes applied for issues found in app-lifecycle testing to flounder.
Jan-Simon Moeller
November 2, 2018 at 1:14 PM
Only if we want to extend the (WIP)basic app-lifecycle test to flounder as well.
Walt Miner
October 31, 2018 at 11:48 PM
Does the bump version need to be applied to Flounder?
jose bollo
October 31, 2018 at 9:34 AM
I've just checked anout the latest comment. The issue is in the error report that says "Success". I will open a new jira issue to track that specific problem
I'm working on a CIAT test to automate the removal and (re)installation of app fwk packages, but I noticed that it's impossible to tell from afm-util whether the package removal is successful or not:
afm-util remove <id> returns the same return value (zero) and the same stdout (null) whether the app is actually present or not.
raspberrypi3:~# afm-util list |grep \"id\" "id":"radio@0.1", "id":"hvac@0.1", "id":"homescreen@0.1", "id":"poi@0.1", "id":"phone@0.1", "id":"mixer@6.90", "id":"navigation@0.1", "id":"settings@0.1", "id":"launcher@0.1", "id":"mediaplayer@0.1", "id":"dashboard@0.1", raspberrypi3:~# afm-util remove dashboard@0.1 null raspberrypi3:~# echo $? 0 raspberrypi3:~# afm-util list |grep \"id\" "id":"radio@0.1", "id":"hvac@0.1", "id":"homescreen@0.1", "id":"poi@0.1", "id":"phone@0.1", "id":"mixer@6.90", "id":"navigation@0.1", "id":"settings@0.1", "id":"launcher@0.1", "id":"mediaplayer@0.1",
Here we can see that "dashboard" was removed.
However, if I try to remove it again, I get exactly the same return values:
raspberrypi3:~# afm-util remove dashboard@0.1 null raspberrypi3:~# echo $? 0 raspberrypi3:~#
Similarily, if I try to remove a dummy package which I know does not exist, it appears to be successfull also:
raspberrypi3:~# afm-util remove nonexistant-dummy@0.1 null raspberrypi3:~# echo $? 0 raspberrypi3:~#