selftests print "no such file or directory" on error
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| | Snappy |
Low
|
Unassigned | ||
Bug Description
When the selftests written in go fail, they print the error message alright. But they also print the useless message "no such file or directory". For example:
/home/elopio/
...open /home/elopio/
... value string = "" +
... "Installing hello-world\n" +
... "Name Date Version Developer \n" +
... "ubuntu-core 2015-06-26 -1 ubuntu \n" +
... "hello-world 2015-06-26 1.0.18 canonical \n" +
... "port-listener 2015-06-11 0.1 sideload \n" +
... "webdm 2015-06-11 0.9 \n" +
... "webdm 2015-04-23 0.5 sideload \n" +
... "generic-amd64 2015-06-11 1.1.1 \n" +
... "Reboot to use the new ubuntu-core.\n"
... regex string = "" +
... "Installing hello-world\n" +
... "Name Date Version Developer \n" +
... ".*\n" +
... "hello-world .* .* canonical \n" +
... ".*\n"
START: /home/elopio/
PASS: /home/elopio/
FAIL: /home/elopio/
--- FAIL: Test (192.09 seconds)
| Leo Arias (elopio) wrote : | #2 |
Yes it is. Setting to low because the error message is displayed properly, so this is just polluting the output a little.
And I have no idea how to fix it. The compiled go tests don't seem to be made to run in a machine that doesn't have the source.
| Changed in snappy: | |
| status: | Incomplete → Triaged |
| importance: | Undecided → Low |
| Michael Vogt (mvo) wrote : | #3 |
This is fixed by moving to spread.
| Changed in snappy: | |
| status: | Triaged → Fix Released |
Is this still a issue? If so, please set status and importance of the bug accordingly.