Wednesday, 2018-07-18

tonybprometheanfire: the mitmproxy thiing happend because our XFAILS stuff is buggy00:11
tonybmanjeets: I'll need to read the logs etc and that's a complex issue :/00:12
*** tosky has quit IRC00:12
manjeetshttp://logs.openstack.org/15/579915/16/check/requirements-check/15c3826/job-output.txt.gz#_2018-07-17_18_08_16_94076200:12
manjeetstonyb, is there a way to add exception for packages in requirements.txt00:13
manjeets?00:13
tonybmanjeets: No00:13
manjeetstonyb, https://review.openstack.org/#/c/579915/ this is the patch00:13
tonybmanjeets: Like I said it's complex00:13
tonybmanjeets: Thanks00:13
manjeetsI cherry picked some changes to stable/queens to fix the gate00:13
tonybmanjeets: Okay I suspect that you just need to deal with the conflicts00:15
manjeetstonyb, sorry I didn't get that ? what conflicts ?00:15
tonybmanjeets: I think on stable/queens you need to leave the tox_install stuff in place so it isn't an actual Conflict in git terms but it is in functaionality chnages00:16
tonybmanjeets: but it's all very confusing00:16
tonybmanjeets: Yup I *think* if you leave the tox_install.sh stuff in place and remove the chnages to requirements.txt things will work as expected00:28
manjeetstonyb, I tried that earlier it failed almost all jobs, but i'll looking at it, will try again00:28
manjeetsim looking at it**00:28
manjeetstonyb, thanks00:28
tonybmanjeets: Can you tell me which PS does it that way?00:29
manjeetstonyb, https://review.openstack.org/#/c/576110/ PS 800:30
manjeetsI think if i just cherry-pick stestr stuff and leave tox_install that may work00:30
manjeetsI just looked at the logs mostly complaining stestr00:30
tonybmanjeets: Okay that doesn't really make sense but it's worth a try00:32
tonybmanjeets: PS8 got a +1 from Zuul but you said it failed almost all the jobs00:32
tonybmanjeets: are you sure PS8 is the right one?00:32
manjeetstonyb, there are rechecks at PS800:32
manjeetsit broke after it got w +100:33
manjeetshttp://logs.openstack.org/10/576110/8/check/networking-odl-fullstack-nitrogen/f05fa85/00:33
tonybOh I see in the gate pipeline00:33
manjeetstonyb, from ps8 recheck http://logs.openstack.org/10/576110/8/check/networking-odl-fullstack-nitrogen/f05fa85/job-output.txt.gz#_2018-07-02_11_23_58_67649600:34
manjeetsthat's why i thought i'd just cherry-pick stestr change00:34
tonybmanjeets: stestr isn't the problem00:35
tonybhttp://logs.openstack.org/10/576110/8/gate/openstack-tox-pep8/c50d9de/job-output.txt.gz#_2018-06-27_13_26_49_85788200:35
manjeetstonyb, its very complicated we are looking at logs of different projects00:35
manjeetsdifferent jobs**00:35
manjeetsnot projects00:35
tonybmanjeets: Sure but if pep8 fails then devstack will aswell00:36
manjeetstonyb, http://logs.openstack.org/10/576110/8/gate/openstack-tox-pep8/c50d9de/job-output.txt.gz#_2018-06-27_13_26_49_858071 this looks like constraint issue00:37
manjeetshow else I add a constraint for a url00:37
manjeetstox_install_project uses url00:38
tonybmanjeets: Let me work through it00:38
tonybmanjeets: 'Revert "add neutron-lbaas to global-requirements"' I5d58f036feee80a5cf9e2a252a3ff3b2b803cd37 was merged between the runs through the check and gate pipelines00:40
manjeetstonyb, so revert a revert ?00:40
tonybmanjeets: so I think PS8 + a small chnage to reflect that will fix you00:40
tonybmanjeets: No that patch is correct00:41
manjeetsbut stestr issue is also there in other job http://logs.openstack.org/10/576110/8/check/networking-odl-fullstack-nitrogen/f05fa85/job-output.txt.gz#_2018-07-02_11_23_58_67649600:42
tonybmanjeets: one problem at a time please00:42
tonybmanjeets: I'm very sure that PS 8 is correct and it failed because it ran after I51e0902215b21abffb39d17daf780b419d55ceea was merged which was wrong.00:50
tonybmanjeets: I think the stestr failure is a side effect of the code not being installable and therefore no tests could run so there wasn't a .testr directory00:52
tonybmanjeets: Can you restor PS8 and try again to see what the gate says now?00:52
manjeetstonyb, I refactored to 800:53
tonybmanjeets: okay00:53
manjeetswait it restored workflow +100:54
manjeetstonyb, thanks for help, I am heading out will check gate results later00:54
manjeetstonyb, have a good night00:54
tonybmanjeets: I'll keep an eye on it during my day00:55
tonybmanjeets: Have a good evening00:55
prometheanfiretonyb: how's it going?01:13
tonybprometheanfire: about as well as can be expected you?01:14
prometheanfireok01:15
prometheanfiretonyb: pypi mirror seem slow today?01:15
tonybprometheanfire: not so as I'd noticed?01:16
prometheanfirebunch of no-distro-found stuff recently01:17
prometheanfirethat's all01:17
tonybprometheanfire: Hmm strange01:22
tonybprometheanfire: ask in #infra to see if bandersnaatch has wedged?  esp if you can see $library on pypi but not in $mirror01:22
prometheanfirek, I will if this fails one last time01:23
tonybprometheanfire: okay01:28
*** number80 has quit IRC01:45
*** number80 has joined #openstack-requirements01:49
*** hongbin has joined #openstack-requirements01:57
*** udesale has joined #openstack-requirements03:24
*** hongbin has quit IRC03:49
*** udesale has quit IRC04:55
*** udesale has joined #openstack-requirements04:55
*** adrianreza has quit IRC04:58
*** openstackgerrit has quit IRC05:10
*** bauzas has quit IRC05:16
*** robcresswell has quit IRC05:16
*** mwhahaha has quit IRC05:16
*** johnsom has quit IRC05:16
*** coreycb has quit IRC05:16
*** jmccrory has quit IRC05:16
*** toabctl has quit IRC05:18
*** toabctl has joined #openstack-requirements05:21
*** bauzas has joined #openstack-requirements05:35
*** robcresswell has joined #openstack-requirements05:35
*** mwhahaha has joined #openstack-requirements05:35
*** johnsom has joined #openstack-requirements05:35
*** coreycb has joined #openstack-requirements05:35
*** jmccrory has joined #openstack-requirements05:35
*** florianf has joined #openstack-requirements06:50
*** ccamacho has joined #openstack-requirements07:08
prometheanfirefyi, gate is wedges, infra knows07:33
*** tosky has joined #openstack-requirements08:06
*** jpich has joined #openstack-requirements08:13
*** dtantsur|afk is now known as dtantsur09:20
*** dmellado has quit IRC10:36
*** dmellado has joined #openstack-requirements10:42
*** witek has quit IRC11:32
*** boden has joined #openstack-requirements11:49
*** edmondsw has joined #openstack-requirements12:11
*** openstackgerrit has joined #openstack-requirements12:32
openstackgerritMonty Taylor proposed openstack/requirements master: DNM testing pypi mirror fix  https://review.openstack.org/58356112:32
*** lbragstad has quit IRC13:19
*** lbragstad has joined #openstack-requirements13:46
openstackgerritOpenStack Proposal Bot proposed openstack/requirements master: update constraint for os-brick to new release 2.5.3  https://review.openstack.org/58358514:09
*** udesale_ has joined #openstack-requirements14:26
*** udesale has quit IRC14:27
*** rpioso|afk is now known as rpioso15:20
openstackgerritMartin CAMEY proposed openstack/requirements master: update constraint for python-monascaclient to new release 1.12.0  https://review.openstack.org/58328115:25
*** lbragstad has quit IRC16:02
*** udesale_ has quit IRC16:13
*** udesale has joined #openstack-requirements16:13
*** udesale has quit IRC16:18
*** florianf has quit IRC16:31
*** jpich has quit IRC16:45
*** lbragstad has joined #openstack-requirements16:50
*** dtantsur is now known as dtantsur|afk17:26
smcginnisprometheanfire: The google driver fix has merged.17:51
prometheanfirewoo, now for gate to unwedge17:51
smcginnisI hope that is soon.17:51
manjeetstonyb, hi18:02
manjeetsI think neutron-lbaas issue is gone, now python 3 requirement is killing it18:02
manjeetsI think the reason is >=1.7.2 for pylint and from upper-constraints.txt it gets 2.0.0 which has a python 3 check so I revised a patch to force 1.7.218:03
prometheanfiremanjeets: just update to 1.7.x (whatever the latest in that series is)18:06
manjeetsprometheanfire, you mean have == 1.7.x instead of >=1.7.x ?18:06
prometheanfiremanjeets: I don't see pylint in https://github.com/openstack/neutron-lbaas/blob/master/test-requirements.txt18:08
manjeetshttp://logs.openstack.org/10/576110/11/check/openstack-tox-pep8/18e9ea4/job-output.txt.gz#_2018-07-18_01_48_11_03172518:08
manjeetsprometheanfire, its networking-odl which had dependency on neutron-lbaas18:08
manjeetsprometheanfire, https://review.openstack.org/#/c/576110/11/test-requirements.txt18:09
manjeetstonyb update it to 1.7.6 but for some reason it gets 2.0.018:09
manjeetshttp://logs.openstack.org/10/576110/11/check/openstack-tox-pep8/18e9ea4/job-output.txt.gz#_2018-07-18_01_48_11_03172518:09
manjeetsand crash saying needs python >=3.518:09
prometheanfiremanjeets: ah, that's because it's unconstrained, if it was ==1.7.6 that'd work18:10
prometheanfireIt should be >=1.7.6<2.0.018:10
prometheanfireor something18:10
manjeetsprometheanfire, ok, i'll wait for run if this passes i'll change18:11
manjeetsand pylint has dependency on astroid, which will be next reason for same type of failure so I forced both pylint and astroid18:11
prometheanfirejust cap pylint18:13
prometheanfirethat'll fix astroid as well18:13
*** boden has quit IRC20:06
edmondswu-c currently has greenlet capped at 0.4.13, so no issue... but for anyone interested in bumping that, see https://github.com/python-greenlet/greenlet/issues/13620:07
dhellmannprometheanfire : does the u-c list support comments? I wonder if we want edmondsw to add one with that bug report ^^20:14
prometheanfiredhellmann: it's auto-generated, so not sure, it's worth testing though20:27
dhellmannprometheanfire : yeah, that's what I was afraid of20:28
prometheanfire#startmeeting requirements20:28
openstackMeeting started Wed Jul 18 20:28:23 2018 UTC and is due to finish in 60 minutes.  The chair is prometheanfire. Information about MeetBot at http://wiki.debian.org/MeetBot.20:28
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.20:28
*** openstack changes topic to " (Meeting topic: requirements)"20:28
openstackThe meeting name has been set to 'requirements'20:28
prometheanfire#topic rollcall20:28
*** openstack changes topic to "rollcall (Meeting topic: requirements)"20:28
prometheanfiretonyb, prometheanfire, number80, dirk, coolsvap, toabctl, smcginnis, dhellmann ping20:28
prometheanfireo/20:28
dhellmanno/20:28
prometheanfiredirk said he couldn't be here iirc20:28
smcginniso/20:30
prometheanfiregonna wait a couple min for tony if able20:31
tonyb\o20:32
* tonyb wonders if Octonauts references would work with this group?20:32
* dhellmann googles octonauts20:33
* prometheanfire googles octonauts20:33
prometheanfirethat the switch thing?20:33
tonybthat was pretty much what I thought :(20:33
tonybIt's a kids TV show20:33
smcginnisI'm well past that stage. :)20:33
tonybanyway let's do this meeting thing ;P20:33
dhellmannso, nothing to do with october20:33
prometheanfire#topic Any controversies in the Queue?20:34
*** openstack changes topic to "Any controversies in the Queue? (Meeting topic: requirements)"20:34
smcginnisIs it being broken controversial?20:34
prometheanfirelol20:34
dhellmannis the pypi mirror still causing trouble, or is there something else?20:34
prometheanfirejust the mirror, ya20:34
tonybhehe I dont' see any controversies, but clearly it's broken and we wanted to talk about post releases20:35
prometheanfireok20:35
prometheanfire#topic brokenness20:35
*** openstack changes topic to "brokenness (Meeting topic: requirements)"20:35
tonybprometheanfire: are infra on it? or should I monitor that during my day20:35
prometheanfirethey are20:35
smcginnisThere's a patch in gate right now to fix it.20:35
tonyb\o/20:35
smcginnisOr at least work around it for now.20:36
prometheanfirejust pinged mordred about it20:36
prometheanfirestill bad20:36
smcginnisOh, looks like the one they hoped would get around it merged: https://review.openstack.org/#/c/583571/20:36
tonybAhh okay, that kind of broken I thought it was just the normal bindersnatch thing20:36
prometheanfireanyway, once it's fixed we can update the uc on networkx and the two google libs20:36
tonybis there a 30sec summary of the problem?20:37
prometheanfirethey ran out of space20:37
tonybOh okay  that's well less that 30secs20:37
prometheanfiresaid it'll be fixed in 15 minutes or so20:37
smcginnisTaskflow uploads ~500m of packages nightly. Mirroring locally got too big.20:37
smcginnisDarn storage.20:37
dhellmannI guess we need a bandersnatch->swift converter20:37
smcginnisI saw some discussion of that.20:37
prometheanfire500M for taskflow?20:37
smcginnisprometheanfire: Yep20:37
tonybsmcginnis: Really? what are they uploading?20:38
prometheanfirewow20:38
smcginnisThe world?20:38
dhellmannwhat on earth20:38
smcginnisI guess some of the ML stuff is pretty big for some reason.20:38
tonybdhellmann: I dont' think so I think that the mirrors are staycing on AFS it's only logs that are moving20:38
dhellmanntonyb : yeah, I meant for the future20:38
prometheanfireanyway, moving on then20:38
prometheanfire#topic freeze20:38
*** openstack changes topic to "freeze (Meeting topic: requirements)"20:39
dhellmannsmcginnis : tensorflow?20:39
prometheanfireI'll need to find more mr freeze puns, maybe rewatch batman & robin20:39
smcginnisOh, sorry. Yes, tensorflow.20:39
prometheanfirethe things I suffer for you20:39
dhellmannok, whew.20:39
tonybsmcginnis, dhellmann: Oh that makes away mmore sense!20:39
smcginnisprometheanfire: :D20:39
dhellmannprometheanfire : I hear they're rebooting the iceman comics20:40
tonybthe earth stops shaking ;P20:40
prometheanfiredhellmann: :D20:40
smcginnisHeh, sorry. That would be really bad if taskflow was that big.20:40
prometheanfirethis freeze should be easier because of the per-project reqs20:40
dhellmannwell, we could at least do something about that :-)20:40
tonybWith the freeze and pre-project requirements we need to think a little about minimum bumping20:40
prometheanfirethis is still the process https://etherpad.openstack.org/p/requirements-cycle-process20:41
tonybin that say (bad example) oslo.privsep adds a new API/constant today and it merges and is released next week at what point can python-swiftclient bump the minimum to require that (for them)?20:41
tonybwhat about say $clientlibrary that is pulled into python-openstackclient?20:42
dhellmannas long as the u-c list isn't changed, does it matter?20:42
prometheanfirethey could bump it immediately, as long as their min is not over our UC20:42
prometheanfirepackagers would need to look at swifts lower-constraints to find swifts min20:43
tonybdhellmann: I'm not sure, which is why I'm asking ;P  I feel like if python-openstackclient took bumped a minimum that kinda of implies that they'd like a release and uc bump20:44
tonybwhich I guess will all come out in the exception proecess20:44
tonybI just wanted to discuss it ahead of time20:44
dhellmannsure20:44
prometheanfireso you want to make sure that their reqs are in any given release?20:44
dhellmannI'm also making sure I'm not missing something :-)20:44
tonybprometheanfire: Yup and we have dhellmann build tool to make life slightly easier for packagers to work that out20:45
dhellmannI do think if we end up needing a release of a library for a bug fix, we need to coordinate the u-c update ahead of time. But I think we generally do that in this period of the cycle anyway, right?20:45
prometheanfiretonyb: ya, you talking about the global-lc.txt builder?20:45
dhellmannwe don't want to have a case where we release a library and then don't allow the u-c update, because then we have a thing out in the wild that we're not using in our own tests20:45
tonybprometheanfire: Yup20:45
prometheanfireok, anything else for now about the freeze?20:46
tonybdhellmann: Yup I agree and I guess without the bot updates a release is less impactful in that only projects that are actually impacted by the bug need to update20:46
tonyband if a project works that out after the fact the fixed version shoudl be available20:47
dhellmanntonyb : ideally we wouldn't update minimums just for bug fixes, but yeah20:47
tonybdhellmann: true, but it does happen esp when a bug fix changes an API (by say adding a new kwarg)20:48
prometheanfireyarp20:48
dhellmanntonyb : sure20:48
tonybit may be I'm over thinking ia and worrying too much due to not enough coffee20:48
dhellmannnah, it's good to review this stuff20:49
prometheanfireya, just in case20:49
dhellmannmaybe we should write the reasoning down so we don't have to think so hard next time :-)20:49
prometheanfiredhellmann: formalizing the release process for reqs would be nice20:50
tonybdhellmann: good plan20:50
prometheanfireturning https://etherpad.openstack.org/p/requirements-cycle-process more official20:50
dhellmannyeah, that made a big difference in our confidence on the release team20:50
tonybprometheanfire: want to add something to the end of that etherpad20:50
prometheanfiretonyb: go ahead?20:50
dhellmannwe have a rst file in the releases repo now; that etherpad could move over to the requirements repo eventually20:50
tonybprometheanfire: +1 having some process docs in repo (like releases) would be good20:50
tonybdhellmann: snap :_20:50
smcginnisThat might be a good place for that.20:51
dhellmannmaybe that's a project for stein20:51
tonybprometheanfire: I mean *can you* add something to the end of that etherpad (or PROCESS.rst)20:51
prometheanfiretonyb: of course, it's just a review away20:52
tonybdhellmann: I feel like we can start now.  it has no material impact on the release20:52
tonybprometheanfire: cool20:52
dhellmannoh, sure, I just meant that we could be deliberate about updating it throughout the cycle at different points where the rules change or whatever20:52
prometheanfire#topic open floor20:52
*** openstack changes topic to "open floor (Meeting topic: requirements)"20:52
tonybso we have 8mins left do we want to discuss post releases in general?20:52
tonyband pyldap specifically?20:53
dhellmanndo we have any topics lined up to discuss at the ptg?20:53
dhellmannoh, sure, that's more important, let's do that20:53
prometheanfiretonyb: sure20:53
prometheanfiredhellmann: I think I'll start thinking about ptg next week (after freeze)20:53
dhellmannmakes sense20:53
* tonyb wont be at the PTG but if y'all want to hangouts me into anything I can be available pening TZs20:53
dhellmannaw!20:53
prometheanfiretonyb: but you'll miss the choo choo puting you to sleep20:54
smcginnisThat's unfortunate.20:54
tonybdhellmann, smcginnis: goes for rleases to20:54
prometheanfiretonyb: so, post release?20:54
dhellmannyeah, we'll keep that in mind20:54
tonybso post releases20:54
smcginnistonyb: Thanks. If we have some topics we'll try to find a convenient time.20:54
dhellmannso, what's the deal with post releases? why are we worried about them?20:54
tonybI think they got lumped with pre releases and theer was some unreasonable FUD about accepting them20:54
dhellmannah, ok20:55
tonybI think we shoudl at a minimum evealuate each, if not just accept them20:55
dhellmanniirc, the only reason we don't like pre-releases is that pip needs special instructions to install them20:55
dhellmanndoes that apply to post releases?20:55
prometheanfireoh, those .post releases20:55
tonyband pyldap is a trivial one to accept as it's litterally the same code as 3.0.020:55
prometheanfireI think we should just accept them20:55
prometheanfirewe don't need to disable pre-releases because they are already disabled by default20:56
prometheanfirethat would make my review not needed20:56
tonybdhellmann: I thought there was more it it than that in that there is a perception that they're more risky20:56
dhellmannI guess I don't understand that perception20:56
tonybput perhaps that's linked to pre releases of $major bumps20:57
dhellmannif the same package was tagged with a new version number we wouldn't even behaving the conversation, right?20:57
prometheanfiredoesn't debian have something like that?20:57
prometheanfire1.2.3-220:57
prometheanfiregentoo has 1.2.3-r2 for instance20:57
prometheanfireit's the same concept20:57
tonybdhellmann: that's true20:57
prometheanfirethis is a question of if we allow revision bumps, I can't see a reason why20:57
prometheanfires/why/why not20:57
dhellmannperhaps we should treat them like any other update, and let the test jobs evaluate them on a case-by-case basis20:57
tonybI guess some of it came from before we had the cross-project gateing we have now20:58
dhellmannhmm20:58
prometheanfireso, everyone fine with just allowing them? if so I'll drop my review20:58
dhellmann+1 for allowing them20:58
tonybprometheanfire: for varying values of fine ;P20:58
dhellmannat least until things blow up in our face, I guess :-)20:59
tonybbut yeah I think I'm good with it20:59
prometheanfiresgtm20:59
tonybdhellmann: at least a u-c (partial) revert is easy20:59
dhellmannyeah20:59
tonyb.pre/.post releases for EVERYBODY ;p21:00
prometheanfiretonyb: anything else?21:00
tonybprometheanfire: I don't think so21:00
prometheanfiretonyb: I don't think pre-releases are good, but those have to be manually proposed anyway21:00
tonybprometheanfire: not all of them21:00
prometheanfireok, going to endmeeting21:00
prometheanfire#endmeeting21:00
*** openstack changes topic to "OpenStack Requirements - IRC meetngs on Wednesdays @ 07:00 UTC in here in #openstack-requirements - See agenda @ http://tinyurl.com/h44ryuw - IRC channel is *LOGGED* @ http://tinyurl.com/j38rk24"21:00
openstackMeeting ended Wed Jul 18 21:00:54 2018 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)21:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/requirements/2018/requirements.2018-07-18-20.28.html21:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/requirements/2018/requirements.2018-07-18-20.28.txt21:00
openstackLog:            http://eavesdrop.openstack.org/meetings/requirements/2018/requirements.2018-07-18-20.28.log.html21:00
prometheanfiretonyb: they don't?21:01
tonybprometheanfire: the bot will propose them sometimes21:01
tonybprometheanfire: and I don't know why21:01
prometheanfireah, ok21:01
tonybprometheanfire: I've seen the bot suggest them21:01
tonybmanjeets: I'll look after breakfast21:08
prometheanfirerechecked allthethings21:29
*** edmondsw has quit IRC21:54
*** lbragstad has quit IRC22:29
tonybmanjeets: Ohh I see what's going on, yeah we need to use pylint== not pylint>=  which you've done23:13
tonybmanjeets: if you can get one neutron-stable-core to +2 it I can +2+W it.23:14
prometheanfiretonyb: >= can work with a cap as well23:17
tonybprometheanfire: Sure but that seems more problematic than use using ==23:19
tonybif we had pylint in u-c then sure we shoudl use >= but we don't23:19
prometheanfiremeh, your choice23:19
*** tosky has quit IRC23:20
tonybprometheanfire: I thought we'd worked out that caps are bad23:20
tonybprometheanfire: anyway it isn't worth discussin anymore23:20
prometheanfirewe did, but we don't do anything with pylint, so that's your problem :P23:20
*** rpioso is now known as rpioso|afk23:48

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