Wednesday, 2020-11-04

openstackgerritMerged openstack/placement master: Adds py38 functional tests to gate  https://review.opendev.org/75116801:37
*** zzzeek has quit IRC03:24
*** zzzeek has joined #openstack-placement03:25
*** evrardjp has quit IRC05:33
*** evrardjp has joined #openstack-placement05:33
*** spatel has joined #openstack-placement07:58
*** spatel has quit IRC08:03
*** spatel has joined #openstack-placement10:59
*** spatel has quit IRC11:04
*** spatel has joined #openstack-placement12:27
*** spatel has quit IRC12:32
openstackgerritBalazs Gibizer proposed openstack/placement master: Add functional-py3[89] tox targets  https://review.opendev.org/76089012:42
openstackgerritBalazs Gibizer proposed openstack/osc-placement master: Add functional-py39 tox target  https://review.opendev.org/76091212:44
*** cdent has joined #openstack-placement12:58
*** spatel has joined #openstack-placement14:15
*** martinkennelly has joined #openstack-placement17:47
*** mugsie has quit IRC18:18
*** mugsie has joined #openstack-placement18:21
*** janice61 has quit IRC18:56
*** janice61 has joined #openstack-placement19:03
lbragstadhey all, is there a way to tell gabbi to report captured logged during a functional run? i see the APIFixture is capturing stdout and logging, but i can't seem to find a way to tell gabbi to report those things during a failed test run19:12
lbragstadcaptured logging*19:12
cdentahoy lbragstad19:50
cdentIs this in the placement tests or somewhere else?19:51
lbragstadyeah - specifically the placement functional API test built using gabbi19:51
lbragstadtests*19:52
lbragstadfor context - i'm working on some tests for https://review.opendev.org/#/c/760235/19:52
cdentHmmm. It’s supposed to be using the capture.Logging inner fixture for that (see in tests/functional/test_api.py19:52
cdentand output.CaptureOutput19:52
cdentif it’s not working there’s at least two possibilities: something changed … somewhere19:53
lbragstadand after reading the contributor guide, it sounded like the functional api tests were the right spot for that sort of thing19:53
cdentor the test is failing in too catastrophic a fashion19:53
cdentor is that you’re after looking at the logs from within the test?19:54
lbragstadnot specifically - my tests aren't asserting anything in the logs, yet19:54
lbragstadi'm just trying to use the logger to figure out the state of specific things during the request19:54
lbragstadfor example - http://paste.openstack.org/show/799708/19:54
lbragstadand since the tests appear to be capturing stdout and the logs, i figured it would be output during the test run19:55
cdentdoes it make any difference if you switch to a higher log level?19:56
cdentbecause of stestr you’ll only see the output if there’s a failure19:57
cdents/because/also because/19:57
lbragstadi'll try that quick19:57
lbragstadcdent a higher log level doesn't appear to make a difference (i used debug, error, and critical)19:59
cdentand this is on a failing test?20:00
lbragstadthe test is failing, yes20:00
lbragstadthis is what i have locally http://pastebin.test.redhat.com/915656 on top of 76023520:02
cdenttry putting your log message somewhere other than in policy.py as the default fixutres may not be touching policy depending on which tests you’ve got going on20:04
*** artom has quit IRC20:04
cdenttests/functional/fixtures/gabbits.py  has some stuff on which things get engaged for which fixtures20:05
cdent( can’t see that url )20:05
lbragstadoh - dang20:05
cdentIf you leave more info here, I’ll catch up later, but I’m a bit in the middle of something20:05
lbragstadsorry - i'll repaste20:05
cdentbut would like to make sure this works, since it should…20:05
cdentso can check back a bit later in the day20:06
lbragstadhttp://paste.openstack.org/show/799709/20:06
lbragstadno worries - it's not a huge rush20:06
cdent20:06
cdentlbragstad: it’s because of the version of gabbi. In 2.0.4 or thereabouts I removed testtools and the the olsotest capture fixtures that do output capture expect that to be there (but don’t actually require it). Basically testtools has some “gather up the data at the end of the test” routines21:43
cdentI removed testtools because it causes a dependency cycle in some contexts21:43
lbragstadahh21:44
lbragstadinteresting21:44
cdentWhat I meant to do what include most of the relevant testtools functionality in the TestCase subclass that gabbi carries itself21:44
cdentbut apparently I left that bit out21:44
cdentthis is the pull request that remove the support: https://github.com/cdent/gabbi/pull/27921:45
cdentthere’s a typo : Please where I meant “Pleas”21:45
cdentI’ll make a bug and see about fixing it, soon. In the meantime if you drop down to gabbi<2 it should be fine21:46
lbragstadok - i'll give that a shot locally quick21:47
cdentlemme know21:47
lbragstadcdent excellent http://paste.openstack.org/show/799713/21:50
cdentyah, makes sense. I pinged you from the newly created issue21:51
lbragstadcdent perfect, thank you for the help21:54
*** artom has joined #openstack-placement21:54
cdentlbragstad: keeping placement on <2 will probably be safe/fine. Most of the changes have been to remove python 2isms and make some minor tweaks here and there. The only change that could be relevant is this one https://github.com/cdent/gabbi/commit/c5b08a1fce4ee7be40aa2d2a2521fbe8c434d279 but in placement the headers are always the same so…21:55
cdentBut I’ll try to fix the bug in any case. In my copious free time and all that.21:55
lbragstad:)21:55
lbragstadyeah - i should be able to just use gabbi < 2 for investigative purposes, then i hop to get the tests working (which shouldn't be specific to gabbi < 2)21:56
lbragstads/hop/hope/21:56
* cdent hops21:56
*** artom has quit IRC22:02
*** artom has joined #openstack-placement22:03
*** spatel has quit IRC22:06
*** cdent has quit IRC22:51
*** spatel has joined #openstack-placement23:12
*** spatel has quit IRC23:17

Generated by irclog2html.py 2.17.2 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!