Saturday, 2013-11-16

flashgordonsalv-orlando: we didn't00:00
flashgordonat least we tried not to00:00
flashgordonwe explicitly set serial for neutron00:01
salv-orlandoIt actually it seems it still running smoke-serial env00:01
flashgordonhttps://review.openstack.org/#/c/56466/00:01
flashgordonhttps://review.openstack.org/#/c/56467/00:01
salv-orlandoI missed the devstack-gate change00:03
salv-orlandomy bad00:03
*** julim has joined #openstack-neutron00:15
*** layer427expert has quit IRC00:17
*** layer427expert has joined #openstack-neutron00:19
*** layer427expert has quit IRC00:20
*** julim has quit IRC00:24
*** devlaps has quit IRC00:30
*** flashgordon is now known as jog000:37
*** alexpilotti has quit IRC00:40
*** gdubreui has joined #openstack-neutron00:44
*** manishg has joined #openstack-neutron00:49
*** jsergent has quit IRC00:53
*** suresh12 has quit IRC00:59
*** suresh12 has joined #openstack-neutron01:00
*** suresh12 has quit IRC01:00
*** suresh12 has joined #openstack-neutron01:01
*** catintheroof has quit IRC01:09
*** manishg has quit IRC01:09
*** gdubreui has quit IRC01:24
*** dkliban has joined #openstack-neutron01:31
*** dkliban has quit IRC01:41
*** catintheroof has joined #openstack-neutron02:21
*** LiJiansheng has joined #openstack-neutron02:37
*** suresh12 has quit IRC02:50
*** suresh12 has joined #openstack-neutron02:51
*** catintheroof has quit IRC02:52
*** suresh12_ has joined #openstack-neutron02:55
*** suresh12 has quit IRC02:56
*** catintheroof has joined #openstack-neutron02:59
*** suresh12_ has quit IRC03:00
*** suresh12 has joined #openstack-neutron03:01
*** gatuus has quit IRC03:02
*** nati_ueno has joined #openstack-neutron03:04
*** suresh12 has quit IRC03:06
*** nati_ueno has quit IRC03:13
*** nati_ueno has joined #openstack-neutron03:15
*** nati_ueno has quit IRC03:17
*** catintheroof has quit IRC03:29
*** nati_ueno has joined #openstack-neutron03:37
*** nati_ueno has quit IRC03:44
openstackgerritstephen-ma proposed a change to openstack/neutron: DHCP port without DHCP server on a network node  https://review.openstack.org/5674003:59
*** networkstatic has joined #openstack-neutron04:01
openstackgerritA change was merged to openstack/neutron: Lower severity of log trace for DB integrity error  https://review.openstack.org/5649604:07
*** suresh12 has joined #openstack-neutron04:11
*** LiJiansheng has quit IRC04:12
*** suresh12 has quit IRC04:16
openstackgerritstephen-ma proposed a change to openstack/neutron: DHCP port without DHCP server on a network node  https://review.openstack.org/5674004:41
*** scotty916 has joined #openstack-neutron04:44
*** scotty916 has quit IRC04:50
*** HenryG_ has joined #openstack-neutron05:06
*** HenryG has quit IRC05:09
openstackgerritJenkins proposed a change to openstack/neutron: Imported Translations from Transifex  https://review.openstack.org/5674506:41
*** alexpilotti has joined #openstack-neutron07:49
*** amritanshu_RnD has joined #openstack-neutron08:12
*** prometheanfire has joined #openstack-neutron08:32
prometheanfireenikanorov_: ping bug 125165708:35
*** idella4 has joined #openstack-neutron08:38
idella4enikanorov: why am I sooo puzzled?08:40
idella4setting up venv not directly related to neutron project somehow skirts the devs of neutron maintaining the testsuite08:41
idella4as in writing it and getting it to work?08:41
prometheanfireI added a comment to the bug, dunno if he's in irc atm :D08:42
idella4ah right08:42
idella4well asking what we're missing seems apt08:43
idella4on the presumption it's us doing the missing so let's plug that hole08:43
prometheanfireif he says it's our fault he must have proof right?08:44
idella4right08:44
prometheanfirebut ya, all about plugging holes08:45
idella4so we ask please serve it up08:45
prometheanfireand that's what she said08:45
idella4we await input from enikanorov08:45
sgranhi,09:04
sgrandoes it make sense that you can add two members to a loadbalancer with the same ip/port tuple?09:05
sgranI can't see the usefulness of that, so I'm thinking of reporting it as a bug, but maybe someone sees a valid reason for it09:05
enikanorovsgran: yeah you can file it. probably it make sense to add a constraint to the schema09:53
idella4well that acounts for sgran09:54
enikanorovidella4: your bug description looks like a huge monologue. At first glance it looks like venv setup has failed and that caused a number of issues later on09:56
enikanorovvenv creation may fail for various reasons and it's not what neutron project should care about09:57
enikanorovunless it's something introduced in neutron's code09:57
idella4did you pick up the part where venv creation is what 'we' would like to take out of the equation?09:57
idella4I gave points where use of a virtual env. confounds a gentoo setup09:58
enikanorovso, first of all, to proceed to UT failures you need to make sure venv was set up properly, e.g. without errors09:59
idella4venus and mars09:59
enikanorovusing virtual env is a normal practice, what's wrong with venv and gentoo setup?10:00
idella4I asked if you can make the testsuite run from nosetests10:01
idella4tI pointed out already, the first thing tox does is download the lot10:01
idella4gentoo practice in test phases is to run everything statically10:01
enikanorovyeah, tox creates it's own venv10:02
idella4no connection to the internet10:02
idella4it totally confounds the approach10:02
enikanorovwell... you want openstack to comply with gentoo's approach?10:03
idella4The idea is for the installed system dependency packages to run the suite10:03
enikanorovi think it's possible if you have exact versions of python libraries required for each project10:03
idella4it's close10:03
idella4seeing it runs by use of nosetests anyway10:04
idella4I realise the use of tox and virtual env is common10:04
idella4and therefore I constantly have to dodge it in testsuites when it comes up10:05
idella4I ask can it be written to run 'stically' from nosetests  without tox10:06
enikanoroveach project has it's own requirements.txt10:06
enikanorovwhich may or may not reuire the same versions of libraries10:06
idella4yep10:07
idella4well right10:07
enikanorovalso, tox is for unit testing and development, when you may change requirements.txt yourself and that should change venv10:07
idella4we list and install all those deps in  requirements.txt10:07
idella4ok so tox reads requirements.txt10:08
idella4hmm so the 1 diff that is in place in neutronm10:08
idella4is the sububnit10:09
idella4vs. python-subunit10:09
idella4so are you making the point that tox can run the tests from the system installed packages10:10
idella4on the condition that they match them listed in reuiqrements .txt?10:10
enikanorovi'm not sure about that10:11
idella4hmm10:11
enikanorovthe purpose of tox is to run things in different environments10:12
enikanorov(venvs)10:12
idella4well fine but we basically want to run the testsuite using the system installed deps10:13
idella4the openstack fundamentally use nose as the test runner'10:14
idella4via tox10:14
enikanorovi guess tox uses testr10:14
enikanorovwhich is different from nose10:15
idella4the use of differing envs de-rails things10:15
idella4ok so can you outline testr for me10:15
enikanorovwhy it derails things?10:15
idella4I recall the test run uses something like python setup.py testr10:16
idella4well it goes creating an environment when there's already one there up and running10:17
idella4'most python packages run testsuites by use of nosetests or pytest or python /path/to/some_test_all.py file10:18
idella4use of tox is infrequent and spasmodic in gentoo's python packages10:19
idella4what exactly is testr enikanorov?10:19
enikanorovhttps://wiki.openstack.org/wiki/Testr10:20
idella4ok gentoo has dev-python/testrepository in portage10:21
enikanorovwhy gentoo at all?10:22
idella4testr is a test runner so it's an alternative to a nose10:23
idella4why what about gentoo?10:23
idella4one dev in particular has recently taken on the openstack project and is in the process of adding and includionmg them into gentoo's portage10:24
enikanorovwhy are you trying to run openstack on gentoo when approaches are so different?10:24
*** jorisroovers has joined #openstack-neutron10:25
idella4ah now that's a question for him, prometheanfire10:25
idella4well which approaches do you mean? the building of the packages?10:26
enikanorovok, so any kind of os-specific issues belong to packaging10:26
enikanorovnot to the project10:26
enikanorovif you're working with source code tree and you want to run project from sources or run unit tests, than it will be tox10:27
idella4oh running a testsuite isn't a matter of packaging10:27
enikanorovand it will be downloading it's own venv regardless of what's installed in the system10:27
enikanorovand regardless of gentoo's best practices10:27
enikanorovif you want to verify the package - that's another matter and that will be a matter of packaging10:28
idella4it's a matter of running the packages as they come10:28
enikanorovok, so does gentoo have neutron package?10:28
idella4yes he has added it to portage10:28
idella4it's what I ran that made for the bug10:29
enikanorovok, so if it doesn't work, you should file a bug on the neutron gentoo package, no?10:29
idella4prometheanfire:  & I are the gentoo devs that would fix them10:30
enikanorovi don't see what neutron project itself has to do with package for gentoo10:31
idella4you don't no10:31
idella4well to run the testsuite in line with gentoo's policies and practices10:32
idella4it has to be more or less completely re-worked10:32
enikanorov'it has' what has to be completely reworked?10:33
idella4well 'it' uses tox which as you said10:34
idella4it will be downloading it's own venv regardless of what's installed in the system10:34
idella4REGARDLESS10:35
idella4the modus operandi of the testsuite is basically unusable in its std form10:35
idella4gentoo10:35
idella4the rest of the package is fine10:36
idella4and prometheanfire soo wanted to have the openstack packages equipped with test phases10:36
idella4therefore it requires re-working completely10:37
enikanorovright, but still neutron project has nothing to do with this reworking10:37
enikanorovi think it's possible to include venv preparation as a step in package isntallation10:37
idella4I have some test phases going in some of the openstack packages; e.g. swift10:37
enikanorovvenv preparation for the tox i mean10:37
idella4I see10:39
idella4prometheanfire can read this when he returns and I can see what he thinks10:39
idella4It looks as if the testr testrunner may offer an alternate path10:41
idella4but I shall have to go learn about how it;s used and operates10:41
*** networkstatic is now known as networkstatic_zZ11:03
idella4it appears the use of testr may suffice11:07
*** idella4 has quit IRC11:13
*** HenryG_ has quit IRC11:16
*** idella4 has joined #openstack-neutron11:21
openstackgerritDuarte Nunes proposed a change to openstack/neutron: MidoNet: Added support for the admin_state_up flag  https://review.openstack.org/5427511:22
idella4enikanorov: There are two mechanisms for running tests: run_tests.sh and tox.  With both mechanisms you can either run the tests in the standard environment11:30
idella4so seems it can be done11:30
idella4testr init followed with testr run seems to be doing something, appears it has no default output11:37
prometheanfireidella4: dev-python/subunit provides the python-subunit package11:39
prometheanfireidella4: also, we don't have to (and I'd rather not) use tox :D11:39
prometheanfireidella4: find out what tox runs as tests, and run them manually ourselves11:39
prometheanfireif tox calls testr then we can just run testr directly11:40
idella4yes that seems to be the key11:40
prometheanfiretox is discouraged in the python herd iirc11:40
prometheanfireand it was cloudy out, so no comet for me :(11:40
idella4running it now directly11:40
idella4ah pity that11:41
prometheanfirethanks :D11:41
prometheanfirehopefully tomorrow will be better11:41
idella4hmm hope so for your sake.  well I have some docs up on testr11:42
prometheanfireeither that or the next day, those are the only chances I have this side of it's orbit around the sun11:42
prometheanfirethis side of perihelion at least11:42
prometheanfireanyway, I'll stop poluting chat here :D11:42
idella4yep11:42
prometheanfireenikanorov: thanks for the talk11:42
openstackgerritDuarte Nunes proposed a change to openstack/neutron: MidoNet: Added support for the admin_state_up flag  https://review.openstack.org/5427511:45
enikanorovyou're welcome11:48
* prometheanfire wonders if it's possible to disable tox's virtualenv function, something to research later11:55
*** cburgess has quit IRC12:04
idella4oh yes please12:07
*** cburgess has joined #openstack-neutron12:10
*** amritanshu_RnD has quit IRC12:24
anttteayaprometheanfire: I'm curious, why do you feel tox is discouraged in the python herd12:39
anttteayait is actively encouraged in openstack12:39
*** anttteaya is now known as anteaya12:39
prometheanfireherds are what we call groups of devs that work on similiar things within gentoo12:41
anteayaenikanorov: tox uses whatever it is configured to use in tox.ini12:42
prometheanfireand the reason I feel we discourage it is because of the way we package/install/test stuff12:42
anteayaokay12:44
anteayaah okay so within gentoo tox is not encouraged12:44
anteayaI didn't know that12:44
prometheanfireya12:44
prometheanfirewell, not encouraged within packaging12:45
anteayayes the move from nose to testr within openstack has taken some time and is gradualling filtering out to all the projects12:45
anteayayes packaging is its own nightmare12:45
prometheanfireya12:45
prometheanfireI'm glad that openstack is centralizing around a set of libs it uses though12:46
prometheanfireI've packaged from folsom to havana for gentoo now12:46
prometheanfireand it's gotten easier12:46
anteayajust wondering since there seems to be pockets of testing culture in various places within openstack which cause pain points when actual integrated testing occurs12:46
anteayafolks using different workflows and not being away what the recommended workflows are12:46
anteayaprometheanfire hat tip to you12:47
prometheanfireya12:47
anteayathat must have been such a headache12:47
prometheanfireas long as we can test by running testr and the like that'll do12:47
anteayayes12:47
prometheanfirewe make sure the deps are installed so tests can run ourselves12:47
anteayafor each project tox.ini runs the test tool specified within12:47
anteayamost projects are on testr now but not all12:48
prometheanfirethat's where I've been looking for what tests to run :D12:48
anteayathe clients were easier to move over12:48
* prometheanfire might test openstack on pypy12:48
anteayagood place to look, ha ha ha12:48
anteayaha ha ha12:48
prometheanfiredid you know, pypy needs 4G to compile....12:48
anteayaand I thought I was the worst person this week for wanting to bang my head against a brick wall12:49
anteayayou out do me in this regard, good sir12:49
anteayaI did not12:49
prometheanfirethis week has not been fun, busy week at work :D12:49
anteayamust be helpful out where I am12:49
anteayanot a fun week for me either12:49
prometheanfirejet lag?12:49
anteayabut I got to watch the sun come up this morning12:50
anteayayeah, that too12:50
anteayaplus I have to drive with my parents on their annual migration south12:50
anteayafirst time I noticed  Ihad to do it12:50
anteayanot what I wanted, not looking forward to it12:50
anteayabut like packaging, sometimes you just have to do it12:50
prometheanfireheh, ya12:51
anteayaso that is week after this one12:51
anteayavery poor timing too12:51
anteayabut i like the alternative less12:51
anteayaso I have to suck it up and do it12:51
prometheanfireI want to actually make a talk at openstack about openstack on gentoo and stuff, we can do a bunch of things in our package manager that others dream of :P12:52
prometheanfirehttp://devmanual.gentoo.org/12:52
* anteaya clicks12:52
prometheanfiredriving is better with passangers12:52
anteayayeah, that is what I am counting on12:53
anteayaand 3 drivers rather than just 212:53
anteayaI have never driven gentoo before12:53
prometheanfireheh, it's very flexible :P12:53
anteayaI've tried ubuntu, xbuntu, fedora, arch for a very short time - too early in my learning12:53
anteayacool12:54
anteayafungi said you gave a talk at an openstack conference in raliegh12:54
anteayaI can't spell correctly12:54
prometheanfireI haven't given a talk for openstack yet :P12:54
anteayaraleigh12:54
anteayano?12:54
prometheanfiremight submit to atlanta, or might wait just to go to paris12:55
anteayaI wonder what fungi was referencing then12:55
* prometheanfire shrugs12:55
anteayaeither or both would be cool12:55
prometheanfireused to live in atlanta12:55
anteayaany suggestions for when I go down to the summit?12:56
prometheanfireabout bars and the like?12:56
prometheanfirenot really, I was younger when I lived there12:57
anteayasure12:58
anteayathings to do12:58
anteayafor instance if you ever go to Budapest order the lemonade12:59
anteayarose water lemonade is amazing12:59
anteayaI had no idea12:59
prometheanfirethe aquarium is nice12:59
anteayacool, thanks12:59
* prometheanfire shrugs12:59
* anteaya adds that to the list12:59
prometheanfirebest one I know of12:59
anteayaawesome12:59
anteayaalso I discovered SF serves everything on a bed of arugala13:00
anteayathat also was unexpected13:00
anteayaeggs florentine with arugala13:00
prometheanfireSF always was odd13:01
anteayaha ha ha13:01
anteayanew york has goat milk ice cream13:01
prometheanfirethat's one city I want to visit13:02
idella4I don't13:02
prometheanfireand somewhere in pac/nw13:02
prometheanfirevisit, not live13:02
anteayaand the best Baba ghanoush I have ever had13:02
anteayaI never thought I would like new york13:02
anteayawas convinced I would hate it13:02
anteayaI love it13:02
anteayacould never live there though13:03
prometheanfireya13:03
idella4oh you northerners13:03
prometheanfireidella4: wat13:03
prometheanfireI'd like to visit .au as well :P13:04
anteayaI'm looking forward to it13:04
anteayalinux con au13:04
anteayathe flight back is going to be interesting13:04
idella4hmm yep, just gotta get pst the 14 hour flight13:04
anteayaperth at about 40 celcius to Montreal at about -20 celcius13:04
anteayayup13:05
prometheanfireya, I'm just worried about the travel13:05
anteayahaving a good seat mate helps13:05
prometheanfirepacific ocean is big13:05
anteayaand fortunately I love movies13:05
anteayaflew over the north pole on my way to HK13:05
anteayacouldn't see anything though, pitch black13:05
prometheanfireaparently the plane out was full of openstackers, and they had free beer13:05
anteayawhich one?13:06
prometheanfireamerican flight I think13:06
anteayanot my cathay pacfic flight13:06
anteayaawesome13:06
prometheanfireout to HK13:06
anteayanice13:06
anteayafree beer would help a 14+ hour flight13:06
idella4anteaya: which distro do you normally use then?13:06
anteayausually an ubuntu13:06
idella4yep it would help13:06
anteayamint is what I have been using13:06
idella4oh ok13:06
anteayadriving ubuntu right now since the tripleo sprint13:07
anteayaI needed raring13:07
prometheanfireya, using ubuntu at work13:07
anteayaI like to move around13:07
anteayatry new stuff13:07
anteayais gentoo related to arch in anyway?13:08
anteayaI see arch mentioned in the gentoo manual13:08
idella4arch is used as an abbrev, for architecture'13:08
prometheanfireit's odd how people switched from rhel based to ubuntu13:08
prometheanfirewish they went to debian instead :P13:08
idella4rather than anything to do with arch linux13:09
anteayaah okay13:09
prometheanfireno, we are totally seperate13:09
prometheanfirewe came first :D13:09
anteayathere are folks wanting debian to be supported13:09
anteaya:D13:09
prometheanfiredebian > ubuntu13:09
anteayayeah13:10
prometheanfirefor server stuff at least13:10
anteayaubuntu feisty fawn was my first13:10
anteayaI was coming off windows and was afraid13:10
anteayaso ubuntu was recommended to me13:10
prometheanfirethough honestly lts ubuntu server isn't bad13:10
anteayaI had to address the fear ms had instilled in me that the world would explode if I switched13:11
anteayaI haven't hit servers particularly hard13:11
anteayaso for my light use I have been happy with it13:11
idella4wow; Ran 18731 tests in 6954.311s \ FAILED (id=0, failures=34, skips=328)13:11
anteayaare the 34 failures similar?13:12
anteayaor all different messages?13:12
idella4test_ovs_tunnel.py13:12
prometheanfirebecause it needs networking?13:13
idella4is the main culprit13:13
prometheanfirethat's my guess13:13
idella4tdout: '\nudevadm settle - timeout of 10 seconds reached, the event queue contains:\n  /sys/module/nvidia (9370323)\n  /sys/module/nvidia (9370328)\n'13:14
prometheanfiregentoo portage sandbox blocks network access13:14
idella4looks like it timedout  so yep13:14
idella4I had already pinned test_ovs_tunnel.py by use of nosetests13:14
prometheanfireidella4: can you raise the timeout?13:14
prometheanfireI don't like timeouts because of the false positives, but I guess they may be needed13:15
idella4possibly, have to open up the test_ovs_tunnel.py and see if the tests stipulate the period13:15
prometheanfireor see if it tries to access the network13:16
idella4INFO [neutron.plugins.openvswitch.agent.ovs_neutron_agent] Mapping physical network net1 to bridge tunnel_bridge_mapping}}}13:16
idella4that's a clue13:16
prometheanfireya13:16
idella4well this has become doable13:17
idella4adter running the thing ALL day long via nosetests13:17
idella4and Stdout: '\nudevadm settle - timeout of 10 seconds reached, the event queue contains:\n  /sys/module/nvidia (9324357)\n  /sys/module/nvidia (9324362)\n'13:17
idella4well rule of thumb the test_ovs_tunnel.py file could do with knocking out entirely13:18
idella4because it pulls in connecting to the network which13:19
idella4will quite possibly leave a clean run with no fails'13:19
idella4It ran Ran 18731 and I'd say in sharper time than nosetests by itself13:20
idella4and it also seems to have skipped some that I had failing13:21
idella4makes for a breakthrough really13:21
prometheanfire:D:D:D13:21
idella4I'll knock out test_ovs_tunnel.py and re-run with time prefixed13:22
prometheanfire:D13:23
idella4so it just lacks output to std.out or whatever it;s called13:24
idella4while running13:24
idella4which basically saves spamming a log file13:25
idella4sorry to interrupt anteaya13:26
anteayano interruption13:28
idella4it seems testr simply calls a; python -m subunit.run discover  so it's using the python builtin discover facility or feature13:28
idella4to pick up the tests13:28
anteayaI'm interested so see your results13:28
idella4ah good13:28
anteayaI think if you check tox.ini that is how testr is configured in that file13:29
* anteaya wonders if she is correct13:29
anteayatox and testr and to a lesser extend nose I have spent time with13:30
idella4I'll look ; python setup.py testr13:30
anteayasubunit I have not addressed yet in my travels13:30
idella4here;s the bummer; python tools/patch_tox_venv.py13:30
idella4so testr is an arg to setup.py, most curious13:31
idella4it's starting to make some sense now13:32
anteayayay13:32
anteayaplease explain your understanding13:33
idella4ok see here13:34
idella4tesr init it seems makes a .testr.conf file13:35
idella4that file has the first line test_command=OS_STDOUT_CAPTURE=1 OS_STDERR_CAPTURE=1 OS_LOG_CAPTURE=1 ${PYTHON:-python} -m subunit.run discover -t ./ neutron/tests/unit $LISTOPT $IDOPTION13:35
idella4so there is a clue to the absent or throttled output to stdout13:36
idella4-t ./ neutron/tests/unit is  saying go look in  ./neutron/tests/unit to find the tests13:36
idella4$LISTOPT $IDOPTION are I guess defined internally or somehow by testr13:37
idella4this is close to tox.ini's python setup.py testr --coverage --testr-args='{posargs}' under [testenv:cover] \ commands13:39
idella4follow13:39
idella4?13:39
anteayayes13:40
idella4so I'm guessing you couls simply edit the tox.ini to take out the actions of python tools/patch_tox_venv.py13:40
anteayawas writing another email13:40
anteayathat would be an interesting experiment13:40
idella4and env related commands13:41
idella4yes13:41
anteayawon't seem to bust anything if you do it13:41
anteayawould be interesting to learn what happens13:41
idella4do you follow all above m'aam13:41
anteayaare you in a vm?13:41
idella4no a regular host atm13:41
anteayathe stdout/err/log yes13:41
anteayacan you move to a vm?13:42
anteayajust in case something goes boom?13:42
prometheanfireportage should protect against that13:42
idella4well  no, don't have one handy13:42
idella4hope so13:42
anteayathe ${PYTHON:-python} is setting the language so python13:42
idella4despite being the xen maintainer of gentoo13:43
anteayaha ha ha13:43
idella4yep13:43
* anteaya covers her eyes13:43
idella4lol13:43
anteayathe subunit.run discover is what you said13:43
anteayago look here for the tests13:43
idella4yes the -t arg lists the location of the tests folder13:44
anteayathe $LISTOPT and $IDOPT I think is allowing you to pass in the name of a certain module or test for just running that test13:44
anteayacool13:44
idella4yes the next 2 lines of .testr.conf read13:44
anteayaI still haven't tried the --parallel option with tox to see if tox will accept it13:45
idella4test_id_option=--load-list $IDFILE \ test_list_option=--list13:45
idella4so they kind o' relate to $LISTOPT and $IDOPT13:45
anteayalooks like it, yeah13:46
idella4what a pleasureto have a gal in the room, well a sheila we'd say down here13:46
anteayaha ha ha13:47
anteayawhat now?13:51
anteayado you have tests running?13:51
idella4yep13:52
anteayacool13:52
prometheanfiretake forever :P13:52
anteayathey do13:52
idella4they're tunning ok, can tell by the activity of the cpu like b413:53
anteayaif they allow paralleliztion it makes all the difference in the world13:53
anteayacool13:53
idella4well they took 2 hours and some minutes running nosetests independently13:53
idella4testr sliced buckets off that with the previous run13:54
idella46954.311s13:54
anteayawoot13:54
idella4was the prior tun's time13:55
idella4was the prior run's time13:55
anteayacool13:55
idella4115 minutes, well less than 2 hours anyways13:56
anteayanot much less13:56
anteayabut less13:56
idella4and this run ought be rid of all those confounded timeouts13:56
anteayalooks like i have some time before the next evaluation13:56
idella4next eval.?13:57
anteayayou post the results of the tests13:58
anteayaand we look at it13:58
anteayaand talk about it13:58
idella4hmm sure13:58
idella4you in the U.S. too young gal?13:58
idella4most all devs I deal with lately do13:59
idella4too13:59
anteayaCanada14:00
anteayagal works young not so much14:00
idella4ah Canada, mb you're more my vintage14:01
idella4I was born pre 196014:01
anteayayou are older14:01
anteayabut I still remember bright orange and blue14:02
idella4I get that alot14:02
anteayaha ha ha14:02
anteayaguitarzan14:02
anteayathere is someone who has that as a nick14:02
anteayaI laughed and laughed14:02
idella4Ray Stevens?14:02
anteayaI was alone in that14:02
anteayayeah14:02
anteayabut ray stevens didn't show up14:02
anteayaI don't think14:02
anteayajust someone with that nick14:02
idella4part pooper he was14:02
idella4party pooper he was then14:03
anteayawell ray is welcome14:03
anteayanot sure if he knows irc14:03
idella4likely nothum14:03
anteayaso yeah, no one else but me and guitarzan got the reference14:04
anteayahappened in the days up to feature freeze14:04
anteayaI needed a laugh14:04
idella4it has its place don't it?14:04
anteayait does14:05
idella4I try to make prometheanfire laugh but it often misfires I think14:06
anteayamisfired fire14:07
prometheanfireic14:07
anteayasounds like the volcano that blows smoke rings14:07
idella4I think so14:08
idella4Is it that  OS_STDOUT_CAPTURE=1 that turns off coverage type output to screen?14:09
anteayaI would go with that assumption14:10
anteayasince running tests tends to be fairly quiet14:11
idella4thought as much14:11
anteayaso much so it shakes up the first time user14:11
anteayathey think it is a hung process14:11
idella4well that's what I thought initially14:11
idella4mostly because our test phases always run output to screen so you can SEE WHAT'S GOING ON14:12
anteayayeah14:13
idella4oh draaat I wish I found this an hour ago14:27
idella4$ testr run --parallel14:27
prometheanfire--help helps :P14:27
idella4This will first list the tests, partition the tests into one partition per CPU on the machine, and then invoke multiple test runners at the same time, with each test runner getting one partition14:28
prometheanfirenot much longer though14:28
idella4now he tell me14:28
idella4hum hum14:28
idella4Actually multiprocessing can get implemented via the distutils-r1 eclass14:29
idella4but that needs running it from the ebuild which is what I'm leading up to14:30
prometheanfirewell, you were worried about system ruining, so I assumed you were using the ebuild14:30
idella4I could have done it from there I s'pose14:31
idella4ah getting error output14:32
*** jroovers has joined #openstack-neutron14:32
idella4means it's all but finished14:32
idella4TypeError: <MagicMock name='LinuxBridgeManager().local_ip' id='726077968'> is not JSON serializable14:32
idella4again14:32
idella4not quite still running14:34
*** jorisroovers has quit IRC14:34
idella4hoping those are non fatal slipups14:34
idella4whoa that should cover all bases; 2 instances running, hopefully the second will overtake the first14:39
*** networkstatic_zZ has quit IRC15:02
*** networkstatic has joined #openstack-neutron15:03
anteayawoot15:05
anteayadidn't realize you had parallel as an option15:05
anteayaI would have suggested it earlier15:05
*** jroovers has quit IRC15:07
*** jorisroovers has joined #openstack-neutron15:11
idella4FAILED (id=1, failures=1 (-33), skips=328)15:16
idella4right the duplicate running with --parallel yielded FAILED (id=1, failures=4 (-30), skips=328)15:17
idella43 of which were OSError: [Errno 12] Cannot allocate memory so I was overtaxing the system15:17
idella4so the first is beautiful just like anteaya15:18
idella4just git to identify the failed test here15:20
enikanorovneutron UTs require lots of memory when being run in parallel15:20
idella4anteaya: you say you've been using testr lately15:20
enikanorovshould be ok with 4 gig though15:20
idella4hmm sure15:20
idella4I'll re-run it on its own now15:21
idella4O got 8 gig RAM15:21
idella4must be this one File "/mnt/gen2/TmpDir/portage/sys-cluster/neutron-2013.2-r1/work/neutron-2013.2/neutron/plugins/linuxbridge/agent/linuxbridge_neutron_agent.py", line 798, in _report_state15:22
anteayaidella4: you are expecting a lot15:23
anteayayou will be disappointed15:23
anteayaI have yes15:23
anteayawell a bit ago15:23
idella4well mb I ought just paste the output I have15:24
anteayahttps://wiki.openstack.org/wiki/Testr15:24
anteayalifeless wrote it15:24
anteayapaste away15:24
anteayaI was saying you will be disappointed if you are expecting that I am beautiful15:24
idella4oh modest you are15:25
anteayanope15:25
anteayajust honest15:25
idella4ok honest have a peruse of this http://codepad.org/jTCkI5on15:26
* anteaya peruses15:26
idella4FAILED (id=1, failures=1 (-33), skips=328) but which is the ailures=1 ?15:27
idella4a number of errors like ERROR:neutron.plugins.linuxbridge.agent.linuxbridge_neutron_agent:Failed reporting state!15:27
idella4nosetests distinguishes between errors and fails15:28
anteayaTypeError: <MagicMock name='LinuxBridgeManager().local_ip' id='726077968'> is not JSON serializable15:28
anteayasomething that expects .json isn't getting .json15:29
anteayaor the ability to become .json15:29
anteayawhat is MagicMock?15:29
* anteaya looks at MagicMock15:29
idella4right linuxbridge_neutron_agent I believe is the common denominator here15:30
anteayaI concur15:31
idella4so that run took 111m16.340s just 4 less than the first run15:31
anteayareally?15:31
anteayathe tests must not support parallelization15:32
anteayaor few of them do15:32
idella4which would be about right seeing I was rid of the several timeouts from test_ovs_tunnel.py15:32
idella4wor there15:32
anteayahow many cores are you running on?15:32
idella4I did 2 concurrent runs15:32
idella4this is the first I started without the parallel option15:32
idella4The second with the option wrapped up in Ran 18668 (+9311) tests in 1758.122s (-5194.175s)15:33
anteayaso 111m vs 29m15:34
idella4exactly15:34
anteayaso yeah, a good difference15:34
anteayaso the tests do support parallelization15:34
anteayawhich is great15:34
idella4do indeed15:34
idella4definitely worth using15:34
anteayayes15:34
idella4as I said the python portage ebuild can add its own multiprocessing layer15:35
idella4when I get that far I'll have to maybe turn one off and leave one on or something similar15:36
anteayaokay15:36
anteayaat this point I am just nodding and smiling15:36
idella4now you rackon I ought knock out ./neutron/plugins/linuxbridge/agent/linuxbridge_neutron_agent.py ?15:37
idella4honest one?15:38
*** jorisroovers has quit IRC15:38
anteayahonestly?15:39
anteayanot a clue15:39
* anteaya looks at the code15:40
idella4well I have 1 single error which you concur stems from15:40
idella4linuxbridge_neutron_agent.py15:40
anteayayes15:41
anteayaMagicMock plays a role15:41
idella4on 4 or more occasions it threw up an outcome of TypeError: <MagicMock name='LinuxBridgeManager().local_ip' id='726077968'> is not JSON serializable15:41
idella4whatever that is exactly15:41
anteayayeah15:43
anteayathe value for local_ip is set in a cnf file: http://git.openstack.org/cgit/openstack/neutron/tree/neutron/plugins/linuxbridge/agent/linuxbridge_neutron_agent.py#n7815:43
anteayacfg.CONF.VXLAN.local_ip15:43
idella4ok I've moved it out now I just need await that repeat with parallelization to complete15:43
anteayayou mv ed that file?15:44
idella4yep15:44
idella4I moved the first one out, the test_ovs_tunnel.py out15:46
anteayahttps://testrepository.readthedocs.org/en/latest/MANUAL.html15:46
anteayayou can see just the failing tests with testr failing15:46
anteayathen I think you can run just failing tests with testr run --failing15:46
anteayaor --failure15:46
anteayasaves 30 minutes or so15:47
anteayasometimes15:47
idella4ah right15:47
idella4I'll move it back15:47
idella4now testr run --failing15:48
idella4hmm15:49
idella4PASSED (id=2)15:49
idella4why did it now pass?15:49
anteayagood question15:50
anteayasounds like a race to me15:50
anteayacan you run it again a few more times15:51
idella4race condition you mean15:51
anteayayes15:51
idella4ooooooh ugh15:51
anteayayeah ugh15:51
idella4could well be15:51
anteayathat is my first thought15:51
anteayaunless changing the filename was the fix15:51
idella4now I changed it back to as it was15:51
anteayaand still passing?15:53
anteayaby itself?15:54
idella4well yep15:54
anteayawell now you have a few options15:54
anteayatry the entire run again and see what happens15:54
idella4which are;15:54
idella4yes15:54
idella4and15:54
anteayatest these tests against other tests15:54
anteayafor instance if the tests are in one file, run that file of tests15:55
anteayalabourous15:55
idella4right you can stipulate a single file by adding the file as an arg15:55
anteayaor find out what the value of local_ip is in the cfg file15:55
anteayayes15:55
idella4to testr yes?15:55
anteayayes15:56
anteayaand to tox15:56
anteayahttp://git.openstack.org/cgit/openstack/oslo-incubator/tree/TESTING.rst15:56
idella4testr run –load-list ./neutron/plugins/linuxbridge/agent/linuxbridge_neutron_agent.py ?15:57
anteayalet's see what that does15:57
anteayaI haven't used -load-list myself15:57
anteayalet me know how it works15:57
idella4eer right15:57
idella4PASSED (id=5)15:58
idella4hmm15:58
idella4I'm going for running the whole thing again, furst with the parallel option15:59
anteayak15:59
anteayasee if they only fail in parallel15:59
anteayathat would be interesting15:59
idella4that will take around 29-30 minutes15:59
idella4you said Montreal is your location?16:00
idella4around -20C there lately?16:01
idella4yes it will be valid to see if the run of the same content yields an identical result16:01
anteayaI'm in Ontario16:02
idella4these race conditions I gather are basically a moving target16:02
anteayabelow zero right now but not -20 yet16:02
anteayain January yes16:02
anteayathey are16:02
idella4right that's peak winter low temp.16:02
anteayawell -35 or -40 is16:03
idella4oh brrrrrrrrrrr16:03
anteaya-20 is typical January weather16:03
anteayaso said the ozzie16:03
idella4a stroll in the park @ -2016:03
anteaya-20 is really nice16:03
anteayapeople have no idea16:03
idella4nice for?16:04
anteayathere are no disagreements at -2016:04
anteayaeveryone gets along16:04
anteayatry it16:04
idella4we all agree it's too damn cold16:04
anteayayes16:04
anteayathat too16:04
anteayalove to hear the ice crack16:04
idella4huh I remember16:04
anteayabeen too warm lately for it to do so16:04
anteayabut it is such a beautiful sound16:05
anteayaI have to move off16:05
anteayaand to other non-keyboard related things16:05
anteayanice to work with you idella416:05
idella4thx16:05
idella4bye16:05
anteayayou can keep commenting in the channel, I will read the log and respond as I can16:05
idella4ah right16:05
anteayado you know where the logs are for this channel?16:06
idella4not offhand no16:06
anteayahttp://eavesdrop.openstack.org/irclogs/%23openstack-neutron/16:06
idella4ah thx16:06
anteayaevery file is a 24 hour period, UTC time16:06
anteayacheers16:06
idella4honest one16:06
* anteaya wanders off16:06
idella4bye16:06
anteaya:D16:06
anteayabye16:06
*** briancline has quit IRC16:11
*** idella4 has quit IRC16:38
*** dkliban has joined #openstack-neutron16:49
*** dkliban has quit IRC16:54
*** dkliban has joined #openstack-neutron16:58
*** networkstatic has quit IRC16:59
*** networkstatic has joined #openstack-neutron17:03
*** rdo_ has quit IRC17:03
*** dkliban has quit IRC17:06
openstackgerritArmando Migliaccio proposed a change to openstack/neutron: Add support for NSX/NVP DHCP services  https://review.openstack.org/4550717:06
*** rdo has joined #openstack-neutron17:27
*** layer427expert has joined #openstack-neutron17:30
*** layer427_ has joined #openstack-neutron17:31
*** layer427expert has quit IRC17:31
*** yportnova has quit IRC17:52
*** dkliban has joined #openstack-neutron17:54
*** rdo has quit IRC18:03
*** dkliban has quit IRC18:08
*** bvandenh has quit IRC18:14
*** scotty916 has joined #openstack-neutron18:18
*** rdo has joined #openstack-neutron18:20
*** scotty916 has quit IRC18:25
*** layer427_ has quit IRC18:25
*** bvandenh has joined #openstack-neutron18:26
*** layer427expert has joined #openstack-neutron18:29
openstackgerritArmando Migliaccio proposed a change to openstack/neutron: Reduce the severity of dhcp related log traces  https://review.openstack.org/5678518:33
*** layer427expert has quit IRC18:54
*** layer427expert has joined #openstack-neutron18:55
*** layer427expert has joined #openstack-neutron18:59
*** layer427expert has quit IRC19:12
*** dkliban has joined #openstack-neutron19:26
*** jlibosva has joined #openstack-neutron19:30
*** dkliban has quit IRC19:54
*** mjbright_ has joined #openstack-neutron21:48
*** jorisroovers has joined #openstack-neutron21:59
*** suresh12 has joined #openstack-neutron21:59
*** jroovers has joined #openstack-neutron22:00
*** jorisroovers has quit IRC22:03
*** nati_ueno has joined #openstack-neutron22:20
openstackgerritArmando Migliaccio proposed a change to openstack/neutron: Reduce the severity of dhcp related log traces  https://review.openstack.org/5678522:22
*** layer427expert has joined #openstack-neutron22:30
*** nati_ueno has quit IRC22:33
*** jroovers has quit IRC22:49
*** suresh12 has quit IRC22:56
*** suresh12 has joined #openstack-neutron22:56
*** suresh12 has quit IRC23:01
*** layer427expert has quit IRC23:05
*** steven-weston has joined #openstack-neutron23:25
*** cburgess has quit IRC23:29
*** alexpilotti has quit IRC23:32
*** cburgess has joined #openstack-neutron23:33
*** silvrax_ has quit IRC23:33

Generated by irclog2html.py 2.14.0 by Marius Gedminas - find it at mg.pov.lt!