Friday, 2017-07-28

openstackgerritClint 'SpamapS' Byrum proposed openstack-infra/zuul feature/zuulv3: Github - Require webhook_token  https://review.openstack.org/48824000:15
openstackgerritClint 'SpamapS' Byrum proposed openstack-infra/zuul feature/zuulv3: Github - Require webhook_token  https://review.openstack.org/48824000:26
*** harlowja has quit IRC01:10
openstackgerritMerged openstack-infra/zuul feature/zuulv3: Use mypy to do static type checking  https://review.openstack.org/48816103:58
*** harlowja has joined #zuul04:32
*** jesusaur has joined #zuul05:00
*** harlowja has quit IRC05:28
*** harlowja has joined #zuul05:41
*** harlowja has quit IRC06:48
openstackgerritMerged openstack-infra/zuul feature/zuulv3: Ensure tox-cover is non-voting  https://review.openstack.org/48717307:08
*** amoralej|off is now known as amoralej07:15
*** hashar has joined #zuul08:15
*** openstackgerrit has quit IRC08:18
*** openstackgerrit has joined #zuul08:22
openstackgerritTobias Henkel proposed openstack-infra/zuul feature/zuulv3: Fix dynamic layout with regex approval filters  https://review.openstack.org/48833108:22
tobiashjeblair, clarkb: ^ fixes the deepcopy issue you had a few days ago08:22
tobiashjeblair, clarkb: this bit me today too as soon as I added a username approval filter to the gate08:23
openstackgerritTobias Henkel proposed openstack-infra/zuul feature/zuulv3: Ignore .mypy_cache  https://review.openstack.org/48833208:26
openstackgerritTobias Henkel proposed openstack-infra/zuul feature/zuulv3: Fix dynamic layout with regex approval filters  https://review.openstack.org/48833108:36
openstackgerritMonty Taylor proposed openstack-infra/zuul feature/zuulv3: Update SQL reporter to store results  https://review.openstack.org/48822108:52
mordredlet's see if maybe that doesn't copletely blow up08:52
tobiashmordred: lgtm08:54
tobiashmordred: ups, overlooked something, see review08:59
mordreduhoh. looking09:02
mordredSpamapS: +A on 488240 - but clarkb and I both left inline comments that may be worth following up on09:02
mordredtobiash: oh good call!09:03
tobiash:)09:03
mordredalso - update unit test :)09:03
tobiashmordred: don't know currently if NODE_FAILURE is the longest though09:03
mordredI can just make it a little longer ...09:04
mordredno need to be SUPER short there - it's a varchar after all09:04
tobiashmordred: yepp, no need to be that grasping there ;)09:05
openstackgerritMonty Taylor proposed openstack-infra/zuul feature/zuulv3: Update SQL reporter to store results  https://review.openstack.org/48822109:06
openstackgerritMerged openstack-infra/zuul feature/zuulv3: Github - Require webhook_token  https://review.openstack.org/48824009:09
openstackgerritMonty Taylor proposed openstack-infra/zuul feature/zuulv3: Update docs to indicate app_key is a file  https://review.openstack.org/48833709:10
*** rbergero1 is now known as rbergeron09:17
*** rbergeron has joined #zuul09:17
openstackgerritMonty Taylor proposed openstack-infra/zuul feature/zuulv3: Update SQL reporter to store results  https://review.openstack.org/48822109:30
*** hashar has quit IRC09:42
*** jkilpatr has quit IRC10:34
*** jkilpatr has joined #zuul10:53
openstackgerritTristan Cacqueray proposed openstack-infra/nodepool feature/zuulv3: Implement a static driver for Nodepool  https://review.openstack.org/46862411:43
openstackgerritTristan Cacqueray proposed openstack-infra/nodepool feature/zuulv3: Implement an OpenContainer driver  https://review.openstack.org/46875311:43
openstackgerritTristan Cacqueray proposed openstack-infra/nodepool feature/zuulv3: Move the fakeprovider module to the fake driver  https://review.openstack.org/48838311:43
openstackgerritTristan Cacqueray proposed openstack-infra/nodepool feature/zuulv3: Refactor provider config to driver module  https://review.openstack.org/48838411:43
*** hashar has joined #zuul12:29
*** dkranz_ has joined #zuul12:56
jeblairmordred: so.... apparently we're doing type checking14:29
mordredjeblair: yah, I should have been more careful and put a WIP on that14:31
jeblairmordred: so what exactly does it get us?14:32
Shrewsoh, did that merge?14:32
mordredwell - right now it gets us checking of inferred types, which isn't super exciting...14:32
mordredbut the bit that's more cool is that if we add type annotations to method signatures, it will cause those to actually be checked14:33
jeblairmordred: do you have an example of an app that does this?14:34
mordredone sec14:34
jeblairto me, that seems like the real question.  we need to decide if we want to start doing that or not, because the patch as written isn't really a goal in and of itself.14:35
mordredyes - totally agree. the straw man was "being able to add type annotations can help sometimes" - definitely not "we can just run more tools on the current thing"14:37
mordredhttps://github.com/tomchristie/apistar/blob/master/apistar/routing.py#L158 here's an example from a project that decided to jump pretty heavily in to making use of 3.x features14:38
jeblairof course they're backwards :)14:39
mordredjeblair: they want SQL to feel loved :)14:39
jeblairmordred: what does this mean?  initial_types: List[type]=None14:40
mordredthat means that it takes a List which can contain anything that subclasses type - and that the argument initial_types has a default value of None14:42
mordredjeblair: so - you can see in a couple of lines that the things being put into initial_types are classes, not instances14:43
jeblairoh, weird.  it was the =None that i find most confusing.14:44
mordredyah - I agree, that combo is a little strange14:44
openstackgerritMonty Taylor proposed openstack-infra/zuul feature/zuulv3: DNM Random zuul type hint examples  https://review.openstack.org/48844214:45
mordredjeblair: there's a couple of small examples of applying to zuul - I picked a place where it wasn't clear at first on reading what the incoming data type and where it seemed the use of an annotation might communicate something14:47
jeblairmordred: what would the annotation for 'items' look likE?14:47
jeblairit's a list of dicts of (dicts and lists and scalars...)14:48
mordredlet's see ...14:48
mordredjeblair: items: List[Dict[str, Any]]14:51
mordredjeblair: I believe should do the trick14:51
clarkbone thing that bugged me (and I may have misread) was that mypy inferrs Any in the vast majority of cases which isnt really a strong co tract. its like using void* everywhere14:51
*** harlowja has joined #zuul14:51
jeblairmordred: is List[Dict] sufficient, (or List[Dict[]] )?14:51
mordredjeblair: lemme see14:51
mordredjeblair: yes - it seems so14:52
jeblairmordred: also, i know there's static type checking with mypy -- is there any runtime checking in py3 itself?14:53
mordredjeblair: so we should be able to be as clear or as vague as we'd like14:53
mordredthere is not14:53
jeblairokay, so we're not going to end up with "Exception: None passed in as items"14:53
mordredthey have been implemented as informational annotations with the intent of things like mypy being able to process them - or for people to write metaclasses to do so if they want14:53
mordredno - not unless we got really clever with a metaclass somewhere14:53
jeblairthat's never gone well14:54
mordrednope. well - there was that one time14:54
mordredI dont remember why we wrote that metaclass - but I do remember spending an entire day discussing its four lines of code14:54
jeblairi doubt we well ever be as smart as that again14:55
openstackgerritMonty Taylor proposed openstack-infra/zuul feature/zuulv3: DNM Random zuul type hint examples  https://review.openstack.org/48844214:55
mordredjeblair: nope. we definitely won't14:55
mordredjeblair: that adds the items annotation just for reference14:55
jeblairwell, i'm willing to give it a try.  my main concerns are whether it's worth the extra effort, and whether it will be confusing to people or a turn-off (we're not tripping over zuul contributors at the moment, so i don't want to tell folks to go a way more than necessary).   but....14:57
jeblair(oh, and also whether now is the best time to make changes like this)14:58
jeblairif we're willing to say this is an experiment, let's try it out, see if it annoys or confuses us, see if we think it's worthwhile, don't feel compelled to immediately use it 100% and feel free to at some point in the future, rip it all out...  okiedokie.  i *do* like static type checking and miss it greatly.14:58
jeblairi think the mostly opt-in approach will help with that.14:59
mordredjeblair: ++ agree with all of that15:04
Shrewsunless folks explicitly add the comments for types, it shouldn't affect our current workflow, right?15:06
Shrewsor use the new func/method definitions15:07
mordredShrews: that is correct15:08
mordredyou'll need to -r your tox -epep8 run the next time to rebuild that and pick up the new depend - but other than that, no change15:08
clarkbunless you break some existing contract or inferred typing15:08
clarkbtox will pep8 job15:08
clarkb*fail pep815:08
mordredyah. and in those cases it'll hopefully be welcome information15:09
mordredjeblair, clarkb: https://review.openstack.org/#/c/488337/ doc update based on yesterday's learning about what the app_key option is15:10
*** olaph has quit IRC15:16
*** olaph has joined #zuul15:20
openstackgerritMerged openstack-infra/zuul feature/zuulv3: Update docs to indicate app_key is a file  https://review.openstack.org/48833715:21
jeblairtobiash: thanks for finding the approval deepcopy thing!15:23
pabelangermorning!15:25
jeblairmordred: left a question on 488221 (with a -1 that can be inverted depending on the answer)15:28
SpamapSmordred: doh, one less 0. :-P15:30
jeblairmordred, pabelanger: https://review.openstack.org/488216 pep8 job failed with a POST_FAILURE.  (note that the upload did happen, it was an earlier post playbook -- unittests/post which failed) here's the executor logs: http://paste.openstack.org/show/616878/  and here's the upload: http://logs.openstack.org/16/488216/3/check/tox-pep8/c1d1c26/15:33
openstackgerritMerged openstack-infra/zuul feature/zuulv3: Ignore .mypy_cache  https://review.openstack.org/48833215:33
openstackgerritMerged openstack-infra/zuul feature/zuulv3: Fix dynamic layout with regex approval filters  https://review.openstack.org/48833115:33
mordredjeblair: hrm. that's a great question15:33
jeblairmordred, pabelanger: does the error "Ansible output: b'ERROR! A worker was found in a dead state'" mean anything to you?15:34
mordredjeblair: not even a little bit15:34
jeblairlib/ansible/plugins/strategy/__init__.py:                raise AnsibleError("A worker was found in a dead state")15:35
mordredjeblair: ah - so, that's likely going to have something to do with the ssh subprocesses15:35
pabelangerjeblair: I haven not seen that before15:37
jeblairmordred, pabelanger: http://logs.openstack.org/16/488216/3/check/tox-pep8/c1d1c26/job-output.json  it looks like the job output json does not include that playbook or anything after15:37
jeblairdouble check me on that15:38
pabelangerya, I notice that last week, some playbooks were not logged into json15:38
mordredgit.openstack.org/openstack-infra/zuul-jobs/playbooks/tox/post is the last one it ran15:44
mordredoh - yeah, that makes sense15:45
mordredif ansible-playbook aborts, the callback is never going to get the on_stats event15:45
tobiashjeblair: yeah, it broke my whole deployment as soon the approval username was set15:46
tobiashjeblair: and sorry for +3ing the static checker too quick, this probably would have required more consensus15:47
jeblairmordred: i guess the only playbook after that one is log uploading, which isn't there for obvious reasons.  so i guess if we had one more post playbook, it probably would have been there.  just coincidence that happened to be the last.15:47
jeblairtobiash: no worries.  we can always revert stuff like that.  but in this case, i think we can move forward and achieve consensus retroactively (or revert later)15:48
*** harlowja has quit IRC15:51
*** amoralej is now known as amoralej|off16:04
SpamapSzomg coffffffffffeeeeeeeeeeeeeeee16:09
openstackgerritJames E. Blair proposed openstack-infra/zuul feature/zuulv3: Ensure ref-updated jobs run with their ref  https://review.openstack.org/48821616:32
openstackgerritJames E. Blair proposed openstack-infra/zuul feature/zuulv3: Ensure ref-updated jobs run with their ref  https://review.openstack.org/48821616:38
*** openstack has joined #zuul16:46
jeblairalternatively, if folks aren't interested in reviewing docs changes, you could tell me to +3 my own changes16:46
jeblairmordred, pabelanger, clarkb, SpamapS: ^16:47
clarkbjeblair: why is http://docs-draft.openstack.org/80/487580/2/check/gate-zuul-docs-ubuntu-xenial/32d8aab//doc/build/html/user/config.html#index-0 preferable to #Pipeline ?16:48
clarkbI think that comes from the switch to using index::\n single: Pipeline ?16:48
jeblairclarkb: i don't think it is preferable.  we can drop it16:50
jeblairclarkb: fixed locally.  i'll push it up after a rebase after the 2 parents merge since i need to resolve some conflicts on the children anyway.16:52
clarkbok16:52
*** harlowja has joined #zuul16:54
*** harlowja_ has joined #zuul16:55
pabelangerjeblair: sure, let me look now16:57
*** harlowja has quit IRC16:59
mordredjeblair: I like reviewing docs patches - but also I'll say I'm completely comfortable with you self-approving docs patches too17:00
*** hashar has quit IRC17:05
openstackgerritPaul Belanger proposed openstack-infra/zuul feature/zuulv3: Fix GithubConnection logging name  https://review.openstack.org/48853717:07
pabelangerjeblair: mordred: ^ I believe that fixes our debug logging for github connection17:07
jeblairoh the docs patches failed with this: 2017-07-28 16:48:01.730004 | zuul/sphinx/zuul.py:92: error: Need type annotation for variable17:09
jeblairso i guess i'll rebase the whole stack and figure that out17:10
pabelangerneat, openstack-zuul update the PR to pending: https://github.com/gtest-org/ansible/pull/117:25
pabelangermordred: ^key worked properly17:25
mordredpabelanger: woot!17:26
pabelangerYa, exciting17:26
jeblairapparently you can only see that if you're signed in?17:26
pabelangerya, it looks that way17:26
pabelangerwonder if that can be changed17:26
mordredpabelanger, jeblair: I notice 2 bugs or possibilities for improvement17:27
clarkbjeblair: I wonder if non authenticed users get heavily cached content?17:28
mordred1) the "Details" link in the pending job status is for "https://zuulv3.openstack.org/" - which isn't a thing17:28
mordredI _think_ that might be due to a setting in the app settings - but I wonder if it's a thing the plugin can report instead17:28
jeblairmordred: that may be the status-url which i asked pabelanger to leave blank for starters; i wanted to see the default17:28
jeblairbut bonnyci configures it to be a status page deep link17:29
mordredjeblair: gotcha. so - in the app config on github there is a url for the service, which I believe is configured to https://zuulv3.openstack.org/ right now17:29
mordredso the default seems to be to use the value from the app config page17:29
jeblairmordred: *nod*17:29
pabelangerYa, we are running defaults from zuul ATM17:30
jeblairmordred: i'm hoping we can work out a zuul github driver default so we don't have to set it in the pipeline config17:30
mordredjeblair: ++17:30
jeblairi'm not sure if we have enough info yet to do that automatically, but i assume we will at least by the time we get all the web stuff ironed out17:30
mordredjeblair: so - the thing in the app config that's set to that url is "User authorization callback URL"17:30
mordredwith a description of "The full URL to redirect to after a user authorizes an installation."17:31
mordredwhich doesn't seem to be the thing that this is17:31
pabelangermordred: for now maybe we set openstack-zuul URL to http://zuulv3.o.o/status17:31
mordredso I'm not 100% sure why it would use that17:31
jeblairmordred: it may also be a default in zuul, i can't remember17:31
mordredah - nod17:31
mordredmaybe that's it - it doens't make sense for that value in github to be used in that location17:32
jeblairmordred: what else was on your list?17:32
mordredjeblair: I was going to suggest the bonny deep-link :)17:32
*** openstackgerrit has quit IRC17:33
jeblaircool, i guess we should try that now :)17:33
mordredit felt like, from that location, what I expected when I clicked on "details" would be the status details for that change, not the whole status page17:33
pabelangercool, left comment about failure17:34
pabelangerURL to logs was correct17:34
*** openstackgerrit has joined #zuul17:38
openstackgerritJames E. Blair proposed openstack-infra/zuul feature/zuulv3: Provide nicer index entries for config items  https://review.openstack.org/48758017:38
openstackgerritJames E. Blair proposed openstack-infra/zuul feature/zuulv3: Add zuul:value sphinx directive  https://review.openstack.org/48753017:38
openstackgerritJames E. Blair proposed openstack-infra/zuul feature/zuulv3: Use default sphinx theme and index attributes  https://review.openstack.org/48723917:38
openstackgerritJames E. Blair proposed openstack-infra/zuul feature/zuulv3: Remove email-filter requirement  https://review.openstack.org/48760717:38
openstackgerritJames E. Blair proposed openstack-infra/zuul feature/zuulv3: Use zuul config sphinx directives for pipeline  https://review.openstack.org/48760417:38
openstackgerritJames E. Blair proposed openstack-infra/zuul feature/zuulv3: Cleanup pipeline requirements  https://review.openstack.org/48761817:38
jeblairokay that's the stack rebased and should by mypy clean17:38
openstackgerritJames E. Blair proposed openstack-infra/zuul feature/zuulv3: Fix gerrit label capitalization in docs  https://review.openstack.org/48855017:45
openstackgerritJames E. Blair proposed openstack-infra/zuul feature/zuulv3: Fix gerrit label capitalization in docs  https://review.openstack.org/48855017:48
mordredjeblair: did we get a mypy break in it?17:48
jeblairmordred: no, just grumped about an empty initializer.  i removed it.17:48
jeblairit was something that other domains use, but the zuul domain doesn't use yet, but i had gone ahead and put it in anyway for reference.17:49
mordrednod. I'm interested as we hit grumps from it how often they're useful vs. nitpicky/lame17:50
jeblairmordred: this is along the lines of "unused variable".17:50
jeblairso, not exceptionally objectionable, but not that useful.17:50
jeblair(maybe not the best comparison -- unused variable is actually usually pretty useful because it may indicate a logic error; this was just an unused facility of a class)17:52
tobiashjeblair: I just discovered a glitch while playing with mypy:17:54
tobiashjeblair: http://git.openstack.org/cgit/openstack-infra/zuul/tree/zuul/driver/gerrit/gerritconnection.py?h=feature/zuulv3#n71417:54
tobiashjeblair: this is calles with a project object but assumes a string17:54
tobiashjeblair: it works by accident though as the project object has a __str__ methog which does the right thing17:54
jeblairmordred: mypy scored a point ^ :)17:55
tobiashjeblair: now I'm not sure how far I should add the type annotations with the fix for that17:56
jeblairi think i'm getting pretty close with the ref-updated fix.  it's currently failing some github tests becaues, in fact, the github test just makes up some random shas which aren't in the repo :)17:57
jeblairtobiash: maybe push up what you have and we'll see what it looks like?17:58
clarkbI think you give the function a signature then update the callers to pass a string not a project object?18:02
openstackgerritTobias Henkel proposed openstack-infra/zuul feature/zuulv3: Use project object in _uploadPack in gerrit driver  https://review.openstack.org/48856018:09
tobiash^ did minimal annotations for the start as this is mainly a bugfix18:09
pabelangerDoes git-review for github PRs exists?18:11
pabelangeror do people just keep using the webui?18:11
*** openstack has joined #zuul18:15
mordredoh - no, I don't really care about <3.518:16
mordredbut other people could overrule me on that18:17
mordredthe comment version for variables/attributes is needed in 3.5 because variable annotations don't hit until 3.618:17
clarkbmordred: you avoided using the 3.5 only features at least18:17
clarkboh I thouht they were in 3.518:17
mordredno - that's 3.618:17
tobiashdidn't we have already some py35 stuff (in zuul-web)?18:17
mordredand we do need to avoid 3.6 only features (sadly, there's a TON in 3.6 I like a lot - like being able to tell python that keyword arguments should never be able to be used positionally)18:18
clarkbmordred: python docs say 3.5?18:18
mordredclarkb: for variable annotations? (not function annotations)18:18
clarkbhttps://docs.python.org/3.5/library/typing.html18:18
mordredclarkb: yah - that's all function annotations18:19
mordredhttps://www.python.org/dev/peps/pep-0526/#abstract explains the difference18:20
clarkbI kind of think if we have to go the comment route for 3.5 anyways for a subset of cases then we should just be consistent and support other versions while we are at it18:20
mordredclarkb: well - I thnk the  most common places where they're useful is in the parameters .. "what did this function take"18:21
mordredBUT - I could see doing it comment-style everywhere as well18:22
clarkbmordred: yes and that is supported in the comment method as well18:22
mordredclass Example:18:22
mordred    def method(self, lst, opt=0, *args, **kwargs):18:22
mordred        # type: (List[str], int, *str, **bool) -> int18:22
mordredisn't terrible18:22
clarkbthe other method of arg per line isn't bad either18:22
clarkbthough it will add a lot of lines to code18:22
clarkbalso maybe its just me but **bool makes no sense to me. kwargs should need two types because its a Dict?18:23
clarkbis the key side implicitly string because it will always be string?18:24
mordredI honestly don't know what the heck **bool is trying to communicate18:28
clarkbI'm guessing its equivalent to Dict(str, bool) ? since function arg names will always be str?18:29
clarkbbut its confusing18:29
mordredclarkb: ah - no - it's the expected type for _one_ of the values18:30
mordredhttps://www.python.org/dev/peps/pep-0484/#arbitrary-argument-lists-and-default-argument-values18:30
mordredoh - nope - you were right18:30
mordredthere is another doc that is wrong18:30
openstackgerritTobias Henkel proposed openstack-infra/zuul feature/zuulv3: Use project object in _uploadPack in gerrit driver  https://review.openstack.org/48856618:32
*** jkilpatr has quit IRC18:32
tobiash^ is the alternative comment only version18:32
mordredoh - so - the downside to the comment only versoin ...18:32
mordredis that pep8 doesn't know the imported type has been used - so it emits an error for unused import18:33
openstackgerritMerged openstack-infra/zuul feature/zuulv3: Use default sphinx theme and index attributes  https://review.openstack.org/48723918:33
mordredwhereas I believe that does not break if it's in the type annotation directly18:33
tobiashmordred: correct18:33
clarkbbah and the mypy docs say you have to have the import even if it is comment only18:33
mordredyah18:33
openstackgerritMerged openstack-infra/zuul feature/zuulv3: Add zuul:value sphinx directive  https://review.openstack.org/48753018:34
mordredso I say we do direct annotations for arguments so that we have the least amount of effort serving the pep8 gods18:34
openstackgerritMerged openstack-infra/zuul feature/zuulv3: Provide nicer index entries for config items  https://review.openstack.org/48758018:34
openstackgerritMerged openstack-infra/zuul feature/zuulv3: Use zuul config sphinx directives for pipeline  https://review.openstack.org/48760418:34
clarkbI dunno I still think its worthwhile to not further restrict python versioning for something that is currently experimental ish18:35
clarkbI would have to completely rebuild my test bed18:35
clarkbmaybe I already have to with the last patch? but I thought it was comment annotation only18:35
tobiashI'm fine with both but have a slight preference to annotations to arguments. This way the arguments and annotations directly match visually together especially for multiline function declarations.18:35
clarkbtobiash: mypy supports comments in multiline function declarations18:36
mordredclarkb: I mean- we don't test 3.4 so I'm not super comfortable declaring support for it anyway - and it's a new release so we don't really have legacy folks to be concerned with18:37
mordredclarkb: I don't feel STRONGLY one way or the other18:37
mordredmostly just listing my various thoughts18:37
clarkbif we didn't have to use comments anyways for 3.5 on variables I would agree18:37
mordredI'm happy either way we go18:37
clarkbbut we do and have the same exact pep8 problem there18:37
clarkbsince we don't avoid any of the overhead we may as well just make it work in more places18:38
mordredyah. I guess I'm mostly arguing that I doubt we'll annotate many variables18:38
mordredthe one I had to do was just becaue the inferred type was wrong (variable in base class was initialized to None so the inferred type was NoneType but it should have been str)18:39
mordredmethod/function signatures and returns seem to me to be the most likely place any of this shows up frequently for us as a place we'll desire putting things18:40
tobiashok, so now I have -1 on both patches ;) , so where do we want to go?18:40
mordredI mean - I say all that - but I'm gonna TOTALLY add this to shade with comment-based annotations - so this is more a "one feels better to me but the other is totally fine" thing18:40
mordredtobiash: I think we get jeblair to tie-break18:41
tobiash:)18:41
*** openstack has joined #zuul18:46
mordredjeblair: maybe let's just generally say "don't use variable annotations unless absolutely necessary"18:47
jeblairya.  for now at least.18:47
mordred++18:47
tobiashI think they are just necessary when initialized with [] or {} or similar18:48
clarkbtobiash: or the None situation that mordred ran into18:48
tobiashjepp18:48
tobiashwhen initializing with a concrete type or function return value the type seems to be autodetected18:49
*** jkilpatr has joined #zuul18:49
clarkbof course you could in some of the none situations assign to eg "" or 0 or other falsey matching value18:51
openstackgerritDavid Shrewsbury proposed openstack-infra/zuul feature/zuulv3: Implement autohold  https://review.openstack.org/48669219:01
jeblairShrews: there's no WIP on that!!!!11one1!19:03
Shrewsjeblair: oh yeah. i mentioned things in #-infra19:03
Shrewstoo many channels19:03
Shrewsat least it was an openstack channel  :)19:03
Shrewsjeblair: so, one thing about that is i pulled the node state from zuul.model rather than repeat the definition in zuul/zk.py. Once this merges, I'd like to do the same for the other states.19:08
jeblairShrews: ok, i'll keep that in mind as i review19:10
Shrewshrm, zuul says the test fails to pass, but passed locally19:13
Shrewsi can at least fix the pep8 fail19:15
openstackgerritDavid Shrewsbury proposed openstack-infra/zuul feature/zuulv3: Implement autohold  https://review.openstack.org/48669219:16
openstackgerritMerged openstack-infra/zuul feature/zuulv3: Remove email-filter requirement  https://review.openstack.org/48760719:16
openstackgerritMerged openstack-infra/zuul feature/zuulv3: Cleanup pipeline requirements  https://review.openstack.org/48761819:17
openstackgerritMerged openstack-infra/zuul feature/zuulv3: Fix gerrit label capitalization in docs  https://review.openstack.org/48855019:18
Shrewsjeblair: aha. rebasing on the latest code i now get the error for the new test19:25
ShrewsKeyError: 'verified'19:26
Shrewswonder if i'm missing something from my yaml19:27
Shrewshttp://logs.openstack.org/92/486692/5/check/gate-zuul-python35/ccc094c/console.html#_2017-07-28_19_24_24_29001019:30
tobiashShrews: the labels are now case sensitive19:37
tobiashShrews: you have to spell it 'Verified'19:38
Shrewstobiash: oh. that was, indeed, the issue. thx19:40
openstackgerritDavid Shrewsbury proposed openstack-infra/zuul feature/zuulv3: Implement autohold  https://review.openstack.org/48669219:40
openstackgerritTobias Henkel proposed openstack-infra/zuul feature/zuulv3: Add project related type hints to gerritconnection  https://review.openstack.org/48859319:59
*** olaph has quit IRC20:20
openstackgerritMerged openstack-infra/zuul feature/zuulv3: Monitor job root and kill over limit jobs  https://review.openstack.org/48590220:22
*** olaph has joined #zuul20:22
mordredpabelanger: fwiw, I needed to make a patch to os_server for ansible/ansible - so I also submitted it as a PR to gtest-org/ansible so that we'd have a PR in there that actually testing against shade would be nice for20:23
mordredpabelanger: https://github.com/gtest-org/ansible/pull/320:24
pabelangermordred: cool, I'll look at shade shortly20:28
mordredpabelanger: yah - I'm still down the stack a bit from it myself20:33
jeblairShrews: i left some comments ranging from nits through things i think we should do in this or a future patch, to something i'm pretty sure we should do before landing that patch.  they should be annotated.  :)20:41
jeblairShrews: i think your state variable change sounds good20:41
jeblairShrews: and, reading tobiash's comments, looks like we have 2 votes for updatable counts.  :)20:41
Shrewsjeblair: awesome. will take a gander20:42
jeblairtobiash: did you see comment on https://review.openstack.org/486227 ?20:45
Shrewsjeblair: all make sense. i'll make those changes. i also like using a 0 value to mean remove it20:45
jeblairShrews: cool20:46
mordredjeblair: see scrollback to you in #openstack-infra20:52
jeblairmordred: ok, so python code then20:53
jeblairmordred: oh!20:53
jeblairyou're talking about singleton arguments20:53
openstackgerritMerged openstack-infra/zuul feature/zuulv3: Fix broken project config in dynamic config test  https://review.openstack.org/48622620:53
mordredjeblair: yup20:54
jeblairmordred: yeah, i think that's fair.  i'm also worn down enough that i'm okay removing those, unless it really makes a difference (like, a recursive algorithm depends on it or something).  this is a step back from my previous position of defending them as long as they were correct.20:54
mordredjeblair: I actually LIKE them for the singleton use case20:55
jeblairya20:55
mordredjeblair: but I think it's also a mistake enough that saying "# notabug singleton usecase"20:55
mordredcan be helpful20:55
mordred(patch coming in a sec for the thing I just accidentally hit)20:56
jeblairi mean, i'm not going to go remove them actively.  just saying if it's borderline ambiguous, maybe not worth the effort to defend.  :)20:56
jeblairmordred: cool20:56
tobiashjeblair: yes, saw it, but didn't yet have time to work on that further21:01
tobiashjeblair: but I tried your suggestion with ProjectTemplateParser._parseJobList21:02
tobiashjeblair: and failed because there not the complete layout is included21:02
tobiashjeblair: but I saw another possibility21:03
openstackgerritMonty Taylor proposed openstack-infra/zuul feature/zuulv3: Replace singleton lists with None defaults  https://review.openstack.org/48867621:04
openstackgerritMonty Taylor proposed openstack-infra/zuul feature/zuulv3: Add an AFS keytab to the bind-mount if it's there  https://review.openstack.org/48867721:04
mordredjeblair: first one is the thing I think was unintentionally doing it21:04
openstackgerritTobias Henkel proposed openstack-infra/zuul feature/zuulv3: WIP Don't ignore inexistent jobs in config  https://review.openstack.org/48875821:06
tobiashjeblair: ^ is my second ides (not finished yet)21:06
tobiashjeblair: that would validate the jobs on every layout generation21:07
tobiashjeblair: I think there are a few tradeoff decisions to be made21:08
tobiashjeblair: lazy validation has less (no) general runtime costs, but only covers jobs that are tried to run21:09
tobiashjeblair: where early validation implies runtime costs and have the risk of breaking overall zuul config when adding new repos or pushing changes through21:11
jeblairmordred: we shouldn't need to put afs into zuul itself i don't think21:11
jeblairmordred: there's a config option to set bubblewrap binds21:11
jeblairmordred: oh, you say you're going to add a generalized system for deployers to bindmount things in.  it already exists.21:14
jeblairof course it's not documented21:15
SpamapSoh yay diskaccounting is happening21:16
mordredjeblair: yay for  not documented!21:18
mordredjeblair: k. I will change that patch to update the docs :)21:19
jeblair++21:19
mordredjeblair: of course, the variable is ro_dirs21:19
mordredand in this case we want to bind-mount a file ... but whatev :)21:20
jeblairmordred: it is already plugged into puppet to, so should just need a system-config change for the puppet side21:20
mordredjeblair: neat!21:20
jeblairmordred: yeah, that was unclear to me, but i tested it the other day and either dir or file works21:20
mordredyup. I just tested the bubblewrap option21:20
clarkbmaybe make it ro_path21:21
jeblairmordred: maybe we should change it to ro_bind and rw_bind21:21
jeblairor path21:21
clarkb(if worried about the confusion)21:21
clarkbbind works too21:21
clarkbro_bind_path :)21:21
jeblairwe're 2/2 for confusing so i think it may be worth it.  :)21:21
mordred++21:21
* mordred does that21:22
jeblairw00t https://pypi.python.org/pypi/zuul-sphinx/0.1.0 exists21:22
pabelangermordred: looks like zuul had some issues with https://github.com/gtest-org/ansible/pull/3 I see some execptions in debug.log. I'll dig into them in a bit and see what is going on21:24
jeblairneat.  one of the scheduler tests verified that we can run post jobs on deleted refs.  it did that by simulating deleting the master branch.21:26
jeblairwith the patch i'm working on, i get the following error:21:26
jeblair2017-07-28 14:25:13,994 zuul.AnsibleJob                  DEBUG    [build: cd33a0ca40b44b63941f3df488fd4922] Sending result: {"error_detail": "Project org/project does not have the default branch master", "result"21:26
jeblair: "ERROR"}21:26
jeblairi think that test may need to be rethought.21:26
jeblairlike -- what did you expect to happen?21:27
openstackgerritMonty Taylor proposed openstack-infra/zuul feature/zuulv3: Change name and document the bind_mount config paths  https://review.openstack.org/48867721:30
mordredjeblair: yah. I agree - that seems like a thing that needs to be rethought :)21:31
jeblairmordred, clarkb: now that i see that, i think making it plural might be important.  so "trusted_ro_paths".  ?21:32
mordredjeblair: sure - can do21:32
jeblair(sorry)21:33
tobiashjeblair: maybe we can discuss on monday about the pros and cons of lazy and eager validation of job existence21:35
openstackgerritMonty Taylor proposed openstack-infra/zuul feature/zuulv3: Change name and document the bind_mount config paths  https://review.openstack.org/48867721:36
tobiashhave to eod now21:36
tobiashcya21:36
jeblairtobiash: ok have a good weekend!21:36
tobiashu221:36
mordredjeblair: remote:   https://review.openstack.org/488859 Change bind mount option names to match zuul21:37
mordredpiddle. that's totally not going to work because CI21:37
mordredsilly testing21:37
jeblairmordred: needs pluralization21:37
clarkboh I just approved21:37
mordredalso needs expand/contract21:37
mordredit won't pass the gate21:37
clarkb48867721:38
mordredwe consume that parameter in site.pp21:38
jeblairmordred: ack21:38
clarkbso we need to support both temporarily?21:38
jeblairclarkb: i think 77 is fine, we can push through on the puppet stuff21:38
jeblairclarkb: yup21:38
jeblairbtw, a likely dvorak typo for pull_request is purr_request.  just sayin.21:47
mordredjeblair: NICE21:54
openstackgerritJames E. Blair proposed openstack-infra/zuul feature/zuulv3: Ensure ref-updated jobs run with their ref  https://review.openstack.org/48821622:01
jeblairmordred: https://review.openstack.org/486698 wants you22:03
mordredactually, https://review.openstack.org/#/c/485897 wants in first - I'll rebase 486698 on top of it22:05
openstackgerritMonty Taylor proposed openstack-infra/zuul feature/zuulv3: Log an extra blank line to get space after each skip  https://review.openstack.org/48669822:06
mordredk. those no longer conflict22:06
openstackgerritMerged openstack-infra/zuul feature/zuulv3: Add spacer line after loops  https://review.openstack.org/48589722:16
openstackgerritMonty Taylor proposed openstack-infra/zuul feature/zuulv3: Add a short name to the project in the inventory  https://review.openstack.org/48887722:22
openstackgerritMerged openstack-infra/zuul feature/zuulv3: Log an extra blank line to get space after each skip  https://review.openstack.org/48669822:23
openstackgerritMonty Taylor proposed openstack-infra/zuul feature/zuulv3: Change name and document the bind_mount config paths  https://review.openstack.org/48867722:30
mordredjeblair, clarkb: I missed a unittest before ^^22:31
jeblairmordred: +322:33
openstackgerritMonty Taylor proposed openstack-infra/zuul feature/zuulv3: Add a short name to the project in the inventory  https://review.openstack.org/48887722:35
mordredjeblair: huzzah!22:36
jeblairmordred: ah just caught myself!  i +2d your change then remembered docs.  vars are documented in doc/source/user/jobs.rst22:40
mordredjeblair: oh!22:43
openstackgerritJames E. Blair proposed openstack-infra/zuul feature/zuulv3: Remove zuul:configobject  https://review.openstack.org/48888622:48
openstackgerritMonty Taylor proposed openstack-infra/zuul feature/zuulv3: Add a short name to the project in the inventory  https://review.openstack.org/48887723:20
mordredjeblair: this time with docs!23:20
jeblairmordred: w00t.  re+223:23

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