Sunday, 2013-09-29

*** ericw has joined #openstack-infra00:00
*** boris-42 has quit IRC00:02
*** ericw has quit IRC00:02
*** UtahDave has joined #openstack-infra00:11
*** torgomatic has quit IRC00:22
*** CaptTofu has joined #openstack-infra00:22
*** torgomatic has joined #openstack-infra00:23
*** ericw has joined #openstack-infra00:25
*** dims has joined #openstack-infra00:28
*** CaptTofu has quit IRC00:34
*** ericw has quit IRC00:37
*** CaptTofu has joined #openstack-infra00:51
*** UtahDave has quit IRC00:54
pabelangermordred, odd, looks like saltstack removed your patch https://github.com/emonty/salt/commit/3867ffb3efff2df97b4bb82b9fb2afa703786a4700:55
pabelangerhere is the revert: https://github.com/saltstack/salt/pull/393300:55
pabelangernot sure why, but trying to get it merged back in00:55
pabelangersince I am hitting the same m2crypto issue00:56
*** xchu has joined #openstack-infra00:59
morganfainbergpabelanger, iirc there were a couple things that pycrypto at the time couldn't do01:13
morganfainbergpabelanger, i _think_ they plan on getting rid of m2crypto soon(ish) again.01:14
morganfainbergpabelanger, i asked about this recently because i was trying to deploy saltstack on a venv on ubuntu01:15
pabelangermorganfainberg, Ya, the same. I am trying to add floating ip support to salt-cloud.  Ended up hacking round the issue with tox and a forked repo on github01:16
pabelangerAdded -e git+https://github.com/ametaireau/M2Crypto#egg=M2Crypto-0.21.1 to my requirements.txt file01:17
morganfainbergpabelanger, yeah01:17
fungiick01:20
*** dims has quit IRC01:31
*** dcramer_ has quit IRC01:32
*** cody-somerville has joined #openstack-infra01:51
mordredpabelanger: http://tarballs.openstack.org/nova/M2Crypto-0.21.2.tar.gz02:01
pabelangermordred, Nice, thanks02:02
mordredpabelanger: there's the patched version of M2Crypto we used in OpenStack before we were able to get off of it02:02
*** CaptTofu has quit IRC02:02
*** boris-42 has joined #openstack-infra02:03
*** thomasm has joined #openstack-infra02:03
mordredfungi, clarkb: around?02:07
clarkbish. just arrived in portland on my way to bend02:08
clarkbthe weather hates me02:08
mordredclarkb: small change: https://review.openstack.org/#/c/48805/ - any objection to me ninja-ing it?02:09
mordredclarkb: enjoy bend btw!02:10
*** guohliu has quit IRC02:11
clarkbmordred no oppisition from me. do tou need a nodepool scripts in config update too?02:11
mordredclarkb: do ?02:11
mordreddo I?02:11
* mordred goes to look02:12
*** CaptTofu has joined #openstack-infra02:12
clarkbmordred: for caching02:12
mordredclarkb: eventually, just getting it in to d-g though will at least get it on the node before the job starts02:12
mordredthanks for reminding me though02:12
openstackgerritMonty Taylor proposed a change to openstack-infra/config: Add pypi-mirror to the devstack-gate cache list  https://review.openstack.org/4881202:14
*** CaptTofu has quit IRC02:17
openstackgerritA change was merged to openstack-infra/config: Add pypi-mirror to the devstack-gate cache list  https://review.openstack.org/4881202:17
openstackgerritMonty Taylor proposed a change to openstack-infra/devstack-gate: Use select-mirror in devstack-gate  https://review.openstack.org/4806402:21
*** wchrisj_ has joined #openstack-infra02:27
*** thomasm has quit IRC02:32
*** thomasm has joined #openstack-infra02:35
*** thomasm has quit IRC02:52
*** mrda has joined #openstack-infra03:07
*** guohliu has joined #openstack-infra03:18
*** alexpilotti has quit IRC03:21
*** mordredtest has joined #openstack-infra03:22
mordredtestok. this is really weird03:22
mordredtestthunderbird has grown IRC support03:22
mordredtestand twitter03:22
mordredtestand XMPP03:22
morganfainbergmordredtest, it … wha?03:22
mordredtestyeah03:22
mordredtestI mean03:22
mordredtestI'm talking to you right03:23
mordredtestfrom03:23
mordredtestTHUNDERBIRD03:23
morganfainberghehe, that is just bizzare03:23
mordredtestyah03:23
mordredmordredtest: I wonder if thunderbird does notifications03:23
mordrednope03:23
morganfainbergthat is unfortunate03:23
morganfainbergkind of a serious gap for any reasonable irc client03:24
mordredtestit does underline names03:24
mordredtestwhen someone spoke to me03:24
mordredtestbut03:24
mordredtestI mean03:24
mordredtestwhy?03:24
*** vipul is now known as vipul-away03:24
morganfainbergmordredtest, not sure, but i think i need to try this now.03:24
morganfainbergjust for the novelty03:24
mordredit's worth looking at at least03:25
*** AlexF has joined #openstack-infra03:25
mordredI do enjoy that their twitter support looks like IRC03:25
*** rockyg has quit IRC03:25
lifelessmordred: there are console clients that do that too03:25
lifelessmordred: that said, wtf; wasn't the value proposition of thunderbird to be 'do one thing well' ?03:26
mordredlifeless: yup to both things03:26
morganfainberglifeless, ++03:26
morganfainbergisn't that a value proposition for most good apps these days?03:26
mordreduntil they decide to do all the other things03:27
mordreddhellmann: could we cut a new release of oslo.sphinx please?03:27
lifelessmordred: pony request03:27
lifelessmordred: I'd like something to nag when branches have unreleased code on them03:27
mordredlifeless: I'm trying follow up on getting rid of the last things in openstack that depend on d2to1 transitively03:27
*** rickerc_ has joined #openstack-infra03:28
mordredlifeless: speaking of - could I have a new diskimage-builder release?03:28
*** guitarza1 has joined #openstack-infra03:28
mordredlifeless: and I updated this: https://review.openstack.org/#/c/42514/ and would like it merged and relased too03:28
*** cherriges has joined #openstack-infra03:29
*** rickerc has quit IRC03:29
*** Protux has quit IRC03:29
*** odyi has quit IRC03:29
*** SpamapS has quit IRC03:29
*** guitarzan has quit IRC03:29
*** Protux has joined #openstack-infra03:29
*** rickerc_ is now known as rickerc03:29
*** cherriges is now known as odyi03:29
*** odyi has quit IRC03:29
*** odyi has joined #openstack-infra03:29
*** SpamapS has joined #openstack-infra03:29
*** SpamapS has quit IRC03:29
*** SpamapS has joined #openstack-infra03:29
lifelessmordred: point me at the how-to-release docs again ?03:29
*** AlexF has quit IRC03:29
mordredlifeless: git tag -s $tagname ; git push gerrit $tagname03:30
mordred(the -s is important, because it signs the tag, and non-signed tags are not recognized as being real)03:30
*** mordredtest has quit IRC03:32
mordredWOW.03:33
mordredmorganfainberg: the thunderbird twitter thing does not have tab completion of nicks03:34
mordredoh - yes it does. its just slow03:34
morganfainbergmordred, that would be a serious failing if didn't have that.03:34
mordredmorganfainberg: yeah. it seems to be working onw03:35
mordrednow03:35
* mordred has removed the IRC connection, but is going to keep the twitter one for a bit to see how that works out03:35
morganfainbergmaybe had to cache a list followers/follwoed03:35
*** ericw has joined #openstack-infra03:37
mordredprolly03:37
*** ericw has quit IRC03:41
lifelessmordred: is that a addon or core thunderbird ?03:47
lifelessmordred: anyhow, what do you think of my nag thing pony request?03:47
mordredlifeless: might be premature for the openstack projects that have 6 months cycles03:47
mordredlifeless: I liek the theory-ish though03:48
lifelessmordred: we could set a release policy per branch03:48
mordredlifeless: nod03:48
lifelessmordred: like 'continuous', 'more than X weeks inventory', 'every X weeks'03:48
mordredlifeless: would be helpful for things that get sporadic and potentially low amounts of dev03:48
mordredlike pbr and git-review03:49
mordredthere's a patch in pbr right now that fixes a bug for someone, for instance03:49
mordredbut in general, I hope we do not do much movement on pbr03:49
mordredso a 'nag me about getting a release done' makes sense03:49
*** HenryG has quit IRC03:52
lifelessI also want a semver automatic release script03:54
lifelesswhere should first drafts of these be put ?03:54
mordredwhat's semver?03:57
mordredand I'd make patches to config - because you'd need zuul config to trigger them03:57
clarkbsemantic versioning. why not put the nag script in as a commit hook locally?03:57
mordredso, I'd think it would want to be a script in slave_scripts, with a job(s) in jjb config and a zuul entry03:57
mordredclarkb: sure, but I mean, what does "semver automatic release script" mean?03:58
clarkbI'm not sure that a script that bugs you is a general thing everyone eants03:58
mordredclarkb: I agree. but I could see it being an opt-in script that a project could request03:59
mordredI'd opt in to it for pbr, for instance04:00
mordredI forget that I have local patches installed on my laptop all the time04:00
*** anteaya has joined #openstack-infra04:01
mordredlifeless: can you explain "semver automatic release script"04:01
lifelessclarkb: because releasing is not coupled to the person doing the commit04:01
mordredlifeless: the individual words all make sense, but the combination of them do not04:01
anteayaI'm fine with a script that bugs mordred04:01
lifelessmordred: oh so04:01
mordred(btw, I would love it if they would remove the use of - from the semver spec)04:02
mordredsince that had well documented uses that conflict with his WELL before he wrote that04:02
lifelessmordred: when I went to release dib04:03
lifelessmordred: I had to:04:03
lifelesspull04:03
lifelesscheck existing tags04:03
lifelessassess whether there was forward or backwards incompatible changes04:03
lifelesspick a new number based on the last two items + semver rules.04:03
lifelessdo the release.04:03
lifelessmordred: so I'd like something that:04:04
mordredyes. I agree04:04
mordredthat would be a good script04:04
lifeless - lets me say 'diskimage-builder minor'04:04
lifelessand it goes and does it all04:04
mordredyuip04:04
lifelessin fact even that, do-release openstack/diskimage-builder major/minor/point.04:04
mordredI'd like it to be able to suggest something04:05
mordredby looking at the api between the two, and telling me something is different04:05
lifelessso putting scripts that one might run locally too in config is a little weird04:05
mordredindeed. if the script itself has general use outside of config04:06
mordredthen putting it elsewhere is a good idea04:06
mordreddo you think the nag script has general use?04:06
lifelessa 'check X and report whether it should do a release' script seems general.04:06
mordred(I think the release code wants to live in pbr, fwiw, because I already have some of the other bits in there)04:06
lifelessglueing that into projects.yaml is openstack specific.04:06
mordredyup04:07
*** ericw has joined #openstack-infra04:08
lifelessso04:09
lifelessis there another infra tree it might go in - a generic release/code gardening kinda place?04:09
lifelessmordred: what - in the semver spec?04:11
mordredlifeless: for pre-releases04:11
lifelessoh04:12
lifelesspoint 1104:12
mordredand 904:12
mordredI've considered filing a bug04:12
mordredbut everytime I've ever given feedback to anyone who works at github, I've been met with MASSIVE arrogance and disdain04:13
*** ericw has quit IRC04:13
mordredso I preemptively give up04:13
mordredI'd love it if semver was usable by linux hackers04:13
mordredand I'd love it if someone else would fix hat04:13
mordredthat04:13
mordredas soon as they do, I will promote it with gusto04:13
mordredin the meantime, I'm happy to say "versioing similar to semver rules, except with different syntax choices"04:14
lifelessis there a common prerelease ruleset for 'linux' ?04:14
lifelessAFAIK only deb has a prerelease syntax at all.04:14
mordrednope04:15
mordredand you're right04:15
mordredI like pep440's approach, since it's not in conflict with existing schemes04:15
mordredN[.N]+[{a|b|c|rc}N][.postN][.devN]04:15
mordredif you choose to use it, you don't produce syntactically incorrect versions for other things04:16
mordredhrm. it's on github04:17
mordredmaybe I'll just fork it04:17
lifelesshmm, I'm not sure pep440 will be interepreted correctly on debian04:18
lifelessbut I haven't finished reading the full thing yet04:18
lifeless(by dpkg --compare-versions specifically)04:19
lifelessyup, it's incompatible04:19
lifelessmordred: the prerelease format in pep440 is interpreted as postrelease by debian.04:20
mordredlifeless: I'm certain that it's incompatible04:20
mordredlifeless: in terms of version math04:20
mordredlifeless: but semver is actually a syntax error on rpm04:21
lifelessmordred: thats fine04:21
lifelessmordred: IMNSHO04:21
*** vipul-away is now known as vipul04:22
lifelessmordred: since AFAIK rpm doesn't have pre-release support, it's appropriate to error when mapping that to rpm.04:22
lifelessmordred: and for debian it should be mapped to ~04:22
mordredwhat would be GREAT is if we could actually start to align these in to one system04:23
mordredlet - be reserved to indicate (re)distributor additions and patches04:23
lifelessmmm04:23
mordredpep440's use of a restricted set of alpha chars to denote prerelease is nice04:24
mordredand is something that could be _added_ to debian version math04:24
lifelessas long as there is a way to compile any given versioning scheme to (debian, python, rpm)04:24
lifelessthen I'm happy04:24
mordredyah04:24
lifelessI really don't give a rats whether there is one or a dozen different schemes04:25
mordredI do, because is just assinine04:25
mordreds/is/it is/04:25
lifelesspep440 is a meta-scheme04:25
lifelessit's the union of everything04:26
mordredyup. but also a paring down to something comprehensile04:26
mordredas a format, I think it's great04:26
mordredas a set of rules for _when_ you change things, I think semver is great04:26
*** zaro0508 has joined #openstack-infra04:26
mordredwhat I think would be fantastic is the union of the two of them04:26
lifelessright, but it doesn't describe backwards compat / api change/bugfix interactions04:27
lifelessso04:27
lifelessto me semver (and the libtool version rules which are similar) is in one problem space04:27
lifelessand pep440 is another04:27
mordredI agree with you (and I believe that's what I just said)04:27
lifelessand deb/rpm are closer to pep440 than semver04:28
lifelesssure04:28
lifelessnot debating04:28
mordredk04:28
mordred:)04:28
lifelessjust thinking out loud04:28
lifelessthe reason I say I don't care if tere are a dozen schemes in the semver space04:28
lifelessis that if there are a dozen such schemes, there are a dozen distinct versioning-driven-by-code-change-categorisation policies04:29
lifelessand so that makes sense04:29
*** mrda has quit IRC04:29
lifelessthe primary thing is that it be possible to compile the output of such a scheme to the target platforms; if you can't, live is very very unpleasant04:30
lifelessmordred: https://fedoraproject.org/wiki/Packaging:NamingGuidelines#Pre-Release_packages04:30
lifelessmordred: so there does appear to be -a- way for rpm04:33
mordredhttps://github.com/emonty/semver04:37
mordredthere's my first step towards a modification04:37
mordredI have not yet updated the BNF grammar04:39
*** ericw has joined #openstack-infra04:39
mordredbut that's possibly because I do not care about the BNF grammer :)04:39
*** ericw has quit IRC04:44
lifelessmordred: so I think it works, but I still don't see the point of changing it :)04:45
mordredlifeless: because I don't see the original point of using a - when there were other options04:54
mordredlifeless: it's like, if you're going to make something new and wonderful, you could also have the humility to at least pretend to look at the existing world a LITTLE bit04:55
mordredand maybe not be compatible with _everyone_04:55
mordredbut with a mild amount of work, you could be compatible with _someone)_04:55
mordredbut it depends on whether or not you want to collaborate04:56
mordredor make a new shiny thing that causes everybody to follow your choices04:56
lifelessmordred: hmm05:03
lifelessmordred: so semver to me seems pretty natural05:03
lifelessmordred: But thats my Debian background probably.05:03
mordredlifeless: the - in semver seems massively arrogant to me05:03
lifelessmordred: hyphens in Debian separate different parts of the version05:04
lifelessmordred: debian and upstream05:04
mordredright. but debian and redhat both use the - for that purpose05:04
mordredso there is already an ecosystem meaning for the - separatoin05:04
mordreda very clear one05:04
lifelessright, but since you need a compile step from semver to most other things /anyway/05:05
lifelessthe - isn't a problem, and the conceptual separation is something everyone is used to.05:05
mordredit's an interesting point05:05
mordredI think for me I'd hope that semver would be step one05:05
mordredand the distros starting to grok it would be step two05:06
mordredwith an eventual goal being that there is no compile step05:06
mordredso anything that adds another need for a compile step05:06
mordredto me is a bug05:06
mordredbecause I want to get rid of the compile steps05:06
lifelessmordred: Thats a lovely dream, I don't think it's feasible - look at pep440 which introduces *yet another* such compiler05:06
mordredbut pep440 + semver + using - separation for distro additions05:07
mordredcould actually be an easy to understand, easy to parse set of rules05:08
lifelessmordred: doesn't help at all, because you have to map prerelease across, which requires represenation specific interpreters05:08
mordredI disagree05:08
lifelesse.g. in deb ~, in rpm the semver prerelease goes into the 'distro additions' segment05:08
mordredright. so, if we get a sane upstream version thing that people can use05:09
mordredthen next step is to get the distros to start groking05:09
mordredthere is no compelling reason for them to re-align to anything right now05:09
mordredbecause there is nothing to realign to05:09
mordredit would be pointless05:09
lifelessthe problem is that distros are the union of all requirements05:09
lifelessso there si there is little reason for them to realign ever05:10
mordredI believe you and I have different worldviews and different goals, perhaps05:10
lifelessthey can / will just map new things into their system, and adjust their system just-enough to cope05:10
mordredI view things like the divergence between the version systems used by debian and redhat as a fundamental bug in free software05:10
mordrednot a feature05:10
mordredor an interesting quirk05:10
*** ericw has joined #openstack-infra05:10
lifelessI don't view it as a feature, thats for sure05:11
mordredthese things should communicate05:11
mordredwhich is why I almost can be a fan of semver05:11
lifelessbut there's a bunch of pragmatic issues even if the syntax and interpreters were identical that make direct reuse of versions problematic05:11
lifelesssonames, for instance.05:11
mordredget rid of the -, and I'm a fanboi and would talk about it at converences05:11
mordredconferences05:11
lifelesscan I paraphrase? 'The - in semver makes version numbers ambiguous when combined with rpm or dpkg versions and thats bad'05:12
mordredyes05:13
mordredthat is an excellent paraphrase05:13
mordredif I see a - in a version, I assume there is a distro part05:13
mordredwhich may be _my_ debian background coming through :)05:13
*** ericw has quit IRC05:15
mordredlifeless: thanks. I've used that sentence in an update I just pushed05:16
mordredI think that very clearly describes the impetus05:16
lifelessok, so - I get that, but given the situation *today* it's not a functional problem. The question is 'would it be a functional problem if distros wanted to support it directly'?05:16
lifelessAnd05:16
lifeless'will it confuse users'?05:16
lifelessThe confusion of users is a significant aspect.05:16
lifelessAnd one I hadn't really cottoned onto05:17
mordredfunctional problem I think is solvable in a few different ways05:17
mordredthe confusion I believe I now understand is the thing that was bugging me05:17
mordredI like it when conversations lead to revalations!05:18
lifeless:)05:18
mordredI think I'm going to more explicitly steal from pep440 in mine by indicating that pre-releases only really can use a|b|c|rc05:19
mordredbecause, again, since the issue is about potential confusion05:19
mordredI think it's worth having actual rules there, rather than "put whatever you want after the - it doesn't really carry meaning"05:20
mordredor, it carries meaning due to sorting rules, but none that's immediately and clearly apparent05:20
mordredto a human05:20
lifelessso you can say a1 right ?05:20
mordredyup05:20
mordredpre-release version section is indicated by (a|b|c|rc)[0-9]*05:21
mordredand is considered a modifier on the thing to its left05:21
mordredso 1.2.3.a3.a4 would be the fourth alpha release leading towards the third alpha release of 1.2.305:22
mordredand is silly05:22
mordredbut possible if you need it05:22
mordrednah. if this is intended for clarity, then I think it needs to be clear like the first three05:24
mordredand really specific05:24
mordredI think that having one and only one pre-release section is clearer, even if parsers could parse a more complex thing05:24
* anteaya has had enough fun for one day and will be going to sleep now, thanks05:25
*** anteaya has quit IRC05:25
mordredbah!05:25
mordredyou can never have enough fun when talking about versioning schemes!05:25
lifelessI agree, but interpretation #205:25
mordredlifeless: can you restate what you think?05:27
lifelessno matter what you do, talking about versioning schemes will never be enough fun05:28
lifelessmordred: last two lines were just humour05:29
mordred:)05:32
*** AlexF has joined #openstack-infra05:40
lifelessmordred: so what is oslo.version ?05:40
mordredlifeless: the version consuming portion of pbr broken out into its own library05:41
mordredso that pbr can just be the build portion05:41
mordredand oslo.version the runtime portion05:41
mordredeither should be able to be used without the other05:41
lifelessok05:41
lifelessso it reads pkg-info etc05:41
lifeless?05:41
mordredyup05:41
mordredas well as /etc/$project/version.ini (for the distro override thing)05:42
*** ericw has joined #openstack-infra05:42
mordredalthoguh I think that needs clearer semantics, tbh05:42
lifelessyeah, though I still don't get the distro thing :P05:43
lifelessbbiab05:43
*** ericw has quit IRC05:46
*** davidhadas_ has joined #openstack-infra05:50
mordredlifeless, clarkb, ttx: ok. I made a bunch of updates to https://github.com/emonty/semver/blob/master/semver.rst05:56
mordredplus side - openstack's versioning is mostly compliant05:57
mordredmaybe I should move that file into the pbr tree05:57
mordredand then make a tool like lifeless was requesting earlier which will make it easy to make a local tag that matches types of the above rules05:57
*** SergeyLukjanov has joined #openstack-infra06:04
*** AlexF has quit IRC06:06
*** ericw has joined #openstack-infra06:13
lifelessmordred: you should06:14
lifelessmordred: 'tox' in pbr just hated on me06:15
lifelessDownloading/unpacking argparse (from -r /home/robertc/work/nova/requirements.txt (line 5))06:15
lifeless  You are installing an externally hosted file. Future versions of pip will default to disallowing externally hosted files.06:15
lifelessis one thing06:15
lifelessoh, wait.06:16
lifelessEWTF am I doing in the nova tree06:16
lifelessso it failed on boto etc, but thats irrelevant as I was just nuts06:16
*** ericw has quit IRC06:17
lifelessmordred: http://paste.ubuntu.com/6169970/06:19
lifelessmordred: any thoughts ?06:19
mordredlifeless: looking06:27
*** zaro0508 has quit IRC06:28
mordredlifeless: are you running that outside of a git repo? and/or is git there?06:28
lifelessthere is git there and there is a repo06:28
lifelessmy global config deliberately has no user details06:28
lifelessso I don't commit as <personal> in a work repo or vice verca06:28
mordredgotcha06:29
lifelesssounds like pbr isn't isolating itself from the environment enough06:29
mordredI wonder if that is causing a problem06:29
mordredyeah06:29
lifelessfixtures.TempHomeDir + explicit git global config06:29
lifelessshould do the ticket06:29
lifelessI will spin that up shortly06:29
lifelessbut first, I've had a fully 'on' day, time for a little time out.06:30
mordredmmm. yes. time out06:31
mordredI'm snacking and beering - if you don't have it sorted when I next am on, I'll also take a look06:32
*** ericw has joined #openstack-infra06:43
*** AlexF has joined #openstack-infra06:45
*** guohliu has quit IRC06:49
*** ericw has quit IRC06:52
*** salv-orlando has quit IRC06:52
*** tkammer has joined #openstack-infra06:55
*** afazekas_zz is now known as afazekas06:59
*** tvb has quit IRC07:03
*** tvb has joined #openstack-infra07:03
*** tvb has quit IRC07:03
*** tvb has joined #openstack-infra07:03
*** AlexF has quit IRC07:05
*** ericw has joined #openstack-infra07:18
*** SergeyLukjanov has quit IRC07:22
*** ericw has quit IRC07:23
*** guohliu has joined #openstack-infra07:24
*** alexpilotti has joined #openstack-infra07:46
*** tvb has quit IRC07:48
lifelessmordred: isn't it uhm 0230 for you ?07:48
lifelessish07:48
*** thingee is now known as thingee_zzz07:52
openstackgerritlifeless proposed a change to openstack-dev/pbr: Fix test_changelog when git isn't globally setup.  https://review.openstack.org/4882807:55
lifelessmordred: ^07:55
*** SergeyLukjanov has joined #openstack-infra08:07
*** tvb has joined #openstack-infra08:14
*** tvb has quit IRC08:14
*** tvb has joined #openstack-infra08:14
*** kpavel has joined #openstack-infra08:18
*** kpavel_ has joined #openstack-infra08:19
*** kong has joined #openstack-infra08:22
*** kpavel has quit IRC08:23
*** kpavel_ is now known as kpavel08:23
openstackgerritlifeless proposed a change to openstack-dev/pbr: Switch away from tearDown for BaseTests.  https://review.openstack.org/4883108:45
openstackgerritlifeless proposed a change to openstack-dev/pbr: Add a test for command registration.  https://review.openstack.org/4883308:59
*** yonglihe_ has quit IRC09:02
*** cody-somerville has quit IRC09:15
*** mrda has joined #openstack-infra09:25
*** SergeyLukjanov has quit IRC09:46
*** mrda has quit IRC10:14
lifelessmordred: so pbr seems clearly the wrong place for next version stuff I was ponying around10:20
*** SergeyLukjanov has joined #openstack-infra10:21
openstackgerritlifeless proposed a change to openstack-dev/pbr: Add a test for command registration.  https://review.openstack.org/4883310:21
*** xchu has quit IRC10:22
*** ericw has joined #openstack-infra10:28
*** ericw has quit IRC10:38
*** guohliu has quit IRC10:39
*** alexpilotti has quit IRC10:39
*** tvb has quit IRC10:51
*** stevebaker has quit IRC10:57
*** stevebaker has joined #openstack-infra10:57
*** tvb has joined #openstack-infra10:57
*** tkammer has quit IRC11:11
*** CaptTofu has joined #openstack-infra11:21
*** ericw has joined #openstack-infra11:35
*** ericw has quit IRC11:40
*** SergeyLukjanov has quit IRC11:44
*** hashar has joined #openstack-infra11:45
lifelessmordred: where do you want bugs on cookiecutter? tox fails in a fresh cut.11:55
lifeless    Complete output from command python setup.py egg_info:11:55
lifeless    error in setup command: Error parsing /home/robertc/work/git-next-version/setup.cfg: Exception: Versioning for this project requires either an sdist tarball, or access to an upstream git repository.11:55
*** alexpilotti has joined #openstack-infra12:00
*** hashar has quit IRC12:01
*** tkammer has joined #openstack-infra12:05
*** ericw has joined #openstack-infra12:06
*** ericw has quit IRC12:11
*** qba73 has joined #openstack-infra12:40
*** tvb has quit IRC12:41
*** che-arne has joined #openstack-infra12:44
*** SergeyLukjanov has joined #openstack-infra12:59
*** SergeyLukjanov has quit IRC13:06
*** nicedice has quit IRC13:08
*** basha has joined #openstack-infra13:08
*** nicedice has joined #openstack-infra13:08
*** basha has quit IRC13:17
*** basha has joined #openstack-infra13:18
*** michchap_ has quit IRC13:19
*** michchap has joined #openstack-infra13:22
*** thomasbiege has joined #openstack-infra13:22
*** michchap has joined #openstack-infra13:24
*** SergeyLukjanov has joined #openstack-infra13:30
*** basha has quit IRC13:31
*** thomasbiege has quit IRC13:33
*** che-arne has quit IRC13:35
*** SergeyLukjanov has quit IRC13:39
*** SergeyLukjanov has joined #openstack-infra13:44
*** SergeyLukjanov has quit IRC13:50
*** Guest98622 is now known as Vivek13:56
*** Vivek has joined #openstack-infra13:56
*** qba73 has quit IRC14:11
*** tjones has joined #openstack-infra14:15
*** tjones has quit IRC14:19
*** guohliu has joined #openstack-infra14:19
*** dims has joined #openstack-infra14:28
*** SergeyLukjanov has joined #openstack-infra14:44
*** schwicht has joined #openstack-infra14:57
*** schwicht has quit IRC15:02
*** ericw has joined #openstack-infra15:02
*** schwicht has joined #openstack-infra15:03
*** thomasm has joined #openstack-infra15:11
*** SergeyLukjanov has quit IRC15:18
*** thomasm has quit IRC15:22
mordredlifeless: on oslo please15:25
*** ericw has quit IRC15:32
*** dcramer_ has joined #openstack-infra15:34
*** kpavel has quit IRC15:37
*** basha has joined #openstack-infra15:39
dhellmannmordred: oslo.sphinx 1.1?15:48
*** dcramer_ has quit IRC15:49
*** basha has quit IRC15:50
mordreddhellmann: that would be nice - oslo.sphinx 1.0 is still using d2to1 version of pbr15:51
mordredand d2to115:51
dhellmannsure, I can do that now -- I was verifying the version would be ok, since I'm not as familiar with the semver rules15:52
dhellmannmordred: looks like the changes are all packaging related, except the intersphinx file thing; nothing should break backwards compatibility15:53
* dhellmann crosses fingers15:53
*** salv-orlando has joined #openstack-infra15:55
dhellmannmordred: 1.1 tag pushed15:56
mordreddhellmann: woot!15:56
mordreddhellmann: I made an openstack friendly semver fork: https://github.com/emonty/semver/blob/master/semver.rst if you want to read :)15:57
dhellmannreading15:57
dhellmannmordred: the bit that always trips me up is where dependency changes fall in terms of "backwards-compatible"15:57
mordreddhellmann: that's an interesting question15:58
mordreddhellmann: I think that if the contract from the thing in question to the thing consuming it changes, it would not be backwards-compatible15:58
dhellmannthe cliff/pyparsing thing is a good example15:59
dhellmannI thought bumping pyparsing to 2.0.1 fixed the bug that it wasn't possible to install the same versions of things under py2 and py315:59
mordredbut what broke in openstack was people's version pins of pyparsing, right?16:00
dhellmannwell, yeah, quantumclient should never have had anything specified for that16:00
dhellmannbecause they were not using it directly16:00
dhellmannand cliff had the right rules in its setup.py16:00
mordredright. I don't think that was a contract violation on your part16:00
mordredI believe it was that quantumclient was reaching in past your contract16:01
mordredand you violated that thing16:01
dhellmannthat's what I thought; sdague disagreed and thought I should have used 1.5 instead of 1.4.516:01
mordredbut- dependency tree as api contract is an interesting topic16:01
dhellmannit doesn't really matter, but I'm trying to understand how people interpret the guidelines to avoid conflicts in the future :-)16:02
mordredsdague: I'd love a dissenting opinion16:02
mordred++16:02
mordred_this_ is actually an area that I don't think semver really covers16:02
dhellmannbtw, do you know the state of that fix for the stable/grizzly gate? I have a cliff release that does not use pyparsing ready, but as dreamhost has broken gates twice this week with releases to our libs, I'd like to hold off a bit before making another ;-)16:02
*** dcramer_ has joined #openstack-infra16:03
dhellmannI was under the impression someone was going to "magic" the fix to remove the pin for pyparsing in quantumclient in stable16:03
mordredoh, well, we did a couple of quantumclient releases16:04
mordredand it now just depends on neutronclient16:04
mordredbut I believe there are some issues with the symbols being exposed that are causing different stable gate failures16:05
mordredand, well, landing things through the gate hasn't been fun for a couple of days16:05
dhellmannmordred: ok, the symbol thing isn't related to cliff or pyparsing, so that's good at least16:06
mordredyah!16:06
dhellmannmordred: does our git setup support grokmirror?16:17
mordreddhellmann: I don't know what grokmirror is (no, but I'd like to learn)16:17
dhellmannmordred: https://www.kernel.org/mirroring-kernelorg-repositories.html16:18
dhellmannI'm looking for a way to get a copy of all of our repositories without scraping the cgit UI16:19
dhellmannhttps://github.com/mricon/grokmirror16:21
jeblairdhellmann: not to distract from looking at grokmirror which might be a good idea, but you may be able to get what you need immediately with 'ssh review.openstakck.org -p 29418 gerrit ls-projects'16:21
mordredjeblair: so, grokmirror actually looks interesting and I could see us even making use of it in d-g16:21
mordred(on very short examination)16:22
mordredfrom what it looks like, the server maintains a json file listing the repos and last modified time16:22
mordred(there's a tool for that)16:22
mordredso things wanting to mirror grab the file first, and then just run git remote update on the repos that have actually changed16:23
jeblairmordred: yeah, also putting it on jenkins slaves for faster local cloning.16:23
mordredyup16:23
jeblairanyway... sunday.16:23
mordredtotally. have a sunday16:23
mordreddhellmann: tl;dr - no, we don't - but it seems like a worthwhile thing to add to the infrastructure16:23
mordredand possibly make use of ourselves16:23
dhellmannmordred: ok, no hurry, I'll look at the gerrit tip jeblair tossed out (need to figure out why ssh is refusing my connection, probably an identity thing)16:24
dhellmannindeed, forgot the gerrit user name part16:24
dhellmanncool, I can script around this, thanks, jeblair16:25
mordredand in the meantime, you should be able to build a mirror fairly simply with for repo in `ssh review.openstakck.org -p 29418 gerrit ls-projects` ; do mkdir `dirname $repo` ; pushd `dirname $repo` ; git clone git://git.openstack.org/$repo; popd; done16:25
mordredhrm. you need a -p on the mkdir so that it doesn't fail when the dir is already there16:25
mordredbut you get the idea16:25
dhellmannmordred: yep16:27
mordredhttps://bugs.launchpad.net/openstack-ci/+bug/123279916:30
uvirtbotLaunchpad bug 1232799 in openstack-ci "add grokmirror support" [Undecided,New]16:30
*** tvb has joined #openstack-infra16:37
morganfainbergmordred, phsaw, stop offering "easy" and "in the mean time" solutions :P *plans to make similar script occur locally*16:39
mordredmorganfainberg: :)16:39
* mordred just realized that if we had grokmirror, I could just run it in my src dir on my laptop16:40
mordredand always make sure that all of my local repos were up to date16:40
* mordred is a bit excited16:40
morganfainbergmordred, that makes far too much sense.16:41
mordredmorganfainberg: yup16:41
*** salv-orlando has quit IRC16:41
dstufftmordred: have you hit any timeouts in pypi today? i know it was failing on thrift (dunno if you ran any jobs today tho)16:44
*** tjones has joined #openstack-infra16:44
mordreddstufft: lemme see if I've run anything that wanted to hit pypi16:46
dhellmannmordred: that's what I wanted it for :-)16:47
mordredhttp://paste.openstack.org/show/4767516:47
mordredoops. bug. one sec16:48
dhellmannthe mkdir has to come in the else block, no?16:48
mordredthe -p should always succeed16:48
dhellmannoh, no, missed the dirname16:48
mordredgod, if I really wanted to be awesome, I should have it gitreview -s if it clones16:49
dhellmanngitreview -s?16:49
dhellmannoh, for new repos16:50
mordredhttp://paste.openstack.org/show/4767716:51
mordredthere we go16:51
mordredthat's working16:51
mordred(I have a remote setup for review.o.o port 29418)16:51
mordredCloning into 'openstack/melange'...16:52
mordredfatal: Could not read from remote repository.16:52
mordredheh16:52
mordredwe should really you know, figure out an opinion on that16:52
ekarlsomordred: melange ?16:52
ekarlsoain't that dead ?16:52
mordredyup16:52
mordredbut we don't delete things from gerrit16:53
ekarlsoah16:53
mordredproblem is, we're not mirroring it to git.o.o, because that's kinda silly16:53
mordredso it's in a weird limbo state16:53
mordredneat! that worked16:59
mordredtakes 4 minutes to git remote update every repo in openstack :)17:09
*** tkammer has quit IRC17:17
*** thingee_zzz is now known as thingee17:25
*** schwicht has quit IRC17:33
*** tjones has quit IRC17:39
*** davidhadas has quit IRC17:53
*** guitarza1 is now known as guitarzan17:58
sdaguemordred, dhellmann: so my take on why I think the pyparsing req change should have been a Y bump (X.Y.Z land)...17:58
*** thingee is now known as thingee_zzz17:58
sdagueis that it was a stepwise X bump in dependency17:58
sdague1.4.3 required == 1.5.7 and 1.4.4 required > 2.0.117:59
sdaguethere was no overlap in dependencies, so you couldn't satisfy the new software without taking a major upgrade of another package17:59
sdaguetriggering additional software installation at a major release level doesn't feel like a Z bump to me18:01
mordredok. I can see that logic18:03
sdaguedstufft: yeh, we hit one pypi timeout - http://logstash.openstack.org/#eyJzZWFyY2giOiJcIkVycm9yIFRoZSByZWFkIG9wZXJhdGlvbiB0aW1lZCBvdXQgd2hpbGUgZ2V0dGluZ1wiIiwiZmllbGRzIjpbXSwib2Zmc2V0IjowLCJ0aW1lZnJhbWUiOiI4NjQwMCIsImdyYXBobW9kZSI6ImNvdW50IiwidGltZSI6eyJ1c2VyX2ludGVydmFsIjowfSwic3RhbXAiOjEzODA0Nzc3NjIzMDh918:03
mordredperhaps we should add text around that in my new semver fork...18:03
sdaguesure18:03
sdagueit's all a judgement call, which is why I tried to word the email on list pretty softly about it18:04
*** dims has quit IRC18:04
sdagueI just really want to go one week without having to deal with the consequences of dependency upgrades :)18:04
mordredyeah. I agree18:05
*** fbo_away is now known as fbo18:06
mordredI think that's the reason I've kind of OCD'd on this semver issue recently18:06
mordredI think it's really helpful to have clear guidelines18:06
dstufftlol18:06
dstufftversioning18:06
dstufftHAVE FUN18:06
mordredand I think we've found around here that making those less flexible and more explicit is more scalable18:06
mordredso a lot of "if you want to do this, then do this" bits are basically fail18:06
mordreddstufft: oh, it's a constant stream of fun on that topic here! :)18:07
dstufftwe're lucky in that all we really need to define is what order versions sort in18:07
dstufftthough we tried in PEP440 to be prescriptive about semantic versions18:07
mordreddstufft: what I did last  night was make a PEP440 compliant version of semver18:08
dstufftmordred: neat18:08
dstufftmordred: are you gonna make it a website, or it's own PEP?18:08
dstufftmordred: you shuold send it to Nic Coghlan18:08
dstufftNick18:08
mordredhrm. interesting idea - I hadn't thought of making it a pep18:08
mordredI was just going to add it as docs to pbr for us - but that's a great idea18:08
mordredI might have to remove oneof the snarky paragraphs though18:09
dstufftmordred: I think it'd be a nice PEP, were PEP440 defines the format and how to order it, and PEPXXX defines a semantic versioning for it that people can opt in to using18:10
openstackgerritMonty Taylor proposed a change to openstack-dev/pbr: Add the semver documentation  https://review.openstack.org/4885518:11
mordreddstufft: ++18:11
mordreddstufft: I'll start working on that18:11
dstufftmordred: do you have Nick's email? He's sort of the BDFL of packaging and might have insight18:11
mordredyah.18:11
dstufftcool18:11
*** dkliban has joined #openstack-infra18:14
mordreddstufft: btw - there's the new text in the context of adding it to pbr docs ^^^18:22
mordreddhellmann: ^^ (I'd love a review from you on that)18:22
mordredsdague: (same with you, although I have not added any text around your dependency thoughts yet)18:22
clarkbthis weather18:26
clarkbjog0 are flights having problems?18:27
clarkbI shouldnt have to strategize a drive to bend in september... should be "exciting"18:27
*** SergeyLukjanov has joined #openstack-infra18:27
mordredclarkb: wow. what sort of weather are you having?18:32
clarkbtyphoon leftovers. lots of rain and wind18:33
clarkband snow but not low enough for the passes thankfully18:34
*** thedodd has joined #openstack-infra18:35
*** thedodd has quit IRC18:35
*** thedodd has joined #openstack-infra18:35
*** thedodd has quit IRC18:46
*** jpeeler has quit IRC18:49
lifelesshttps://bugs.launchpad.net/oslo/+bug/123286818:54
uvirtbotLaunchpad bug 1232868 in oslo "fresh cookiecut environment barfs" [Undecided,New]18:54
mordredlifeless: thanks18:55
lifelessmordred: added more info18:57
lifelessmordred: looks like it needs some - -> _ folding logic18:57
mordredlifeless: that's not a cookiecutter bug per-se (I might be wrong) - you need to do an initial commit18:57
mordredand YES - ti needs - _ folding logic18:57
mordredI believe I'm going to have to add an additional input var18:57
mordredso "repo_name" and "module_name"18:58
* mordred started hacking on that18:58
lifelessmordred: so if the init/add/commit is needed to make it usable, that seems like a bug in /something/18:58
mordredlifeless: nod18:58
mordredlifeless: let me see if there is a way for me to add operational hooks18:58
mordredso that I can potentially do the git init/add/commit steps18:58
lifelessnote that for me there is also git config --local user.email and user.name steps18:58
mordredpoint well taken18:58
mordredhrm18:59
lifelessso just doing the init/add/commit won't work18:59
mordredI'm not 100% sure how to accomodate that - perhaps printing a message saying "now you need to git init/commit before this will work" ?18:59
lifelessmordred: that would remove somme wtfing18:59
mordredso that at least the expectation is clear18:59
mordredyah. ok. I can work on that19:00
lifelessmordred: note that the current message saying 'have to have a parent' is super misleading19:00
lifelessbecause I was like, how can I get this into gerrit so there is a parent, when I can't validate19:00
mordredlifeless: cookiecutter 0.7 (not yet released) supports the features we'll need for post-hooks19:01
mordredsigh. fail.19:02
mordredthe main author is having to deal with life drama19:03
mordredwhich is why 0.7 isn't out yet19:03
mordredthe life drama is perfectly fair19:03
mordredbut definitely one of the reasons why projects with a single human gatekeeper are problematic19:03
mordredlifeless: for translation domains - do you know if it should be project name or module name?19:07
mordredlike, python-swiftclient or swiftclient ?19:07
lifelessthe former19:08
lifelessit's not related to python19:08
lifelessit's an arbitrary key into /usr/share/locale/<lang>/LC_MESSAGES/$domain.mo19:08
openstackgerritMonty Taylor proposed a change to openstack-dev/cookiecutter: Differentiate between repo and module name  https://review.openstack.org/4885719:09
mordredlifeless: let me know what you think of that ^^19:09
mordredlifeless: I think it addresses the repo/module -/_ split, but I'm not sure if the default value/prompt text is clear enough19:10
lifelessHard to tell without unaware guinea pigs19:11
mordredindeed19:11
openstackgerritMonty Taylor proposed a change to openstack-dev/cookiecutter: Add some clarifying text to README about git  https://review.openstack.org/4885819:12
openstackgerritMonty Taylor proposed a change to openstack-dev/pbr: Add the semver documentation  https://review.openstack.org/4885519:16
mordredWOW19:17
mordredTHE GATE IS SO BAD19:17
mordredlifeless: speaking of - did you see you had a real test failure on one of your pbr patches?19:19
mordredlifeless: thanks for those, btw19:19
mordredI want all of them to land19:19
*** tjones has joined #openstack-infra19:28
*** jaypipes has quit IRC19:28
*** tjones has quit IRC19:32
lifelessmordred: was one real?19:32
mordredlifeless: yes19:32
mordredI -1'd the code review on it19:32
mordredso it should be easy to spot19:32
lifelessthanks, shall look19:33
lifelessC was up all night with coughing/breathing issues19:33
mordredsupporting python3 is hard19:33
mordredlifeless: ewww19:33
lifelessso today may be terrible19:33
mordredyah19:33
lifelessmum had her19:33
lifelesswhich means I have her now19:33
dstufftmordred: supporting python3 is easier if you just stop supporting python219:33
dstufft:D19:33
mordreddstufft: yes. yes it is19:35
mordreds/supporting python3 is hard/supporting python2 AND python3 is hard/19:35
lifelessmordred: btw, putting nontrivial stuff in __init__ is a bit of an antipattern19:35
mordredlifeless: agree19:35
mordredlifeless: are we doing that in pbr?19:35
lifelessmordred: better to have $module.tests.support or $module.tests.base or something19:35
mordredah. yes.19:35
lifelessmordred: cookiecutter and pbr19:35
mordredagree. I'll fix in both19:36
notmynamemordred: I can't seem to follow the conversation. something up with python-swiftclient?19:40
mordrednotmyname: nope. sorry, was using you as a naming example in a question19:40
openstackgerritMonty Taylor proposed a change to openstack-dev/pbr: Move base test case logic out of __init__.py  https://review.openstack.org/4886019:42
openstackgerritMonty Taylor proposed a change to openstack-dev/cookiecutter: Move base test class out of __init__.py  https://review.openstack.org/4886119:43
*** ericw has joined #openstack-infra19:44
*** jaypipes has joined #openstack-infra19:45
openstackgerritMonty Taylor proposed a change to openstack-dev/cookiecutter: Remove vim modelines  https://review.openstack.org/4886219:45
*** ericw has quit IRC19:48
*** thedodd has joined #openstack-infra19:49
*** dcramer_ has quit IRC19:52
*** ekarlso has quit IRC20:00
openstackgerritA change was merged to openstack-dev/cookiecutter: Differentiate between repo and module name  https://review.openstack.org/4885720:01
lifelessmordred: copy-pasting the stdout/stderr capturing and timeout glue everywhere seems poor.20:01
mordredlifeless: agree. thoughts?20:01
lifelessmordred: can I suggest a single fixture in oslo somewhere that encapsulates all of that20:01
lifelesse.g. oslo.testsupport.StandardFixtures()20:02
lifelessthen the copy-paste is just20:02
mordredlifeless: yes. actually, I've been meaning to do more with the fixtures modules in oslo, break it out into its own library - and to move some thigns in to fixtures themselves20:02
lifelessself.useFixture(StandardFixtures())20:02
mordredyah20:02
mordredI've actually been thinking even that an oslo BaseTestCase class might not be terrible - which would then use an oslo fixture thing20:04
mordredwhat do you think20:04
mordred?20:04
lifelessbase classes are bad20:04
openstackgerritA change was merged to openstack-dev/cookiecutter: Add some clarifying text to README about git  https://review.openstack.org/4885820:04
openstackgerritA change was merged to openstack-dev/cookiecutter: Move base test class out of __init__.py  https://review.openstack.org/4886120:04
openstackgerritA change was merged to openstack-dev/cookiecutter: Remove vim modelines  https://review.openstack.org/4886220:04
mordredawesome20:05
mordredyou know we have one in every project pretty much though20:05
lifelesshttp://rbtcollins.wordpress.com/2010/05/10/maintainable-pyunit-test-suites/20:05
lifelessyes, and in most of them it's a code smell IMO20:05
mordredbut where do you put self.useFixture(StandardFixtures()) ?20:06
mordredin every test case? and then assume that the 1200 devs out there are going to remember to do it?20:06
lifelessso that genuinely common to everyone policy is about the only time it makes sense :)20:07
lifelessbut20:07
mordredthat was all I was thinking of putting into the base test class :)20:07
lifelessthe problem is that folk then want to add helpers20:07
lifelessand assertions to the base20:07
mordredah. no. I'm not interested in that20:07
lifelessthe difference between20:07
lifeless'inherit from X'20:07
lifelessand 'def setUp(self):\nself.useFixture(StandardFixtures())'20:07
lifelessis 3 lines, one of which is blank20:08
mordredbut you have to inherit from _something_20:08
mordredand it's 3 lines per test class which can be forgotten20:08
lifelesssure20:08
lifelesswhich is why20:08
lifeless09:07 < lifeless> so that genuinely common to everyone policy is about the only time it makes sense :)20:08
mordrednod20:08
*** ekarlso has joined #openstack-infra20:09
lifelessI think the cookiecutter having a base class is an ok compromise20:09
lifelessthere's not enticement to follow the antipattern openstack-wide that way20:09
*** fbo is now known as fbo_away20:10
dstufftmordred: use py.test, no more base calsses :V20:10
dstufftautouse fixtures ftw20:11
mordreddstufft: too much magic, not enough explicit20:11
mordredI find py.test test suites very difficult to follow20:11
dstuffthard to follow?20:11
dstufftreally? :V20:11
mordredyes. truly20:11
mordredthe first time I tried to make a patch to tox, I had NO idea how the test suite worked20:12
dstufftwhat trips you up? I find them way easier because there's almost no boilerplate20:12
lifelessdstufft: py.test is way too clever20:12
mordredthere's no boilerplate20:12
mordreddstufft: that's the problem20:12
dstufft..20:12
dstufftyou want boilerplate?20:12
mordredas a person who has not read _everything_ there is to know about py.test20:12
mordredit's black magic20:12
mordredit's not clear what's going on20:12
mordredand I can't folow from the code itself20:12
lifelessdstufft: even the magical assert interception squicks me20:12
mordred"where does the X in the arg list come from? what's calling it?"20:12
dstufftlifeless: oh man I hate self.assertFoo20:13
dstufftI won't use them20:13
dstufftI use bare asserts even in non py.test20:13
mordredand herein we reach impass20:13
mordreddstufft: please don't use base asserts in non py.test20:13
mordredit's fine in py.test - they're supported there20:13
lifelessdstufft: you'll want to to fit in the style with projects to contribute too20:13
mordredthey're terrible in non py.test20:14
lifelessdstufft: or your reviewers may have words for you20:14
*** ericw has joined #openstack-infra20:14
mordredin any case - things with magical side effects are confusing to newcomers20:14
dstufftI got better things to do then try to remember which assertFoo I want in any particular case20:14
lifelessthere's no breadcrumbs20:14
mordredand we have a TON of those around here. they have a hard enough time figuring out the explicit stuff :)20:15
lifelessdstufft: sure, I'm not trying to modify your personal preference; just saying that in different environments there is value to consistency20:15
lifelessdstufft: and btw, assertThat, the last assertion you'll ever need :P20:15
mordredpy.test to me seems like powertools, which is great in a lot of scenarios20:16
mordredlike "if I use this, I can get a ton more done with less typing, and I'm smart, so it's ok"20:16
dstufftlifeless: sure, and I just don't submit patches to places that make me have to remember which assertWhatever I need to use (or look them up), maybe that's rude of me IDK, I got more things on my plate then I can get reasoanbly get done so if it annoys me I don't do it :D20:17
lifelessthis is like the LISP argument :P20:17
lifelessdstufft: you must have a headache contributing to openstack then :)20:17
dstufftlifeless: I don't think I have any openstack patches :)20:17
dstufftgranted I probably would if I worked directly on openstack at work (and I don't)20:18
dstufftand i'd probably have to put up with assertFoo in that case, but that's got $$20:18
mordreddstufft: well, most of the people at nebula hate openstack dev anyway - so you're probably safe :)20:18
mordredthey used to yell at me a lot20:19
*** ericw has quit IRC20:19
dstufftheh20:20
dstufftI'm somewhat isolated from openstack directly, I spend the bulk of my time working on our pieces20:20
mordredwell, I'm THRILLED with the contribution your work makes to OpenStack personally20:21
dstufftmy "contribution" to openstack seems to be whining about packaging20:21
dstufft;)20:21
ekarlsoopenstack dev, what's bad about that ?20:22
mordreddstufft: you might also run pypi and hack on pip and listen to us :)20:25
mordreddstufft: in any case, if you ever want an ATC exception to come to the summit for free, you just let us know20:25
dstufftmordred: :)20:25
*** salv-orlando has joined #openstack-infra20:26
dstufftmordred: gotta go for a bit20:26
*** ekarlso has quit IRC20:28
*** ekarlso has joined #openstack-infra20:28
mordredsdague: I have 9 patches up for pbr. several of them I've rechecked several times. Of that, in the last day, I have two passing test runs20:32
mordrednone of the fails are real20:32
*** ekarlso has quit IRC20:38
*** AlexF has joined #openstack-infra20:44
sdaguemordred: how many of them are elastic-recheck finding20:44
sdague?20:44
mordredsdague: at least half20:44
mordredsdague: but it's the same ones over and over again20:44
mordredsdague: it's amazing how painful it is20:45
sdagueyep20:45
sdaguewe've got a good dozen races in there20:45
*** ericw has joined #openstack-infra20:45
sdagueyeh, I've got a fix to something that I need to see the neutron fail to be useful. I'm on my 5th recheck, 3 passes, 2 unrelated fails20:49
sdagueI actually think the idle time test swarm would provide some very interesting data about how bad things are, especially with elastic-recheck to help us semi-automatically classify them20:49
*** ericw has quit IRC20:50
*** AlexF has quit IRC21:14
*** ericw has joined #openstack-infra21:16
*** ericw has quit IRC21:21
*** dims has joined #openstack-infra21:27
*** ekarlso has joined #openstack-infra21:28
openstackgerritA change was merged to openstack-infra/devstack-gate: Add pypi-mirror to the list of pre-cloned repos  https://review.openstack.org/4880521:40
*** tjones has joined #openstack-infra21:44
*** ianw has joined #openstack-infra21:46
mordredsdague: ++21:49
mordredO M G21:50
mordredthe d-g patch passed!21:50
*** Ryan_Lane has joined #openstack-infra22:02
*** tjones has quit IRC22:03
*** dkranz has quit IRC22:04
jog0clarkb: just arrvied in Bend22:08
*** SergeyLukjanov has quit IRC22:12
*** ekarlso has quit IRC22:14
*** ekarlso has joined #openstack-infra22:14
*** Ryan_Lane has quit IRC22:21
*** Ryan_Lane has joined #openstack-infra22:23
*** Ryan_Lane has quit IRC22:24
mordredjog0: congrats22:27
clarkbjog0 me too. just checked in. thinking of getting food at $brewpub in a bit22:27
mordredclarkb: it's guam where you lived, yeah?22:28
jog0clarkb: what hotel are you at?22:28
jog0count me in for food22:28
mordredclarkb: or am I spacecake?22:28
clarkbpheonix inn on franklin22:28
clarkbmordred pohnpei, near guam22:29
jog0mordred: the two are orthogonal22:29
jog0clarkb: same, I am on the second floor22:29
mordredjog0: ++22:29
BobBallRandom question that I assume ppl in here will know... Do I need to run tempest tests in a special way to get them executing in parallel?22:30
jog0clarkb: let me know when you are ready and lets meet in the lobby22:30
*** ArxCruz has joined #openstack-infra22:30
clarkbwill do22:31
clarkbBobBall we use testr --parallel to run them22:32
BobBalllooks like I need to upgrade testr then :)22:34
BobBallthanks22:35
*** mrda has joined #openstack-infra22:37
mordredBobBall: I _think_ the tox envs in the tempest tree will execute parallel or non-parallel as appropriate22:38
BobBallhmmmm - ok... Maybe it's a bug with the way I'm setting things up then22:39
BobBallI'm pretty sure they aren't running in parallel22:39
BobBallI'll dig22:39
BobBallthanks22:39
clarkbjog0: meet in the lobby at 4?22:48
jog0clarkb: sounds good22:49
*** slong has joined #openstack-infra22:50
mordredjog0, clarkb: if you want to review pbr patches, I will approve any beer you attempt to expense...22:51
*** mrda has quit IRC22:53
*** boris-42 has quit IRC22:57
*** cody-somerville has joined #openstack-infra22:59
*** vipul is now known as vipul-away23:02
mordredlifeless: did you ever make any headway on ValueError: I/O operation on closed file23:13
mordredin pip?23:13
mordredlifeless: http://logs.openstack.org/03/48803/1/check/check-pbr-devstack-vm-rawinstall/da93fc2/console.html23:13
mordredlifeless: I'm hitting it in my patch to try to get wheels to work23:13
*** thedodd has quit IRC23:18
openstackgerritMonty Taylor proposed a change to openstack-dev/pbr: Use wheels for installation  https://review.openstack.org/4880323:19
lifelessmordred: yes, it was a cascade error23:22
lifelessmordred: there was an earlier error that was reported, and once fixed it was all good23:22
lifelessmordred: the earlier error was due to the use of pypi.o.o rather than my local mirror23:23
dstufftmordred: ping23:23
dstufftmordred: how hard would it be to run the openstack tests (just once is alll I really need) against a different index server then pypi.o.o23:24
mordredlifeless: yup. same here. thanks - found the real error (I think)23:24
mordreddstufft: hrm. which ones, the "build the mirror" tests, or the "run tempest" ones?23:25
mordreddstufft: (both I think I can trigger easily, but want to know which thing you want)23:25
dstufftmordred: whichever would stress the index server the most23:25
mordredah. that would be the build-the-mirror test most likely23:25
dstufftmordred: I don't know if you know or not, I'm writing a PyPI 2.0, and sometime in the near future i'm going to have a preview.pypi.python.org/simple/ with a whole new codebase that I'm going to try and get people to install against it some to make sure I didn't miss anything23:26
mordreddstufft: yes. I'm very excited about that23:26
mordreddstufft: I could probably even just set up a non-voting job to hammer it constantly and give you a nice stream of feedback :)23:26
dstufftfigure the openstack tests would be a decent data point23:27
mordredwe are evil23:27
dstufft:D23:27
dstufftit won't be behind a CDN or anything for now, and I need to get a *.pypi.python.org SSL certificate still23:27
dstufftbut I almost have the /simple/* api finished23:27
mordredneat!23:27
mordreddstufft: is this replacement something that will be actually runnable elsewhere too?23:27
dstufftIt's working locally, I need to write tests and documentation and finish a few things like Cache-Control headers23:27
dstufftmordred: ideally yes23:27
dstufftthat's the goal anyways23:28
mordreddstufft: neat. I mean, tbh, I still am not sure we really need to do that, since the real purpose of our mirror is just to protect against transient network barf and static files in an apache does fine for that23:28
* mordred wants to make sure we don't go _too_ far in running an alternate universe over here23:28
dstufftright now the only pypi.p.o centric stuff is Fastly integration and that's conditioned on a config change23:29
dstuffts/change/variable/23:29
mordredossum23:29
dstufft(Fastly specific because varnish doesn't have surrogate-keys)23:29
* mordred should go poke devpi again and see if it works yet23:29
dstufftPart of my work with Warehouse (PyPI 2.0) is actually documenting the fucking API23:30
dstufftbecause documentation is a cool thing to have23:30
mordredyup23:30
mordredalso, I'm excited23:30
mordredbecause once warehouse is there23:30
mordredyou can start adding NEW api23:30
dstufftyes :D23:30
mordredlike "o hai, I'm a person, and I want to upload this thing"23:30
dstufftthe upload API is conceivably a thing that could happen sooner rather than later23:31
dstufftsince it's distinct from the download API23:31
dstufftand isn't as big of a problem23:31
dstufftI'm hopefully going to be able to get a PEP to depercate/break ``python setup.py upload`` completely23:31
dstufftand make twine the official uploader23:31
mordredooh. nice23:32
mordredyou know, people are going to be angered23:32
dstufftMostly because sending credentials in plaintext is bad23:32
mordredbecause of $crazy23:32
* mordred eats dinner now23:32
dstufftof course they are, I'm getting good at pissing people off tho :D23:32
dstufftmordred: have fun23:32

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