[ovirt-devel] [VDSM] Tests failing because of ordering dependencies

[Dan Kenigsberg]

On Wed, Oct 12, 2016 at 09:16:08PM +0300, Nir Soffer wrote:
> If you want to reproduce the errors, try this patch:
> https://gerrit.ovirt.org/65404
> 
> On Wed, Oct 12, 2016 at 9:14 PM, Nir Soffer <nsoffer at redhat.com> wrote:
> > Hi all,
> >
> > Trying to run vdsm tests via tox (so correct nose is used automatically),
> > some of the tests fail.
> >
> > The failure are all about ordering expectations, which look wrong.
> >
> > Please check and fix your tests.
> >
> > Thanks,
> > Nir
> >
> > ----
> >
> > 18:04:10 ======================================================================
> > 18:04:10 FAIL: test_parseVolumeStatus (gluster_cli_tests.GlusterCliTests)
> > 18:04:10 ----------------------------------------------------------------------
> > 18:04:10 Traceback (most recent call last):
> > 18:04:10   File
> > "/home/jenkins/workspace/vdsm_master_check-patch-el7-x86_64/vdsm/tests/gluster_cli_tests.py",
> > line 1121, in test_parseVolumeStatus
> > 18:04:10     self._parseVolumeStatusClients_test()
> > 18:04:10   File
> > "/home/jenkins/workspace/vdsm_master_check-patch-el7-x86_64/vdsm/tests/gluster_cli_tests.py",
> > line 449, in _parseVolumeStatusClients_test
> > 18:04:10     self.assertEquals(status.keys(), ['bricks', 'name'])
> >
> > status.keys() order is not undefined.

I've never seen this in Python 2, but since Python 3 uses a different
hash function, this specific issue is handled in
https://gerrit.ovirt.org/#/c/65008/