File "neutron/api/v2/base.py", line 329, in _emulate_bulk_create
no less than 36 times. That's problematic. Now note;
testuser@archtester ~/cvsPortage/gentoo-x86/sys-cluster/neutron $ ls -ld /path/to/neutron-2013.2/.testrepository/0
yields
-rw------- 1 testuser testuser 78318772 Nov 20 23:18 /mnt/gen2/TmpDir/portage/sys-cluster/neutron-2013.2-r1/work/neutron-2013.2/.testrepository/0
Is this 78 mb of log that backtraces to neutron system packages, never reaches the actual instigating tests and lists 2 FAILS despite listing _emulate_bulk_create on 36 separate occasions. In the filed of analysing testsuites, this one really breaks new ground.
The good news is 2 out of 18665 tests in 1689.939s is not so bad
The bad news is for all the 78 mb of logging we have no idea WHAT THE TESTS ARE, in addition to this test still having an invalid invalid status
so from
python_test() { /bugs.launchpad .net/nova/ +bug/1235955 NO_PARALLEL_ BUILD=1 router_ schedule_ with_candidates :_&:' -i neutron/ tests/unit/ openvswitch/ test_agent_ scheduler. py
# https:/
local DISTUTILS_
mv $(find . -name test_ovs_tunnel.py) ./troubled || die
sed -e 's:test_
testr init
testr run --parallel || die "failed testsuite under python2.7"
}
we have
======= ======= ======= ======= ======= ======= ======= ======= ======= ======= ------- ------- ------- ------- ------- ------- ------- ------- ------- ======= ======= ======= ======= ======= ======= ======= ======= ======= ------- ------- ------- ------- ------- ------- ------- ------- ------- neutron- 2013.2- r1::gentoo failed (test phase):
FAIL: process-returncode
tags: worker-0
-------
Binary content:
traceback (test/plain; charset="utf8")
=======
FAIL: process-returncode
tags: worker-1
-------
Binary content:
traceback (test/plain; charset="utf8")
Ran 18665 tests in 1689.939s
FAILED (id=0, failures=2, skips=328)
* ERROR: sys-cluster/
* failed testsuite under python2.7
as always with NO traceback, setting a rather nouvelle mystery.
from http:// paste.openstack .org/show/ 53681/ from .testrepository/0
we have
pythonlogging:''
ok python logging gets turned on
2013-11-20 22:49:57,995 INFO [neutron.manager] Loading Plugin: neutron. plugins. bigswitch. plugin. NeutronRestProx yV2
the traceback begins at neutron. plugins. bigswitch. plugin,
who knows what the instigating test was. Here's a hint;
successful: neutron. tests.unit. bigswitch. test_restproxy_ plugin. TestBigSwitchPr oxyNetworksV2.
just occurred before, so it appears it's likely from neutron. tests.unit. bigswitch. test_restproxy_ plugin. py
2013-11-20 22:49:58,108 ERROR [neutron. api.extensions] Extension path 'unit/extensions' doesn't exist!
Oh dear, that's problematic.
$ find ...../neutron- 2013.2/ -name extensions neutron- 2013.2/ neutron/ tests/unit/ extensions
.....
perhaps?
should it not be seeking Extension path 'neutron/ tests/unit/ extensions' ??????????
testuser@archtester ~/cvsPortage/ gentoo- x86/sys- cluster/ neutron $ grep _emulate_ bulk_create /mnt/gen2/ TmpDir/ portage/ sys-cluster/ neutron- 2013.2- r1/work/ neutron- 2013.2/ .testrepository /0
yields
File "neutron/ api/v2/ base.py" , line 329, in _emulate_ bulk_create
no less than 36 times. That's problematic. Now note;
testuser@archtester ~/cvsPortage/ gentoo- x86/sys- cluster/ neutron $ ls -ld /path/to/ neutron- 2013.2/ .testrepository /0 TmpDir/ portage/ sys-cluster/ neutron- 2013.2- r1/work/ neutron- 2013.2/ .testrepository /0 bulk_create on 36 separate occasions. In the filed of analysing testsuites, this one really breaks new ground.
yields
-rw------- 1 testuser testuser 78318772 Nov 20 23:18 /mnt/gen2/
Is this 78 mb of log that backtraces to neutron system packages, never reaches the actual instigating tests and lists 2 FAILS despite listing _emulate_
The good news is 2 out of 18665 tests in 1689.939s is not so bad
The bad news is for all the 78 mb of logging we have no idea WHAT THE TESTS ARE, in addition to this test still having an invalid invalid status