| 2014-09-08 12:18:34 |
Michael Vogt |
description |
I was trying to verify the click testplan and ran into the issue that the deployment does not work for me.
This is confusing becaue I was able to run the click package on my device and from reading qtc_device_applaunch.py
it seems like something put the click on the device and then the qtc_device_applaunch.py script installs it, runs it
and removes it. So installing is possible and yet it fails in step #15 of the SDK testplan when its running
/usr/share/qtcreator/ubuntu/scripts/qtc_project_click_deploy
I looked at the script and noticed some issue:
- does not use "set -e" when ssh can't connect this gets ignored
- redirects errors from ssh/scp which means that if something goes wrong here its unclear to the user what is going on
- does not output when it was successful
I will work on a branch for that.
Thanks,
Michael |
I was trying to verify the click testplan and ran into the issue that the deployment does not work for me.
This is confusing becaue I was able to run the click package on my device and from reading qtc_device_applaunch.py
it seems like something put the click on the device and then the qtc_device_applaunch.py script installs it, runs it
and removes it. So installing is possible and yet it fails in step #15 of the SDK testplan when its running
/usr/share/qtcreator/ubuntu/scripts/qtc_project_click_deploy
I looked at the script and noticed some issue:
- does not use "set -e" when ssh can't connect this gets ignored
- redirects errors from ssh/scp which means that if something goes wrong here its unclear to the user what is going on
- does not output when it was successful
I will work on a branch for that. For unknown reasons deploying my click package works now even without this branch. Before I got a error that the ssh connection to port 10000 was refused (and I only saw the error because I hacked the deploy script locally).
Thanks,
Michael |
|
