Tuesday, 2018-11-06

*** dangtrinhnt has joined #openstack-requirements01:32
*** hongbin has joined #openstack-requirements01:56
*** hongbin has quit IRC02:11
*** toabctl has quit IRC02:19
*** toabctl has joined #openstack-requirements02:23
*** hongbin has joined #openstack-requirements02:29
*** udesale has joined #openstack-requirements04:55
*** udesale has quit IRC04:58
*** udesale has joined #openstack-requirements04:58
*** udesale has quit IRC04:58
*** udesale has joined #openstack-requirements05:05
*** hongbin has quit IRC05:09
*** udesale has quit IRC05:40
*** udesale has joined #openstack-requirements05:53
openstackgerritTony Breeds proposed openstack/requirements master: update constraint for oslo.service to new release 1.32.1  https://review.openstack.org/61567606:00
openstackgerritMerged openstack/requirements master: update constraint for oslo.db to new release 4.42.0  https://review.openstack.org/61567806:08
openstackgerritOpenStack Proposal Bot proposed openstack/requirements master: Updated from generate-constraints  https://review.openstack.org/61573106:12
openstackgerritMerged openstack/requirements master: update constraint for oslo.messaging to new release 9.2.0  https://review.openstack.org/61566806:15
openstackgerritMerged openstack/requirements master: update constraint for oslo.policy to new release 1.41.0  https://review.openstack.org/61567006:15
openstackgerritMerged openstack/requirements master: update constraint for osprofiler to new release 2.5.1  https://review.openstack.org/61567306:15
openstackgerritMerged openstack/requirements master: update constraint for sphinx-feature-classification to new release 0.3.1  https://review.openstack.org/61567406:15
openstackgerritMerged openstack/requirements master: update constraint for futurist to new release 1.8.0  https://review.openstack.org/61567506:18
openstackgerritMerged openstack/requirements master: update constraint for oslo.upgradecheck to new release 0.1.1  https://review.openstack.org/61567906:18
*** e0ne has joined #openstack-requirements06:24
openstackgerritMerged openstack/requirements master: update constraint for pbr to new release 5.1.1  https://review.openstack.org/61567206:31
openstackgerritMerged openstack/requirements master: update constraint for oslo.config to new release 6.7.0  https://review.openstack.org/61566906:31
openstackgerritMerged openstack/requirements master: update constraint for python-freezerclient to new release 2.0.0  https://review.openstack.org/61565206:31
*** e0ne has quit IRC06:44
*** e0ne has joined #openstack-requirements06:48
*** udesale has quit IRC06:54
*** e0ne has quit IRC07:07
openstackgerritMerged openstack/requirements master: Add monasca-analytics to projects.txt  https://review.openstack.org/61555507:21
*** udesale has joined #openstack-requirements07:35
*** ccamacho has joined #openstack-requirements08:03
*** jpich has joined #openstack-requirements08:57
*** e0ne has joined #openstack-requirements11:11
*** dtantsur|afk is now known as dtantsur11:33
*** e0ne has quit IRC12:29
*** e0ne has joined #openstack-requirements12:43
*** zul has joined #openstack-requirements13:46
openstackgerritOpenStack Proposal Bot proposed openstack/requirements master: update constraint for neutron-lib to new release 1.20.0  https://review.openstack.org/61589414:45
*** e0ne has quit IRC15:06
openstackgerritMatthew Thode proposed openstack/requirements master: Updated from generate-constraints  https://review.openstack.org/61573115:47
prometheanfiredhellmann: you know much about the xfails stuff?  it seems to me that it checks the dependency===1.2.3 is co-defined with the caller of the dependency.  What I think I'd like recorded is the bad version of the caller (since it's typically capping something) and the version of the dep known to fail.15:57
dhellmannI don't know what xfails is15:58
dhellmannis that a job/tool in the requirements repo?15:58
prometheanfireya, but it's not been used in a while16:01
prometheanfirethink tony made it16:01
dhellmannyeah, I don't know anything about that :-/16:02
prometheanfirebasically, I'm tired of holding back opentracing and now salt :P16:02
prometheanfireI could add exclusions to g-r but that doesn't seem right16:02
prometheanfireupstream is slow to move to resolve their caps16:03
prometheanfireat least openshift was somewhat quick to update their allowable kubernetes version16:03
dhellmannso opentracing and salt have caps on some of their dependencies that are lower than the versions we use?16:05
prometheanfirenot quite16:06
prometheanfirejaegerclient has a cap that doesn't allow opentracing 2.0.0 https://github.com/jaegertracing/jaeger-client-python/issues/199 https://github.com/jaegertracing/jaeger-client-python/pull/20616:07
prometheanfiresalt is an odd one, it fails validation even though it shouldn't :|16:07
prometheanfirehttp://logs.openstack.org/31/615731/1/check/requirements-tox-py27-check-uc/3712d13/job-output.txt.gz#_2018-11-06_06_35_48_24957416:09
prometheanfirehttps://github.com/saltstack/salt/blob/2018.3.3/requirements/base.txt#L816:09
dhellmanntornado 5.1.1 is > the max of 5.0 there16:10
prometheanfirebut the version defined in their reqs file is 6.0 as the cap16:10
prometheanfirefor py2.716:11
dhellmannis that job running under python 3?16:16
dhellmannthe venv name implies it is not16:16
prometheanfirethe tox job itself is defined as py2716:17
dhellmannand the tox config looks like it sets basepython properly16:18
dhellmannso maybe it's a bug in the check script16:18
prometheanfiremaybe, will have to check, just something I've noticed16:19
*** ccamacho has quit IRC16:27
*** udesale has quit IRC16:32
openstackgerritBen Nemec proposed openstack/requirements master: Exclude oslo.cache 1.31.1  https://review.openstack.org/61593516:35
*** andymccr has quit IRC16:36
openstackgerritMatthew Thode proposed openstack/requirements master: update tornado  https://review.openstack.org/61594016:43
openstackgerritBen Nemec proposed openstack/requirements master: Exclude oslo.cache 1.31.1  https://review.openstack.org/61593516:45
prometheanfiretonyb: ping, bugging you about constraints publishing again :D16:50
prometheanfireI think we need to set recreate=True for the uc checks (since it doesn't seem to update if something is already installed17:12
prometheanfirethat or change pip install to include -I17:12
prometheanfirethat or change pip install to include -U17:12
prometheanfirewhich it has, odd17:12
prometheanfirealso, we should remove basepython17:14
prometheanfireHowever, if ignore_basepython_conflict is set, the value is ignored and we force the basepython implied from the factor name.17:14
*** ccamacho has joined #openstack-requirements17:22
prometheanfiredhellmann: so.. change the value of basepytohn within testenv and the output changes :D17:30
*** e0ne has joined #openstack-requirements17:32
*** ccamacho has quit IRC17:33
*** jpich has quit IRC17:34
prometheanfirehttps://github.com/tox-dev/tox/issues/477 I think17:36
prometheanfiretonyb: basepython stuff again17:36
prometheanfireprobably need to set envdir separate for each python17:37
dhellmannthe dir should be different by default unless we're explicitly sharing them17:37
prometheanfireok17:40
dhellmannit defaults to .tox/$envname right?17:40
*** e0ne has quit IRC18:03
*** dtantsur is now known as dtantsur|afk18:06
*** e0ne has joined #openstack-requirements18:06
*** e0ne has quit IRC18:24
prometheanfiretrue18:37
prometheanfireI think maybe check_conflicts just takes the last value in the list to check or something18:55
prometheanfirecat .tox/py27-check-uc/lib/python2.7/site-packages/salt-2018.3.3.dist-info/METADATA19:42
prometheanfirehas tornado twice19:42
prometheanfireso that's no good19:42
tonybprometheanfire: that isn't a problem for us but it probably is for nova that are using the envdir stuff.  I'll go poke around19:45
prometheanfireya19:46
prometheanfiretonyb: it looks like it's salt's fault (what I'm looking at at least19:46
prometheanfireRequirement already satisfied: tornado<6.0,>=4.2.1 in ./.tox/py27-check-uc/lib/python2.7/site-packages (from salt) (5.1.1)19:46
prometheanfiresalt 2018.3.3 has requirement tornado<5.0,>=4.2.1, but you'll have tornado 5.1.1 which is incompatible.19:46
prometheanfirepip install salt with python2.7 with tornado already updated to 5.1.1 should fail19:46
prometheanfirehttps://github.com/saltstack/salt/blob/2018.3.3/requirements/base.txt#L8-L9 doesn't seem to be obeyed19:46
tonybprometheanfire: Ok19:48
prometheanfirethey have their own custom requirements.txt parser19:50
prometheanfiresetup.py is 1k lines long :D19:56
prometheanfirecan we get a second person looking at https://review.openstack.org/615935 ?21:41
*** efried has joined #openstack-requirements21:42
efriedmordred: Is there going to be a bot or other effort to percolate this https://review.openstack.org/#/c/615441/ to projects importing monotonic?21:43
mordredI didn't do it21:43
efriedI think it's not possible to update requirements on such a project (thereby triggering the requirements-check job) without doing that first.21:43
efriedI'm about to do it for oslo.service, just wanted to make sure I didn't stomp on something a bot was gonna do.21:44
mordredefried: no bot updates in work ... I think doing it by hand is fine21:45
efriedack, review coming atcha :P21:45
mordredefried: although now that you mention it - I probablyshoudl follow up and do that more broadly21:45
efried"blah blah blah, I'm a bad person, blah blah blah"21:46
efried<kisses>21:46
*** dangtrinhnt has quit IRC22:01
*** dangtrinhnt has joined #openstack-requirements22:02
openstackgerritMerged openstack/requirements master: Updated from generate-constraints  https://review.openstack.org/61573123:11
*** vpickard is now known as vpickard_23:25
efriedbnemec: Sorry, I'm pretty confused about https://review.openstack.org/#/c/616013/ -- how does l-c work with a py version restriction like this?23:39
bnemecefried: I think it should look like: monotonic>=0.6;python_version<'3.3'23:41
bnemecWhich would mean that on python versions where it needs to be installed, it requires at least 0.6.23:41
efriedbnemec: okay, I think that makes sense.23:42
* efried tries23:42
efriedbnemec: was going to say: so we can't restrict the requirements.txt version to <py3 because that effectively removes the lower bound for py3, which conflicts with l-c; but we can't drop the requirement from l-c because then we would be unrestricted for py2...23:44
efriedI hope that's not the case...23:44
bnemecI guess we'll find out when zuul reports in. :-)23:46

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