[VDSM] travis tests update - 1 failure on Fedora with python 3

Hi all, All the tests pass on centos: https://travis-ci.org/oVirt/vdsm/jobs/175484347 Some moduleloader tests fail on fedora python 3: https://travis-ci.org/oVirt/vdsm/jobs/175484348 I have see this and other module loader tests fail on travis randomly in the past. https://travis-ci.org/nirs/vdsm/jobs/175483969 Looking at the test code, looks like it needs a rewrite. The test is much more complicated then the code it tests. Nir

On Sun, Nov 13, 2016 at 4:39 PM, Nir Soffer <nsoffer@redhat.com> wrote:
Hi all,
All the tests pass on centos: https://travis-ci.org/oVirt/vdsm/jobs/175484347
Some moduleloader tests fail on fedora python 3: https://travis-ci.org/oVirt/vdsm/jobs/175484348
I have see this and other module loader tests fail on travis randomly in the past. https://travis-ci.org/nirs/vdsm/jobs/175483969
Looking at the test code, looks like it needs a rewrite. The test is much more complicated then the code it tests.
Another random test failure is: ====================================================================== ERROR: testMutiWrite (miscTests.AsyncProcTests) ---------------------------------------------------------------------- Traceback (most recent call last): File "/usr/lib/python2.7/site-packages/nose/case.py", line 133, in run self.runTest(result) File "/usr/lib/python2.7/site-packages/nose/case.py", line 151, in runTest test(result) File "/usr/lib64/python2.7/unittest/case.py", line 431, in __call__ return self.run(*args, **kwds) File "/usr/lib64/python2.7/unittest/case.py", line 406, in run result.addSuccess(self) File "/usr/lib/python2.7/site-packages/nose/proxy.py", line 165, in addSuccess self.result.addSuccess(self.test) File "/vdsm/tests/testlib.py", line 356, in addSuccess self._writeResult(test, 'OK', TermColor.green, '.', True) File "/vdsm/tests/testlib.py", line 349, in _writeResult self.stream.writeln() File "/usr/lib64/python2.7/unittest/runner.py", line 25, in writeln self.write('\n') # text-mode streams translate to \r\n if needed IOError: [Errno 4] Interrupted system call -------------------- >> begin captured logging << -------------------- 2016-11-13 14:45:41,350 DEBUG (MainThread) [root] /usr/bin/taskset --cpu-list 0-1 cat (cwd None) (commands:69) 2016-11-13 14:45:41,355 INFO (MainThread) [AsyncProcTests] Writing data to std out (miscTests:257) 2016-11-13 14:45:41,356 INFO (MainThread) [AsyncProcTests] Writing more data to std out (miscTests:259) 2016-11-13 14:45:41,356 INFO (MainThread) [AsyncProcTests] Written data reading (miscTests:262) --------------------- >> end captured logging << --------------------- This happen in various tests. never seen in jenkins, fails randomly locally and in travis. Related to tests not waiting for child processes, typically because we use zombiereaper instead of waiting for the child process. Nir

On Sun, Nov 13, 2016 at 4:39 PM, Nir Soffer <nsoffer@redhat.com> wrote:
Hi all,
All the tests pass on centos: https://travis-ci.org/oVirt/vdsm/jobs/175484347
Some moduleloader tests fail on fedora python 3: https://travis-ci.org/oVirt/vdsm/jobs/175484348
I have see this and other module loader tests fail on travis randomly in the past. https://travis-ci.org/nirs/vdsm/jobs/175483969
Looking at the test code, looks like it needs a rewrite. The test is much more complicated then the code it tests.
Since the failures are random, here is a successful build: https://travis-ci.org/oVirt/vdsm/builds/175494870 And the readme build status turned green: https://github.com/oVirt/vdsm#vdsm-virtual-desktop-server-manager Nir
participants (1)
-
Nir Soffer