Unit Test Failure After Building Component
vladimir-v-diaz opened this issue · comments
Vladimir Diaz commented
The unit tests fail on a newly-built softwareupdater
component (using the buildscripts):
$ python initialize.py
Checking out repo from https://github.com/SeattleTestbed/seattlelib_v2 ...
Done!
Checking out repo from https://github.com/SeattleTestbed/portability ...
Done!
Checking out repo from https://github.com/SeattleTestbed/repy_v2 ...
Done!
Checking out repo from https://github.com/SeattleTestbed/common ...
Done!
Checking out repo from https://github.com/SeattleTestbed/nodemanager ...
Done!
$ git build.py -t
git: 'build.py' is not a git command. See 'git --help'.
$ python build.py -t
Building into /home/vlad/projects/seattletestbed/softwareupdater/RUNNABLE
Done building!
$ cd ../RUNNABLE/
$ python utf.py -a
Testing module: softwareupdaters
Running: ut_softwareupdaters_testupdaterlocal.py [ FAIL ]
--------------------------------------------------------------------------------
Standard error :
..............................Produced..............................
Traceback (most recent call last):
File "ut_softwareupdaters_testupdaterlocal.py", line 295, in main
Exception: [do_rsync] Unable to update ntp time. Not updating.
Test type: -u URL: http://128.238.64.165:12345/ [ FAIL ]
nmmain.py was supposed to be updated, but was not included in the updatedlist
metainfo was supposed to be updated, but was not included in the updatedlist
nmmain.py should have been updated, but wasn't
metainfo should have been updated, but wasn't
..............................Expected..............................
None
--------------------------------------------------------------------------------
aaaaalbert commented
Please try with the patch I suggested on #50. I had this in my working copy for ages, but forgot to push it :-(
Vladimir Diaz commented
Do you know if there are uncommitted fixes for other repositories? I have tried to run the unit tests for others and they unexpectedly fail (e.g., a missing import). I'm not sure if this is due to a repy_v1 -> repy_v2 transition phase and modules are still in the process of being migrated.