Monday, 2017-04-03

*** jamielennox|away is now known as jamielennox01:06
*** persia has quit IRC04:17
openstackgerritTobias Henkel proposed openstack-infra/zuul feature/zuulv3: Change mutex to counting semaphore  https://review.openstack.org/44256305:51
*** isaacb has joined #zuul06:24
*** bhavik1 has joined #zuul07:00
*** bhavik1 has quit IRC07:02
*** hashar has joined #zuul07:31
*** hashar has quit IRC07:36
*** hashar has joined #zuul07:42
openstackgerritDirk Mueller proposed openstack-infra/nodepool master: Remove link to modindex  https://review.openstack.org/41549607:50
*** bhavik1 has joined #zuul08:02
*** openstackgerrit has quit IRC08:03
*** bhavik1 has quit IRC08:39
*** hashar_ has joined #zuul08:52
*** hashar has quit IRC08:55
*** hashar_ is now known as hashar08:56
*** hashar is now known as hasharLunch11:04
*** adam_g has quit IRC11:45
*** adam_g has joined #zuul11:47
*** hasharLunch is now known as hashar11:52
*** adam_g has quit IRC12:35
*** adam_g has joined #zuul12:36
*** nt has quit IRC13:34
*** isaacb has quit IRC14:01
*** openstackgerrit has joined #zuul14:06
openstackgerritMerged openstack-infra/nodepool feature/zuulv3: Fix debian-jessie settings for devstack  https://review.openstack.org/45249114:06
openstackgerritMerged openstack-infra/nodepool feature/zuulv3: Remove unused timing constants  https://review.openstack.org/45077014:07
jeblairpabelanger: i'm happy to talk about timedatabase when you're ready14:27
openstackgerritMerged openstack-infra/nodepool master: Remove link to modindex  https://review.openstack.org/41549614:50
*** hashar has quit IRC15:19
*** nt has joined #zuul15:30
jeblairrbergeron, Shrews: (cc clarkb) there was a person in #openstack-infra who is running into problems with nodepool documentation.  i think it's an instructive case because the actual nodepool documentation doesn't explain what's going on.  we have some infra-specific documentation that touches on it, but it still doesn't explain much (and when this person tried to follow that, they got themselves more confused because their problem didn't match ...16:42
jeblair... the sort of problem we typically have in infra).  at any rate, i think the sort of "this is what the builder does and how it works and these are what all the commands do" documentation is one of the things we're missing.  i don't know if that's on the agenda for the doc work you're doing.  if it's not, i'll be happy to write it, though i'm not going to get to it right away.16:42
openstackgerritClint 'SpamapS' Byrum proposed openstack-infra/zuul feature/zuulv3: Re-enable test_queue_rate_limiting  https://review.openstack.org/45283516:51
SpamapSjeblair: ^^ do you have a minute to make a quick sanity check of the zuul.yaml file I ported there? The dependencies part is new for me, and also the hold-following-jobs doesn't seem to be working (builds ends up with all the jobs)16:52
SpamapShold-following-changes I mean16:52
SpamapShrm maybe that's not what I thought it was not that I get it out of my head16:52
SpamapSoh that seems right n/m16:53
jeblairSpamapS: will do in just a few.  i'm finishing up poking at jesusaur's change16:56
SpamapSjeblair: thanks!16:56
jeblairSpamapS: i think the word "dependencies" and everything under it need to be indented an extra step.17:07
SpamapSoh derp17:07
SpamapSI screw that up in yaml a lot17:08
SpamapSlooks visually right-ish17:08
SpamapSbut definitely doesn't produce the desired result :-P17:08
jeblairyeah, I think this is something we can/should check for in configparser.  it shows up as two keys inside of a dictionary, with one of them having a value of None.  so I bet we can detect it.17:09
SpamapSAnd the other one has a list as the value17:09
SpamapSthanks for the extra eyes17:09
SpamapSthat was in fact it (also didn't need hold-following-changes .. that was cargo cult fail)17:10
openstackgerritClint 'SpamapS' Byrum proposed openstack-infra/zuul feature/zuulv3: Re-enable test_queue_rate_limiting  https://review.openstack.org/45283517:10
jeblair(this is also why i prefer the "always indent" style of yaml indentation, and we use it for all the documentation and examples -- i think knowing when it's optional vs required to indent yaml is an advanced skill :).  i should write that up in the dev docs.17:15
SpamapSjeblair: I do wonder if there's room for something between yaml's flexibility and json's rigidity/non-readability.17:17
SpamapSPerhaps a yamlfmt would solve that.17:17
SpamapSjust "run this on save of any yaml file"17:17
openstackgerritClint 'SpamapS' Byrum proposed openstack-infra/zuul feature/zuulv3: Re-enable test_queue_rate_limiting_dependent  https://review.openstack.org/45286417:17
mordredSpamapS: well, I don't think actual yamlfmt sould solve it for us, since it does the opposite of the zuul yaml style. but it should be possible to write a yamlfmt that does emit zuul-style yaml17:41
mordred(assuming, of course, that by yamlfmt you mean https://github.com/mmlb/yamlfmt - which you might not)17:41
SpamapSoh there's already a yamlfmt?17:43
SpamapSI just made that up17:43
mordredthe underlying library that yamlfmt wraps, ruamel.yaml, supports keyword arguments for setting indent style - so doing that as "indent=4, block_seq_indent=2" should get the zuul format (it's the block_seq_indent=2 that is the important part)17:45
*** jamielennox is now known as jamielennox|away17:50
SpamapSI will say, once I tied rustfmt to "run this whenever I save a rust file", I stopped noticing the differences and have just sort of learned the proper formatting by osmosis.17:50
SpamapSbut this would be harder to setup17:51
SpamapS"when I'm yaml'ing for zuul..."17:51
mordredyah. for me that's honestly why gate jobs are personally helpful - I learn from the feedback loop and can _usually_ follow it for the most part in a given codebase, but if I get it wrong a friendly robot tells me and then I improve for next time17:55
mordredI've thought a format-on-save tool would be pleasing - but I have not found any such tools that can _emit_ code like I want it to look - whereas having tools that reject bad code for some reason seems easier :(17:56
clarkbI don't like it when tools magically fix things too17:58
SpamapSmordred: well ultimately the thing that finds bad code should be able to produce good code instead of nagging17:58
mordredSpamapS: one would certainly think so17:59
clarkbif you looked at the jenkins code base a couple years ago it was clearly edited by people with magical editor settings and was unreadable without them17:59
mordredSpamapS: but so far I have not found one that does so well for python17:59
mordredor, let me rephrase - I have not found one for python that I can bend to match _my_ preferences properly, thus I find all of them unusable :)17:59
SpamapSYeah for python I just have the vim-flake8 plugin18:00
SpamapSf8 ... iterate on quickfix.. save18:00
mordredclarkb: ++ wow that stuff is hard to deal with18:00
mordredSpamapS: ++18:00
SpamapSAlso rustfmt is special. Because basically every piece of code you will see already had it run on it.. you never learn any other habit.18:01
SpamapSso it feels less like magic18:01
SpamapSit's too late for python and yaml to do that18:01
mordredyah - also, go and rust both started life out with this in mind18:01
mordredyup18:01
mordredI mean, python started us out with enforced indentation...18:02
mordredso you will never see a python program with incorrect indentation :)18:02
SpamapSYeah, python is already pretty good even when it is bad.18:02
mordredyup18:02
SpamapSyaml tho..18:02
SpamapSzomg have I seen bad yaml18:02
mordredleaving us to quibble over things like visual or non-visual indentation styles18:02
openstackgerritJames E. Blair proposed openstack-infra/zuul feature/zuulv3: Perform pre-launch merge checks  https://review.openstack.org/44627518:05
jeblairjesusaur: ^ i pushed up a new patchset18:06
jesusaurjeblair: cool, i'll take a look18:06
jeblairjesusaur: i was going to just leave comments, but it would have been gnarly and wasteful, so i'm doing this and i'll go leave comments on the diff to make sure i explain18:07
SpamapShrm, test_crd_check_transitive is not cooperating. :-P18:07
*** harlowja has joined #zuul18:12
jeblairjesusaur: okay, i left explanatory comments on PS16.  so if you do a side-by-side diff from PS16 to PS17, it will make the most sense.  let me know if it does, in fact, make sense.  :)18:23
mordredjeblair: if it doesn't make sense, should he also let you know that? :)18:24
jeblairmordred: he should let you know :)18:24
mordredjeblair: I walked right in to that one18:25
jesusaurjeblair: yeah, your comments on ps16 and comments in the tests all make sense :) thanks for fixing that up18:30
jeblairjesusaur: thank you :).  mordred: you're off the hook.18:40
mordredTHANK GOD18:42
jesusauralso, WHOO ALL THE (py27) TESTS PASS!18:42
jeblairjesusaur: i think before too long we need to change how the executor constructs git repos -- i think we're going to want to build on this change to save the exact git shas that the initial merge (triggered by the scheduler) uses for a change, and then pass those to the executor so it uses them.18:44
jeblairjesusaur: mostly we should do this so that jobs run by different executors run with exactly the same git repo content.  the racy nature of the current system means they might not.18:45
jeblairjesusaur: but it will also have the effect of making it so that an executor should never have a merge failure (so that test will end up changing or being removed.  but it's how things behave right now, so it's a good test.)18:46
jesusaurjeblair: yeah, i can see some benefit from passing the merge sha around to be sure everything is using the exact same version of the repo18:52
*** hashar has joined #zuul19:09
pabelangerjeblair: okay, back at desk. Regarding TimeDataBase(), what are your thoughts on hashing the Job objection in some matter, then using that as the file we store on disk?  I am assuming we can make the Job objection unique19:27
pabelangerjeblair: I was also looking into dogpile.cache, but I am not sure that is the right path19:30
*** harlowja has quit IRC19:37
jeblairpabelanger: i think the unique key for this is probably 'job name, project, branch'19:42
pabelangerjeblair: tenant also?19:43
jeblairpabelanger: yes19:45
pabelangerjeblair: k, any preference on how to create the file on disk? concat, hash?19:45
jeblair[thinking]19:50
clarkbare you trying to persist the database?19:53
jeblairpabelanger: how about deep directories?  .../tenant_name/connection_name/project_name/branch_or_ref_name/job_name.db  (branch_or_ref_name may have '/' in it, making more directories; that should be okay).19:53
clarkbI wouldn't use dogpile for something that needs to persist19:53
pabelangerright, we only persist data over 10 runs19:55
pabelangerjeblair: sure, I can start with that19:55
jeblairpabelanger: probably should double check that the path we end up with is a subdirectory of the root, just in case someone manages to do something tricky with "../" in a branch name or somesuch19:56
jeblair(or job name)19:56
pabelangerack19:57
clarkbpath == os.path.abspath(path)19:59
*** jamielennox|away is now known as jamielennox20:05
mordredclarkb: you need realpath too20:26
mordredto expand fun symlink tricks20:27
*** harlowja has joined #zuul20:53
jesusaurhrm, it looks like the tox-linters zuul job may not be working as expected?20:59
jesusaurI see tracebacks and then 'commands succeeded' http://zuulv3-dev.openstack.org/logs/5142710d32a842e782a669414ac16637/console.log20:59
openstackgerritK Jonathan Harker proposed openstack-infra/zuul feature/zuulv3: Perform pre-launch merge checks  https://review.openstack.org/44627521:00
clarkbjesusaur: that looks like a docs job21:02
clarkband if I am guessing we don't install all the deps to the venv tox target so autodoc fails to import21:03
clarkbhrm tox env doesn't override deps so it should get all the listed ones at least21:04
jesusauroh, you're right, tox-linters and tox-docs both run the same thing21:06
pabelangero.021:06
pabelangerthat doesn't sound right21:06
* jesusaur was wondering why tox-linters didn't catch a pep8 failure21:06
jesusaurpabelanger: nope, it sure doesn't21:06
pabelangerha21:07
pabelangerI see the issue21:07
jesusaurin .zuul.yaml?21:07
pabelangercopy pasta fail21:07
pabelangerya21:07
jesusauryep21:07
clarkbboth jobs run the same playbook21:07
clarkbbut also should figure out why autodoc is mad21:08
jesusauroh, so 'run:' refers to a playbook?21:08
pabelangerline 34 should be : run: tox/linters21:08
pabelangerjesusaur: ya21:08
jesusaurok, i see that now21:08
jesusauri'll write up a quick change for that21:09
pabelangerI'd be in favour of making pre-run, run, post-run support file extensions. I think it would make it more readable to users21:10
clarkblooks like the docs issues are old code autodoc directives that weren't cleaned up when zuul got refactored21:10
* clarkb pokes at cleaning that up21:10
openstackgerritK Jonathan Harker proposed openstack-infra/zuul feature/zuulv3: Make tox-linters run the tox/linters play  https://review.openstack.org/45295321:11
clarkboh boy that actually means documenting all of zuuls new internals, I think I am not best person to do that21:11
jesusaurpabelanger: care to give that a review^?21:11
clarkbjeblair: doc/source/datamodel.rst is the area needing attention to clean up doc builds21:11
clarkbis it intentional that we don't record the job name in the logs dir structure?21:13
pabelangerI guess we also don't have warnerrors=true for pbr21:13
pabelangerclarkb: we have a patch up to include it21:14
pabelangerhowever, we haven't merged because of lookup pluging21:14
pabelangerhttps://review.openstack.org/#/c/441617/21:14
pabelangerI could remove the lookup call, to at least land it21:15
clarkbpabelanger: they changed pbr and warnerrors is no longer a thing https://git.openstack.org/cgit/openstack-dev/pbr/commit/?id=72e8e42a34217e7f6847d221dc9751d0c350baa921:15
clarkbyou have to set it with sphinx's config now aiui21:15
pabelangerneat21:15
pabelangerclarkb: actually, we can move forward on 44161721:18
pabelangerlet me update it21:18
clarkbI'm fiddling with the doc builds to see if I can get this to fail21:18
clarkbthen will likely push up a mock up change with an attempt to make ti work21:18
clarkbbut someone like jeblair will likely need to edit datamodel.rst21:18
openstackgerritPaul Belanger proposed openstack-infra/zuul feature/zuulv3: Add net-info role  https://review.openstack.org/44161721:19
pabelangerwe might need to restart zuul to pick up zuul.executor.hostname21:20
pabelangerclarkb: mind a +3 https://review.openstack.org/#/c/450894/21:20
pabelangernodepool-launcher rename21:20
pabelangerfor puppet21:20
openstackgerritPaul Belanger proposed openstack-infra/zuul feature/zuulv3: Add net-info role  https://review.openstack.org/44161721:28
openstackgerritClark Boylan proposed openstack-infra/zuul feature/zuulv3: Cleanup docs builds and error on warnings  https://review.openstack.org/45296421:30
clarkbpabelanger: jesusaur ^ thats the fix for the docs. Jeblair you will likely want to make sure I didn't break anything on the docs side of the model21:30
openstackgerritPaul Belanger proposed openstack-infra/zuul feature/zuulv3: Add net-info role  https://review.openstack.org/44161721:38
openstackgerritMerged openstack-infra/zuul feature/zuulv3: Make tox-linters run the tox/linters play  https://review.openstack.org/45295321:40
*** hashar has quit IRC21:51
pabelangerclarkb: zuul information for jobs: http://zuulv3-dev.openstack.org/logs/44c6ac9aee174c8c8c8e8c190615a89f/console.log21:54
pabelangerfeedback wanted21:54
clarkbpabelanger: taht seems to match up with what we have in jjb21:55
clarkbpabelanger: maybe for verbosity include the commands run to collect the data?21:55
pabelangeruntil we restart zuul, executor will be unknow21:55
pabelangerclarkb: most are ansible variables at this point. hostname is uname -a, but ya21:56
pabelangerI can fix that21:56
clarkbpabelanger: specifically the network neighbors one could be a little ambiguous21:58
clarkbpabelanger: oh we should include the image uuid near the image build date too22:00
clarkbor did we lose that capability with newer nodepool, hrm22:00
pabelangerwill check22:01
clarkbya we don't appear to have it anymore because we stopped sshing to the nodes to write that in22:01
jeblairthere's some sort of zuul meeting now in #openstack-meeting-alt i think22:02
pabelangerclarkb: we likely need to append the info to our nodepool vars for zuul22:03
clarkbpabelanger: I also don't think its a blocker, just somethign to work towards while geting the current stuff in early22:04
pabelangerya22:04
jheskethMorning22:11
jeblairpabelanger: yeah, the node data structure in zk has a reference to the image, so we can look all that up within zuul and add it to ansible vars22:45
pabelangerjeblair: clarkb: we are just not collecting the subunit files from the worker, working on a patch22:59
pabelangerjeblair: agree22:59
openstackgerritPaul Belanger proposed openstack-infra/zuul feature/zuulv3: Collect test-results for tox jobs  https://review.openstack.org/45299123:07
SpamapSjeblair: apologies for missing zuul meeting. Did not sleep well last night and took a longer than expected power nap :-P23:17
jeblairSpamapS: np.  sounds like you're ready to hack now.  ;)23:19
SpamapScoffee in hand23:20
openstackgerritPaul Belanger proposed openstack-infra/zuul feature/zuulv3: Collect test-results for tox jobs  https://review.openstack.org/45299123:23
openstackgerritPaul Belanger proposed openstack-infra/zuul feature/zuulv3: Collect test-results for tox jobs  https://review.openstack.org/45299123:32
pabelangerokay, that gets the subunit files23:32
pabelangerbut, if it is the right place in the playbook23:32
pabelangerI'll figure that out tomorrow23:32

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