Friday, 2015-06-05

*** alexpilotti has quit IRC00:10
*** dims__ has joined #openstack-oslo00:11
*** dims_ has quit IRC00:12
*** vilobhmm has joined #openstack-oslo00:12
harlowjalifeless have u seen http://paste.openstack.org/show/264329/ ?00:15
harlowja$ pip freeze | grep testtools00:15
harlowjatesttools==1.8.000:15
*** sputnik13 has quit IRC00:16
lifelessharlowja: too-old pbr00:16
harlowjaah00:16
harlowjak00:16
lifelessharlowja: how did you install testtools ?00:16
harlowjapip, but in a old venv i guess00:16
*** dims__ has quit IRC00:17
lifelessI'll check the install_requires is appropriately versioned, it may not be00:17
harlowjak00:17
*** dims_ has joined #openstack-oslo00:17
harlowjaupdated @ https://review.openstack.org/#/c/188633/00:18
harlowjathx00:19
*** jaosorior has quit IRC00:22
*** vilobhmm has quit IRC00:27
*** tsekiyam_ has joined #openstack-oslo00:42
*** tsekiyam_ has quit IRC00:42
*** mtanino has quit IRC00:43
*** tsekiyama has quit IRC00:45
*** amotoki has joined #openstack-oslo00:53
*** salv-orlando has joined #openstack-oslo00:54
*** salv-orlando has quit IRC01:10
*** stpierre has quit IRC01:30
*** stpierre has joined #openstack-oslo01:31
*** tobe has joined #openstack-oslo01:38
*** Kiall_ has joined #openstack-oslo01:43
*** Kiall has quit IRC01:43
*** vilobhmm has joined #openstack-oslo01:46
tchaypolifeless: I’ve re-added the checks on requires.txt to https://review.openstack.org/187846 (well, the change it depends on) to make sure that requires.txt is being generated properly, and that passes; but even with setuptools>=16, in every test, either we get ‘invalid environment marker’ or we end up with the requirements missing01:56
tchaypolifeless: the biggest doubt I’ve got is whether I’m calling pip properly01:56
lifelesstchaypo: ok, so I should pull it down again and poke? Where are you seeing invalid environment market btw02:01
*** vilobhmm has quit IRC02:01
lifelesstchaypo: still python 2.6 only?02:01
tchaypoon the most recent run, 26, 27, and 3402:02
tchaypoon patchset 5, test_requirement_parsing(editable,tree,pbr_not_installed) (and maybe others) didn’t get invalid environment marker, but did fail to install the requirements02:04
*** yamahata has quit IRC02:04
lifelessweird02:06
*** salv-orlando has joined #openstack-oslo02:09
*** gordc has quit IRC02:13
*** salv-orlando has quit IRC02:17
*** stevemar has quit IRC02:40
*** achanda has joined #openstack-oslo02:46
*** boris-42 has quit IRC02:58
*** stpierre has quit IRC03:00
*** achanda has quit IRC03:00
*** dims_ has quit IRC03:07
tchaypoLifeless: makati is having a look at pbr now. She's running into issues with the tests that invoke GPG in test_packaging.TestVersions - it seems to be because she has a newer GPG - so she's planning to poke at those03:18
lifelessk03:21
lifelesswho is makati ?03:21
*** amotoki has quit IRC03:22
lifelesstchaypo: ?^03:50
*** salv-orlando has joined #openstack-oslo03:51
tchaypoBah03:55
tchaypo*nakato03:55
*** exploreshaifali has joined #openstack-oslo03:56
*** salv-orlando has quit IRC04:01
*** dims_ has joined #openstack-oslo04:05
*** dims_ has quit IRC04:10
*** rpodolyaka1 has joined #openstack-oslo04:15
*** rushiagr_away is now known as rushiagr04:22
*** rushiagr is now known as rushiagr_away04:27
*** amotoki has joined #openstack-oslo04:31
*** jamielennox is now known as jamielennox|away04:32
*** rpodolyaka1 has quit IRC04:38
*** rushiagr_away is now known as rushiagr04:40
*** rpodolyaka1 has joined #openstack-oslo04:58
Nakatore-pbr-tests: So it breaks due to %no-ask-password being a no-op in 2.1, so just need to use new options with 2.105:16
lifelesscool05:18
tchayposhouldn’t a no-op do nothing?05:18
lifelessIt would be nice if gpg could pick one way of doing this and stick to it05:18
tchaypoor is it one of those not-much-ops that very noisly does nothing?05:18
lifelesstchaypo: its no-opping - so it asks for a password; is how I interpret Nakato's statement05:19
tchaypo… oh.05:19
Nakatolifeless: precisely, which fails when it's not interactive05:19
tchaypole sigh05:21
*** achanda has joined #openstack-oslo05:25
*** exploreshaifali_ has joined #openstack-oslo05:28
*** exploreshaifali has quit IRC05:29
*** sputnik13 has joined #openstack-oslo05:37
*** tobe has quit IRC05:41
*** tobe has joined #openstack-oslo05:42
*** achanda has quit IRC05:43
*** tobe has quit IRC05:44
*** mdbooth has quit IRC05:48
*** mdbooth has joined #openstack-oslo05:53
*** jaosorior has joined #openstack-oslo05:54
*** rpodolyaka1 has quit IRC06:02
*** achanda has joined #openstack-oslo06:09
openstackgerritSachi King proposed openstack-dev/pbr: Fix test case to be runnable with gnupg 2.1  https://review.openstack.org/18867506:10
*** vilobhmm has joined #openstack-oslo06:12
*** amotoki has quit IRC06:16
*** tobe has joined #openstack-oslo06:19
jd__harlowja: yeah thanks I wanted to investigate on that migration, you beat me to it06:23
*** amotoki has joined #openstack-oslo06:25
*** sputnik13 has quit IRC06:29
*** amotoki has quit IRC06:36
*** amotoki has joined #openstack-oslo06:37
openstackgerritSachi King proposed openstack-dev/pbr: Fix test case to be runnable with gnupg 2.1  https://review.openstack.org/18867506:41
*** amotoki has quit IRC06:41
*** exploreshaifali_ has quit IRC06:45
*** vilobhmm has quit IRC06:46
*** rpodolyaka1 has joined #openstack-oslo06:52
*** dims_ has joined #openstack-oslo06:54
openstackgerritMerged openstack/oslotest: Fix argument handling in oslo_run_cross_tests  https://review.openstack.org/18852706:54
*** e0ne has joined #openstack-oslo06:54
lifelessNakato: patch is looking ok, but did you see my second erview comment?06:55
*** takedakn has joined #openstack-oslo06:56
*** dims_ has quit IRC06:59
*** takedakn has quit IRC07:00
*** takedakn has joined #openstack-oslo07:01
*** e0ne has quit IRC07:04
*** takedakn has quit IRC07:04
lifelessNakato: ah nvm, I read the diff badly!07:11
ekarlsosileht: heya, you about mr ?07:12
*** takedakn has joined #openstack-oslo07:16
*** prashant-upadhya has joined #openstack-oslo07:17
Nakatolifeless: Yea saw that, bit confusing when a script has commented out things in it...  Saved me a great deal of research though as I started by looking up what those options were.07:17
prashant-upadhyahi nakato07:17
prashant-upadhyai have a query regarding rpc.call/cast07:17
*** takedakn has quit IRC07:17
prashant-upadhyacan u help me07:17
*** takedakn has joined #openstack-oslo07:18
NakatoSorry prashant-upadhya, I currently don't know anything about that.07:18
*** takedakn has quit IRC07:18
*** takedakn has joined #openstack-oslo07:19
prashant-upadhyai want to know how message reaches its destination . how topic subsribers get to know a message has reached. is there some documents i can go through07:19
prashant-upadhyasomebody else who knows it.. can help07:19
prashant-upadhya:)07:19
*** takedakn has quit IRC07:22
*** achanda has quit IRC07:28
lifelessprashant-upadhya: probably need to read the rabbitmq docs07:32
prashant-upadhyaokay ; is there any way to see the logs of queues . what message it got from whom . who picked it ?07:33
lifelesssee the rabbitmq docs for all that sort of thing IMO07:34
*** exploreshaifali has joined #openstack-oslo07:36
*** rpodolyaka1 has quit IRC07:44
*** achanda has joined #openstack-oslo07:52
*** achanda_ has joined #openstack-oslo08:01
*** achanda has quit IRC08:04
*** ajo_ has joined #openstack-oslo08:05
*** ihrachyshka has joined #openstack-oslo08:10
openstackgerritElena Ezhova proposed openstack/oslo.service: Add entrypoints for option discovery  https://review.openstack.org/18760708:19
*** yassine_ has joined #openstack-oslo08:21
eezhovadhellmann, hello! I updated the review ^^^. Do the entrypoints look okay and what additional documentation should I add?08:22
*** rpodolyaka1 has joined #openstack-oslo08:27
openstackgerritVictor Sergeyev proposed openstack/oslo.messaging: Reduce `magic` conf attribute usage  https://review.openstack.org/18792308:30
*** sdake has quit IRC08:34
*** ndipanov has joined #openstack-oslo08:37
*** rpodolyaka1 has quit IRC08:45
*** achanda_ has quit IRC08:46
*** rpodolyaka1 has joined #openstack-oslo08:46
ekarlsosileht: heya, I got a Q regarding oslo.messaging, is it possible to have it send more raw data vs the data being wrapped in some oslo dicT ?08:47
*** ozamiatin has joined #openstack-oslo08:54
*** cdent has joined #openstack-oslo09:00
*** Kiall_ has quit IRC09:05
*** Kiall has joined #openstack-oslo09:06
*** e0ne has joined #openstack-oslo09:09
*** prashant-upadhya has quit IRC09:13
*** exploreshaifali has quit IRC09:23
*** Kiall has quit IRC09:24
*** Kiall_ has joined #openstack-oslo09:24
openstackgerritElena Ezhova proposed openstack/oslo.service: Introduce abstract base class for services  https://review.openstack.org/18871409:25
*** ajo_ has quit IRC09:33
*** prashant-upadhya has joined #openstack-oslo09:34
*** dims_ has joined #openstack-oslo09:43
*** rpodolyaka1 has quit IRC09:43
*** alexpilotti has joined #openstack-oslo09:45
*** dims__ has joined #openstack-oslo09:47
*** rpodolyaka1 has joined #openstack-oslo09:48
*** dims_ has quit IRC09:48
*** Kiall_ has quit IRC09:53
*** Kiall has joined #openstack-oslo09:56
*** rpodolyaka1 has quit IRC10:04
*** e0ne is now known as e0ne_10:07
*** rpodolyaka1 has joined #openstack-oslo10:07
*** e0ne_ is now known as e0ne10:12
*** rpodolyaka1 has quit IRC10:13
silehtekarlso, no this is not possible, I wonder why you need that, this dict containt the information to decode the payload ie: the version tell that the message is a json dict with a payload a context...10:14
ekarlsosileht: if you're wanting to send info to logstash for example..10:14
silehtekarlso, the application consumer need to decode the message and transform it to something suitable for logstash10:16
silehtekarlso, otherrise if one day we change the content of the message, you logstash will be borken10:16
ekarlsosileht: uhm, logstash is a PITA to do that kinda stuff ie extract stuff in payload etc into something useful10:17
ekarlsobut I guess i'm off writing my own notification listener then10:17
silehtekarlso, to have something solid you have to wrote something (or use oslo.messaging) that understand the message format10:18
ekarlsosileht: i guess a notifi listener is the best thing then :'(10:19
silehtekarlso, or don't use logstash :p10:20
openstackgerritMerged openstack/oslo.db: Allow to fail instead of skip in DbFixture  https://review.openstack.org/18771710:20
*** achanda has joined #openstack-oslo10:20
silehtekarlso, fluentd is not cool for that too10:20
ekarlsosileht: really logstash is more or the less like a notification listener no ?10:20
*** boris-42 has joined #openstack-oslo10:20
silehtekarlso, yes this a notification listener, but it doesn't decode the message format10:21
ekarlsoah well ok10:21
ekarlsosileht: is there a way to just publish notifications to 1 topic vs topic.info etc ?10:22
silehtekarlso, you have to use grok or something like that to read the pauload10:22
dims__sileht: easy ones? https://review.openstack.org/#/c/187963/ and https://review.openstack.org/#/c/185853/10:33
silehtdims__, done10:34
dims__sileht: this one may be a long one for the weekend :) https://review.openstack.org/#/c/187338/10:35
dims__jd__: flaper87: any opinion on this one? https://review.openstack.org/#/c/143423/10:35
ihrachyshkadims__, hey. I have a concern around debtcollector. it seems it uses DeprecationWarnings that are disabled by default in py27+, so if we want to see those warnings, we need to enable them globally for all libraries, including those that we don't control.10:37
ihrachyshkadims__, while versionutils module allows us to report just those that we explicitly request10:37
ihrachyshkacomments?10:37
*** SergeyLukjanov has quit IRC10:39
dims__ihrachyshka: are you using versionutils right now?10:42
ihrachyshkadims__, we consider it for one of deprecations in neutron. yes, we also use it in several places.10:43
dims__ihrachyshka: then i'd be ok for you to continue with that but the one from oslo.log10:43
ihrachyshkawe wanted to extend versionutils to support keyword deprecation, but were asked to use debtcollector.10:43
ihrachyshkaso we looked into it and don't get how to enable warnings without bloating logs with irrelevant stuff10:44
dims__let's involve dhellmann and harlowja in this discussion as it is important.10:44
dims__ihrachyshka: point me to the review please?10:44
ihrachyshkadims__, neutron review that raised the need of keyword deprecation: https://review.openstack.org/17523810:45
ihrachyshkadims__, and versionutils extension for that: https://review.openstack.org/187530 (abandoned due to debtcollector)10:45
dims__ihrachyshka: can you please unabandon that one? and paste this chat there10:47
dims__looks like we did not wait for dhellmann's response on that one10:48
ihrachyshkadims__, done10:49
ihrachyshkaall in all, seems like adopting debtcollector as the way to go for openstack can be blocked by this. unless we extend the lib to log with something more visible.10:50
*** SergeyLukjanov has joined #openstack-oslo10:51
dims__ihrachyshka: ack11:02
dims__lifeless: around?11:02
*** prashant-upadhya has quit IRC11:03
*** e0ne is now known as e0ne_11:05
*** e0ne_ is now known as e0ne11:07
dims__lifeless: i am slowly adding to py34 tests in nova (using testtools.run), the white list is becoming quite big - https://review.openstack.org/#/c/188653/3/tox.ini,cm - any suggestions to better manage it outside of tox.ini?11:08
*** prashant-upadhya has joined #openstack-oslo11:09
openstackgerritMerged openstack/oslo.messaging: Enable `fanout_target` scenarios in test_impl_rabbit  https://review.openstack.org/18796311:20
openstackgerritMerged openstack/oslo.messaging: rabbit: test for new reply behavior  https://review.openstack.org/18585311:20
ihrachyshkadims__, why not working on covering a single tree of tests so that you can merge multiple entries into one?11:23
*** ozamiatin has quit IRC11:26
openstackgerritElena Ezhova proposed openstack/oslo.service: Make logging option values configurable  https://review.openstack.org/18874711:31
*** rpodolyaka1 has joined #openstack-oslo11:31
*** achanda has quit IRC11:35
*** prashant-upadhya has quit IRC11:42
*** tobe has quit IRC11:42
*** jecarey has joined #openstack-oslo11:52
*** rpodolyaka1 has quit IRC12:04
*** rpodolyaka1 has joined #openstack-oslo12:06
*** e0ne is now known as e0ne_12:21
*** e0ne_ is now known as e0ne12:22
*** kgiusti has joined #openstack-oslo12:34
*** ndipanov is now known as ndipanoff12:36
*** shardy_ has joined #openstack-oslo12:39
*** shardy has quit IRC12:39
*** gordc has joined #openstack-oslo12:41
*** bknudson has joined #openstack-oslo12:44
*** shardy_ has quit IRC12:44
*** shardy has joined #openstack-oslo12:44
*** exploreshaifali has joined #openstack-oslo12:57
*** dims__ has quit IRC13:09
*** dims_ has joined #openstack-oslo13:10
*** boris-42 has quit IRC13:18
*** ozamiatin has joined #openstack-oslo13:19
*** rpodolyaka1 has quit IRC13:20
*** rpodolyaka1 has joined #openstack-oslo13:24
*** stpierre has joined #openstack-oslo13:25
*** mriedem has joined #openstack-oslo13:27
*** rushiagr is now known as rushiagr_away13:28
*** kgiusti has quit IRC13:29
*** kgiusti has joined #openstack-oslo13:30
*** shardy_ has joined #openstack-oslo13:36
*** shardy has quit IRC13:36
*** e0ne is now known as e0ne_13:39
*** e0ne_ is now known as e0ne13:39
*** jecarey has quit IRC13:40
*** shardy_ has quit IRC13:41
*** boris-42 has joined #openstack-oslo13:41
*** shardy has joined #openstack-oslo13:42
*** exploreshaifali has quit IRC13:43
*** jaypipes is now known as leakypipes13:43
*** jecarey has joined #openstack-oslo13:52
*** exploreshaifali has joined #openstack-oslo14:00
*** zzzeek has joined #openstack-oslo14:01
*** yamahata has joined #openstack-oslo14:03
*** exploreshaifali has quit IRC14:06
*** achanda has joined #openstack-oslo14:10
*** shardy_ has joined #openstack-oslo14:11
*** shardy has quit IRC14:12
*** sigmavirus24_awa is now known as sigmavirus2414:12
*** amrith is now known as _amrith_14:12
*** e0ne is now known as e0ne_14:16
*** shardy_ has quit IRC14:16
*** shardy has joined #openstack-oslo14:17
*** rushiagr_away is now known as rushiagr14:18
*** rpodolyaka1 has quit IRC14:25
*** e0ne_ has quit IRC14:26
*** mtanino has joined #openstack-oslo14:29
*** salv-orlando has joined #openstack-oslo14:31
*** dansmith is now known as superdan14:32
*** rpodolyaka1 has joined #openstack-oslo14:38
*** yamahata has quit IRC14:43
*** stevemar has joined #openstack-oslo14:44
*** zzzeek has quit IRC14:45
*** e0ne has joined #openstack-oslo14:45
*** zzzeek has joined #openstack-oslo14:46
*** zzzeek has quit IRC14:46
*** achanda has quit IRC14:56
*** _amrith_ is now known as amrith15:01
*** sputnik13 has joined #openstack-oslo15:22
*** e0ne is now known as e0ne_15:29
*** e0ne_ is now known as e0ne15:30
*** shardy_ has joined #openstack-oslo15:30
*** e0ne is now known as e0ne_15:30
*** e0ne_ is now known as e0ne15:30
*** shardy has quit IRC15:31
*** arnaud____ has joined #openstack-oslo15:32
*** achanda has joined #openstack-oslo15:34
*** shardy_ has quit IRC15:35
*** tsekiyama has joined #openstack-oslo15:36
*** shardy has joined #openstack-oslo15:36
ihrachyshkadhellmann, hey15:39
ihrachyshkaI have debtcollector concern15:40
dhellmannihrachyshka: hi15:42
openstackgerritMerged openstack/oslotest: Updated from global requirements  https://review.openstack.org/18856915:43
ihrachyshkadhellmann, concern is: debtcollector does not log by default, and if I enable deprecation warnings, I get all of them, not just from openstack components15:43
ihrachyshkadhellmann, should we run with deprecation warnings enabled, always and globally?15:43
dhellmannihrachyshka: we don't want the messages logged anywhere other than unit test jobs, and those can turn on the warnings themselves15:43
dhellmannihrachyshka: deployers cannot fix a problem with a deprecated internal API, so they don't need to see the warning15:44
ihrachyshkawell, then how would other consumers of neutron code catch that they use it in wrong way?15:44
ihrachyshkaso versionutils is for user actionable items while debtcollector for code issues?15:45
dhellmannihrachyshka: the unit test jobs should have warnings turned on, so that the deprecation warnings are emitted15:45
dhellmannand yes, that's why we have them in separate libraries, the messages are intended for different audiences15:46
*** david-lyle has quit IRC15:46
dhellmanndebtcollector is also not tied to openstack release names for the same reason15:46
ihrachyshkadhellmann, got it. do you think anyone reads unit tests output, especially since we run it thru tox that swallows everything?15:46
*** david-lyle has joined #openstack-oslo15:46
dhellmannihrachyshka: when I run tox locally I see deprecation warnings as the jobs start up. don't you?15:47
*** pblaho has quit IRC15:47
dhellmannthose might only be on import, though15:47
dhellmanndims_, harlowja: have any thoughts on ^^?15:48
*** amrith is now known as _amrith_15:49
*** crc32 has joined #openstack-oslo15:52
*** ozamiatin has quit IRC15:54
*** ozamiatin has joined #openstack-oslo15:56
dims_dhellmann: i like the distinction you were making15:59
*** achanda_ has joined #openstack-oslo15:59
dims_unit tests vs deployed instance15:59
dhellmanndims_: do you share ihrachyshka's concerns about those warnings not being visible from unit tests?15:59
dims_dhellmann: i do see a whole bunch when i run tox targets locally with nova16:00
dhellmannok, cool, I was worried maybe I had something special set up to enable that16:00
*** achanda has quit IRC16:00
*** ozamiatin has quit IRC16:00
openstackgerritDoug Hellmann proposed openstack/oslo-incubator: Remove versionutils  https://review.openstack.org/18242816:05
ihrachyshkadhellmann, in which repo do you see them?16:07
ihrachyshkadhellmann, in neutron, I only get list of test names + ... ok16:07
*** shardy_ has joined #openstack-oslo16:07
*** ashleighfarnham has joined #openstack-oslo16:08
*** shardy has quit IRC16:08
dhellmannihrachyshka: dims_ reported seeing them for nova, and I've seen them in a couple of different places. Maybe there is something about those jobs that enables showing them? Maybe compare the neutron setup and nova setup?16:10
*** shardy_ has quit IRC16:13
*** shardy has joined #openstack-oslo16:13
*** exploreshaifali has joined #openstack-oslo16:14
*** crc32 has quit IRC16:18
dims_ihrachyshka: dhellmann: example when i run tox py34 in nova http://paste.openstack.org/show/266386/16:20
ihrachyshkadims_, is it at the start of tox run?16:21
dims_ihrachyshka: no, just a random snip from my screen16:21
*** e0ne is now known as e0ne_16:23
ihrachyshkadims_, oh indeed I see them now. in nova at least.16:24
ihrachyshkathough in a different format16:24
*** e0ne_ has quit IRC16:24
ihrachyshkadims_, so is there a way to execute unit tests in a way that they fail on deprecation warnings?16:25
ihrachyshkaif it does not fail, it's not getting attention at all16:26
*** achanda_ has quit IRC16:26
dims_ihrachyshka: here's what the keystone folks use - https://review.openstack.org/#/c/187640/1/keystone/tests/unit/core.py,cm16:27
dims_bknudson can fill in details on what they do :)16:28
dstanekdims_: that would be a great thing to add everywhere to catch deprecation warnings16:30
dims_dstanek: unfortunately it stops people in their tracks and makes them copy code :)16:30
ihrachyshkaoh, filter on namespace is nice16:31
ihrachyshkawe don't want to be broken by external libs16:31
ihrachyshkathough that would mean that we immediately break consumers once we mark anything as deprecated.16:33
dims_right16:33
ihrachyshkathe only workaround for them would be to reset it back to 'normal'16:33
ihrachyshkaor fix breakage16:33
ihrachyshkamaybe we should just promote disabling it by default if they don't want to chase neutron16:34
ihrachyshkaand provide a way to enable it for a specific test run16:34
ihrachyshkavia envvar16:34
*** rpodolyaka1 has quit IRC16:34
ihrachyshkaor go vice versa: enable it for neutron jobs only, and allow consumers of the code to opt in16:34
*** rpodolyaka1 has joined #openstack-oslo16:35
*** arnaud____ has quit IRC16:35
ihrachyshkaok, I think we have now clear way to go for neutron16:35
ihrachyshkathanks dims_ and dhellmann for clarifications16:35
*** rpodolyaka1 has quit IRC16:36
dstanekdims_: ihrachyshka: is this for more than just unit tests?16:39
*** sdake has joined #openstack-oslo16:40
*** e0ne has joined #openstack-oslo16:40
ihrachyshkadstanek, I want to expose it for most tox controlled jobs, for neutron it's functional, unit, fullstack, probably api16:42
*** e0ne has quit IRC16:43
*** achanda has joined #openstack-oslo16:43
*** sdake_ has joined #openstack-oslo16:44
*** yassine_ has quit IRC16:45
*** ashleighfarnham has quit IRC16:46
*** sdake has quit IRC16:48
*** rpodolyaka1 has joined #openstack-oslo16:49
ihrachyshkadims_, hm, neutron\\. filter still raises oslo invoked deprecations as if they are failures16:50
*** rpodolyaka1 has quit IRC16:54
*** achanda has quit IRC16:55
bknudsonI would have been happy to change keystone to use the workaround (isoformat), but it wouldn't be backwards compatible.17:00
bknudsonI've got a similar change in keystonemiddleware - https://review.openstack.org/#/c/187775/17:01
bknudsonmaybe there could be a fixture that we could use instead.17:01
bknudsonnova has http://git.openstack.org/cgit/openstack/nova/tree/nova/tests/fixtures.py#n24717:02
ihrachyshkabknudson, so while keystone has that keystone\\. filter for DeprecationWarnings, isn't it now broken by any change in e.g. oslo libs that would raise a new deprecation?17:02
bknudsonihrachyshka: the tests fail if keystone is calling a deprecated function.17:03
bknudsonat which point we need to fix it.17:03
bknudsonwhich makes sense... keystone shouldn't be calling function that's not supported17:03
ihrachyshkabknudson, so you are frequently broken by a new release and are ok with that?17:03
ihrachyshkait's still supported while it's deprecated17:03
bknudsonit's only happened once so far17:03
dstanekihrachyshka: it's good to be broken like that so that we are not fighting to catch up17:04
bknudsonif a library wants to warn users about deprecation they can use PendingDeprecation instead.17:04
ihrachyshkaI'm not sure neutron team will be ok with that kind of breakages :)17:04
bknudsonI would have liked to see a PendingDeprecation because then we could have fixed it in our own time.17:04
bknudsonor, more likely, it would have been ignored until we were totally broken.17:04
ihrachyshkabknudson, though if you are not broken, it's easy to just miss the warning17:04
ihrachyshkaright17:05
bknudsonmy opinion is that it's better to know right away so that we're not picking up debt.17:06
bknudsonand, it's easy to unbreak, just disable the guard.17:06
bknudsonor, the deprecation message should say what the remediation is, so do that17:07
*** vilobhmm has joined #openstack-oslo17:10
harlowjadims_ dhellmann perhaps oslotest should enable https://github.com/testing-cabal/fixtures/blob/master/fixtures/_fixtures/warnings.py by default, and dump them out or something (or blowup? of any are triggered)17:11
harlowjaor something else (print the messages in big bold blinky red html)17:12
harlowjaso then it shows up as blinky red html (with a sad face next to it)17:12
bknudsonit's hard to get output from unit tests.17:13
bknudsonor it seems to be anyways17:13
bknudsonsome projects don't show any output and others have all sorts of it17:13
bknudsonthe change of keystoneclient to oslotest starts printing all sorts of stuff where it didn't before --https://review.openstack.org/#/c/187770/517:14
bknudsonI haven't had a chance to look into why17:14
bknudsonalso running tox -e py34 has lots of output where py27 doesn't17:15
*** ashleighfarnham has joined #openstack-oslo17:15
*** achanda has joined #openstack-oslo17:16
harlowjahmmmm17:17
harlowjaodd17:17
ihrachyshkafor py34 vs py27, it's clear why.17:18
harlowjahttps://docs.python.org/3/library/warnings.html#default-warning-filters (maybe thats the reason?)17:19
harlowja'Changed in version 3.2: DeprecationWarning is now ignored by default in addition to PendingDeprecationWarning.'17:19
harlowjabut perhaps all thats needed is to use '-W ' correctly in tests17:20
bknudsonthe change in output is unrelated to warnings17:20
bknudsonit's debug output or something17:20
harlowjaya, those look like log warnings (not warnings.warnings ones)17:21
harlowjait doesn't look like the duplicate message handling is working (?)17:21
bknudson2015-06-05 01:36:50.653 |  WARNING [keystonemiddleware.auth_token] Authorization failed for token  -- these are just log.warnings17:22
harlowjaright17:22
bknudsonfor some reason these aren't printed during tox -e py27 when using testtools.TestCase17:22
harlowjaodd17:23
bknudsonso something in oslotest must be letting those through17:23
bknudsonthere might be some oslotest config I didn't do.17:23
harlowjaman my browser acting up, damn FF, lol17:23
harlowjahttps://github.com/openstack/oslotest/blob/master/oslotest/base.py#L116 ?17:24
harlowjamaybe something going on there?17:24
bknudsonI didn't try setting OS_LOG_CAPTURE17:25
harlowjaya, maybe try17:25
bknudsonseems not safe to change how the tests work based on env vars.17:25
* harlowja won't disagree with that17:26
harlowjaafaik https://github.com/openstack/keystone/blob/master/.testr.conf (and others set most of these)17:26
bknudsonthat's probably what I missed in keystoneclient17:27
bknudsonoops, keystonemiddleware17:27
harlowjapossibly17:27
harlowjabb17:27
*** harlowja has quit IRC17:27
*** harlowja has joined #openstack-oslo17:32
*** achanda has quit IRC17:34
*** rushiagr is now known as rushiagr_away17:40
*** achanda has joined #openstack-oslo17:40
*** _amrith_ is now known as amrith17:42
*** e0ne has joined #openstack-oslo17:48
*** sdake has joined #openstack-oslo17:50
*** zz_jgrimm is now known as jgrimm17:53
*** sdake_ has quit IRC17:54
*** sdake_ has joined #openstack-oslo17:56
*** achanda_ has joined #openstack-oslo17:59
*** sdake has quit IRC17:59
*** achanda has quit IRC18:01
harlowjabknudson hopefully adding that stuff makes it all work18:06
harlowja*if u are trying18:06
bknudsonit's on my list18:06
harlowjamaybe we should add oslotest docs for all that18:06
harlowjaor something18:06
harlowjaso the 'magic' is more known18:06
harlowjahttp://docs.openstack.org/developer/oslotest/ doesn't seem to mention it18:06
*** achanda has joined #openstack-oslo18:10
*** achanda_ has quit IRC18:10
*** sdake_ is now known as sdake18:10
* harlowja will seee if i can remember to add something18:11
harlowjalifeless if u get around can u re +2 https://review.openstack.org/#/c/183194/18:12
harlowjahad to rebase after another merge18:12
harlowjaif u don't mind18:12
*** achanda_ has joined #openstack-oslo18:18
*** achanda has quit IRC18:20
bknudsonI wanted to check my understanding of how rabbit ssl config works...18:20
bknudsonhttp://git.openstack.org/cgit/openstack/oslo.messaging/tree/oslo_messaging/_drivers/impl_rabbit.py#n55218:20
bknudsonaccording to that, looks like it's --insecure if you don't set ca_certs18:20
bknudson(where ca_certs is actually kombu_ssl_ca_certs18:21
bknudsonand --insecure means it doesn't verify server cert.18:21
harlowjaunsure, sileht or flaper87 may know18:23
bknudsonso, rather than using the system CA certs, it just accepts any cert the server presents18:23
*** cdent has quit IRC18:30
*** cdent has joined #openstack-oslo18:32
*** cdent has quit IRC18:32
*** mriedem is now known as mriedem_madmax18:35
*** mriedem_madmax has quit IRC18:35
*** achanda has joined #openstack-oslo18:38
*** sabari has quit IRC18:41
*** achanda_ has quit IRC18:41
*** ashleighfarnham has quit IRC18:42
*** ashleighfarnham has joined #openstack-oslo18:43
*** harlowja has quit IRC18:46
*** achanda_ has joined #openstack-oslo18:48
*** achanda has quit IRC18:49
*** harlowja has joined #openstack-oslo18:53
*** jraim has quit IRC18:54
*** zhiyan has quit IRC18:54
*** sabari has joined #openstack-oslo18:55
*** exploreshaifali has quit IRC18:58
*** achanda has joined #openstack-oslo19:00
*** achanda_ has quit IRC19:01
*** ihrachyshka has quit IRC19:02
openstackgerritJeremy Stanley proposed openstack/oslo.db: Switch from MySQL-python to PyMySQL  https://review.openstack.org/18439219:04
*** achanda has quit IRC19:04
fungiwhen zzzeek's around again, i know that's ^ going to need some guidance on what we want to do about the opportunistic tests for mysql-python and mysql-connector19:05
fungii started trying to rip them out, but it's one of those loose yarns that seems to unravel much of the sweater19:05
dims_fungi: ack will ping him19:06
dims_thanks!19:06
fungisure thing. i'm happy to keep poking at it given sufficient suggestions on tweaking/removing tests, though also equally happy to hand over the reigns19:07
fungier, reins19:07
*** sdake has quit IRC19:08
*** jaosorior has quit IRC19:12
dims_fungi: i need to sync up on this topic as well19:22
dims_harlowja: do you know if there's a replacement for cmp(dict1, dict2) in python3? found a bunch of those in nova19:22
harlowjasomething in https://github.com/testing-cabal/testtools/blob/master/testtools/matchers/_dict.py perhaps?19:23
harlowjahttps://github.com/testing-cabal/testtools/blob/master/testtools/matchers/_dict.py#L168 ?19:24
*** amrith is now known as _amrith_19:25
harlowjadims_^19:27
*** leakypipes has quit IRC19:34
dhellmanndims_: how are they used? can you just say == or != ?19:35
dhellmanndims_: I've noticed some of the other projects maintain an etherpad "whiteboard" with priority lists and team status info. I wonder if it would be useful for us to do something similar, with reviews associated with priorities for this cycle.19:36
*** e0ne has quit IRC19:39
*** zzzeek has joined #openstack-oslo19:41
*** amotoki has joined #openstack-oslo19:55
*** dims__ has joined #openstack-oslo19:57
harlowjadhellmann i like that idear19:58
*** dims_ has quit IRC20:00
*** boris-42 has quit IRC20:02
*** dougwig has quit IRC20:02
*** dims__ has quit IRC20:11
*** e0ne has joined #openstack-oslo20:16
*** kgiusti has quit IRC20:38
*** jraim has joined #openstack-oslo20:38
*** e0ne has quit IRC20:45
*** e0ne has joined #openstack-oslo20:48
*** jecarey has quit IRC20:49
*** dougwig has joined #openstack-oslo20:50
*** zhiyan has joined #openstack-oslo20:54
*** amotoki has quit IRC20:57
*** boris-42 has joined #openstack-oslo21:00
*** e0ne has quit IRC21:06
*** rpodolyaka1 has joined #openstack-oslo21:06
*** rpodolyaka1 has quit IRC21:09
*** rpodolyaka1 has joined #openstack-oslo21:11
*** rpodolyaka1 has quit IRC21:13
*** rpodolyaka1 has joined #openstack-oslo21:14
*** rpodolyaka1 has quit IRC21:17
*** zzzeek has quit IRC21:37
*** openstack has joined #openstack-oslo21:42
-cameron.freenode.net- [freenode-info] if you're at a conference and other people are having trouble connecting, please mention it to staff: http://freenode.net/faq.shtml#gettinghelp21:42
*** amotoki has joined #openstack-oslo21:44
*** stpierre has quit IRC21:50
*** Kennan2 has joined #openstack-oslo22:02
*** Kennan has quit IRC22:03
*** amotoki has quit IRC22:11
*** stevemar has quit IRC22:12
*** gordc has quit IRC22:29
openstackgerritJoshua Harlow proposed openstack/tooz: Ensure locks can not be created outside of the root file driver directory  https://review.openstack.org/18846722:36
*** openstackgerrit has quit IRC22:37
*** openstackgerrit has joined #openstack-oslo22:37
*** ashleighfarnham has quit IRC22:41
openstackgerritJoshua Harlow proposed openstack/futurist: Vastly improve the docs  https://review.openstack.org/18896022:41
openstackgerritJoshua Harlow proposed openstack/futurist: Vastly improve the docs  https://review.openstack.org/18896022:43
openstackgerritJoshua Harlow proposed openstack/automaton: Add a initial .gitreview file  https://review.openstack.org/18896122:45
openstackgerritJoshua Harlow proposed openstack/futurist: Caps for futurist in hacking  https://review.openstack.org/18896222:50
openstackgerritJoshua Harlow proposed openstack/automaton: Revamp repo to match openstack repos  https://review.openstack.org/18896122:55
openstackgerritJoshua Harlow proposed openstack/futurist: Capital letters for futurist in HACKING.rst  https://review.openstack.org/18896222:56
openstackgerritJoshua Harlow proposed openstack/automaton: Revamp repo to match openstack repos  https://review.openstack.org/18896123:02
openstackgerritJoshua Harlow proposed openstack/automaton: Revamp repo to match openstack repos  https://review.openstack.org/18896123:06
openstackgerritJoshua Harlow proposed openstack/automaton: Vastly improve the docs  https://review.openstack.org/18896823:14
harlowjaok those should be good to go (unless they fail CI, which i don't think they will)23:17
*** sdake has joined #openstack-oslo23:26
*** amotoki has joined #openstack-oslo23:53
*** sdake_ has joined #openstack-oslo23:57
openstackgerritJoshua Harlow proposed openstack/automaton: Revamp repo to match openstack repos  https://review.openstack.org/18896123:57

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