Thursday, 2019-08-08

corvusmnaser: https://review.opendev.org/621479 is the long-term plan for that.  i'm hoping we'll be able to start on that later this year00:08
mnaserNeat!00:09
corvusas Shrews points out, we're already starting on it really, with his change, and i think we're really close to being ready for the sql reporter change00:09
openstackgerritJames E. Blair proposed zuul/zuul master: Refactor build page tabs  https://review.opendev.org/67523500:28
openstackgerritJames E. Blair proposed zuul/zuul master: Add permalinks to task detail popup  https://review.opendev.org/67523600:28
corvusthat's clarkb's other request from yesterday; i think that's all known issues accounted for00:28
openstackgerritJames E. Blair proposed zuul/zuul master: Scroll log line anchor into view  https://review.opendev.org/67522000:29
*** threestrands has joined #zuul00:46
*** jamesmcarthur has joined #zuul01:05
*** jamesmcarthur has quit IRC01:11
*** jamesmcarthur has joined #zuul01:14
*** wxy-xiyuan has joined #zuul01:15
*** jamesmcarthur has quit IRC01:23
*** jamesmcarthur has joined #zuul01:26
*** tributarian has quit IRC01:37
openstackgerritJames E. Blair proposed zuul/zuul master: Refactor build page tabs  https://review.opendev.org/67523501:37
openstackgerritJames E. Blair proposed zuul/zuul master: Add permalinks to task detail popup  https://review.opendev.org/67523601:37
*** jamesmcarthur has quit IRC01:40
*** rlandy|rover|bbl is now known as rlandy|rover01:45
*** rlandy|rover has quit IRC01:50
*** jhesketh has quit IRC01:53
*** bhavikdbavishi has joined #zuul02:00
*** bhavikdbavishi1 has joined #zuul02:03
*** bhavikdbavishi has quit IRC02:04
*** bhavikdbavishi1 is now known as bhavikdbavishi02:04
*** jamesmcarthur has joined #zuul02:04
*** jamesmcarthur has quit IRC02:17
*** jhesketh has joined #zuul02:22
*** jamesmcarthur has joined #zuul02:28
*** bhavikdbavishi has quit IRC02:32
*** igordc has joined #zuul03:16
*** jhesketh has quit IRC03:29
*** bhavikdbavishi has joined #zuul03:33
*** jhesketh has joined #zuul03:36
*** raukadah is now known as chkumar|ruck03:49
*** jamesmcarthur has quit IRC04:01
*** jamesmcarthur has joined #zuul04:05
*** jamesmcarthur has quit IRC04:09
*** jamesmcarthur has joined #zuul04:10
*** jamesmcarthur has quit IRC04:19
*** jamesmcarthur has joined #zuul04:23
*** jamesmcarthur has quit IRC04:33
*** jamesmcarthur has joined #zuul04:34
*** jamesmcarthur has quit IRC04:42
*** jamesmcarthur has joined #zuul04:42
*** jamesmcarthur has quit IRC04:48
*** spsurya has joined #zuul05:02
*** lennyb has quit IRC05:26
*** bjackman has joined #zuul05:40
*** igordc has quit IRC05:59
*** lennyb has joined #zuul06:27
*** ianychoi has quit IRC07:01
*** ianychoi has joined #zuul07:01
*** themroc has joined #zuul07:16
*** tosky has joined #zuul07:17
*** themroc has quit IRC07:21
*** ianychoi has quit IRC07:24
*** ianychoi has joined #zuul07:25
*** themroc has joined #zuul07:28
*** panda has quit IRC07:35
*** panda has joined #zuul07:38
*** threestrands has quit IRC08:19
openstackgerritMark Meyer proposed zuul/zuul master: Rework a cache invalidation issue  https://review.opendev.org/67442508:26
openstackgerritSorin Sbarnea proposed zuul/zuul-jobs master: DNM: Test iptables_rules on Suse  https://review.opendev.org/67527008:28
openstackgerritMerged zuul/zuul-jobs master: Be consistent about spaces before and after vars  https://review.opendev.org/66769809:02
*** electrofelix has joined #zuul09:12
*** AshBullock has joined #zuul09:14
AshBullockHey all, I'm interested in passing the comment that triggers a job to the job itself as in zuul vars so that it could be used by our playbooks, does anyone know how feasible this would be?09:16
*** dmellado has quit IRC09:53
*** dmellado has joined #zuul09:55
*** AshBullock has quit IRC10:28
*** tobiash has quit IRC11:18
*** tobiash has joined #zuul11:20
*** tobiash has quit IRC11:24
*** tobiash has joined #zuul11:26
chkumar|ruckDoes required projects defined in parent job gets inherited in child job?11:43
*** jamesmcarthur has joined #zuul11:51
*** jamesmcarthur has joined #zuul11:51
*** jamesmcarthur has quit IRC12:02
*** jamesmcarthur has joined #zuul12:04
*** rfolco has joined #zuul12:12
*** jamesmcarthur has quit IRC12:21
AJaegerchkumar|ruck: yes - and you can check this in the log file as well12:26
*** rlandy has joined #zuul12:28
*** rlandy is now known as rlandy|rover12:28
*** bjackman has quit IRC12:34
tobiashShrews, corvus: any objections against adding cleanup of leaked volumes to nodepool? We have the problem that we leak a percentage of volumes that are created using boot-from-volume (they should get deleted automatically by openstack but that doesn't seem to work reliably).12:41
*** jamesmcarthur has joined #zuul12:54
Shrewstobiash: well, i've been trying to hunt down why that happens. I thought I found it, but apparently was incorrect. What I see in our logs is the first attempt fails because the volume is still in use (Conflict exception), but it never tries again because the znode for it disappears somewhere. I still don't know why that happens.13:07
tobiashShrews: so nodepool itself tries to delete it? I thought it marks them just as 'delete together with vm' and openstack automagically does that?13:08
Shrewstobiash: oh, you typed 'volume' but i read 'image'    *sigh*    lack of coffee13:09
tobiashShrews: well, we also leak images so we have that problem as well ;)13:09
tobiashbut the more pressing one for us is volumes atm13:09
Shrewstobiash: I'd be a bit nervous about volume cleanup. Accidentally deleting a volume could be very not good.13:11
tobiashShrews: the volumes have nodepool specific metadata13:11
ShrewsIf we can do it safely, I'm all for it13:11
tobiashso we could do it like ports, list them, filter by nodepool metadata and available and delete if we saw them a second time13:12
*** themroc has quit IRC13:15
*** themroc has joined #zuul13:16
*** jeliu_ has joined #zuul13:19
*** Diabelko has quit IRC13:39
openstackgerritJeff Liu proposed zuul/zuul-operator master: WIP: Add zuul-operator-functional-openshift job  https://review.opendev.org/67435513:44
*** electrofelix has quit IRC13:57
*** tributarian has joined #zuul13:58
corvusclarkb, mordred, tristanC: would you please review any changes in "topic:console" and go ahead and approve them when they have 2x+2 ?14:01
tobiashcorvus: awesome work :)14:02
openstackgerritJeff Liu proposed zuul/zuul-operator master: WIP: Add zuul-operator-functional-openshift job  https://review.opendev.org/67435514:05
mordredcorvus: stack looks great!14:11
corvusmordred: don't forget https://review.opendev.org/67522014:12
corvusit's independent14:12
mordredcorvus: ++14:21
openstackgerritTristan Cacqueray proposed zuul/zuul master: web: refactor the errorsIds into the build action  https://review.opendev.org/67535014:28
corvustristanC: thanks!14:29
*** rlandy|rover is now known as rlandy|rover|mtg14:31
openstackgerritJeff Liu proposed zuul/zuul-operator master: WIP: Add zuul-operator-functional-openshift job  https://review.opendev.org/67435514:41
corvustristanC: i went to dig up a zuul-preview url for you, and i think there's a bug that allows it to be an open proxy, so i've shut it down for now, sorry15:02
tristanCcorvus: that's ok, i'll use my local yarn run then15:04
*** themroc has quit IRC15:08
*** rlandy|rover|mtg is now known as rlandy|rover15:20
openstackgerritMerged zuul/zuul master: Scroll log line anchor into view  https://review.opendev.org/67522015:20
corvushaha, there's a comment in zuul: https://bugs.executepad.net/zuul/+bug/107894615:29
corvuslooks like one of the s/launch/execute/ seds got away from someone :)15:30
fungii can't reach bugs.executepad.net15:33
*** spsurya has quit IRC15:34
AJaegerfungi: s/launch/execute/ - I felt in the same trap, so use bugs.launchpad.net/zuul/+bug/107894615:34
fungid'oh!15:34
fungiso *that's* what corvus meant15:34
AJaegerfungi: the problem is that the comment is wrong15:34
AJaegerZuul has that broken URL as comment15:35
fungii thought that looked remarkably like a launchpad url, and wondered if someone was running a private lp instance at that domain at first15:35
AJaegerfungi: for both of us, this URL would have been better: https://opendev.org/zuul/zuul/src/branch/master/tests/unit/test_scheduler.py#L207015:36
fungiahh15:36
funginow it's making sense15:36
corvusthis way you got to have the same experience i did :)15:37
corvusgroup bonding activity15:37
AJaegerhttps://review.opendev.org/#/c/445594/ - by pabelanger ;)15:37
AJaeger"Rename zuul-launcher to zuul-executor"15:37
fungiyes, this was a fun trip through zuul history15:38
AJaeger;)15:39
mordredhahaha15:39
clarkbtobiash: the other day I noticed something weird with zuul's ansible installation management. Let me get a few links together but I was hoping to talk to you about that today to see if I am missing anything15:50
tobiashclarkb: was it failing? I think I also saw some unzip related errors (which are probably due to parallel installation of all envs)15:51
tobiashwe should think about serializing those15:51
clarkbtobiash: no I think we use inconsistent installation targets depending on whether or not zuul automanages the venvs or if zuul's venv installer command is used15:52
clarkbtobiash: at https://opendev.org/zuul/zuul/src/branch/master/zuul/lib/ansible.py#L44-L45 we default to /usr/lib/zuul/ansible as the installation target when no other directory is provided. This is the case with the zuul manage_ansible.py tooling15:52
tobiashclarkb: I have to run now, I'll look later at home15:53
clarkbtobiash: but at https://opendev.org/zuul/zuul/src/branch/master/zuul/executor/server.py#L2400-L2408 if the executor config is set to manage_ansible automatically it defaults to os.path.join(state_dir, 'ansible-bin') and the state_dir is /var/lib/zuul by default15:54
clarkbI think this means that if you use the manage_ansible command things get instlaled to /usr/lib/zuul/ansible and if you use [executor] manage_ansible = True things intsall to /var/lib/zuul/ansible-bin15:55
clarkbIf this is indeed the case I think it would be safe to update the [executor] manage_ansible case to simply intsall things to /usr/lib/zuul/ansible instead and have a release note that people can clean up /var/lib/zuul/ansible-bin ?15:56
clarkbtobiash: ok, I'm going to push up the change to do ^ and that can collect the discussion15:57
openstackgerritClark Boylan proposed zuul/zuul master: Consistent handling of ansible venv install dirs  https://review.opendev.org/67540316:26
clarkbtobiash: ^ I think that explains what I found and cleans it up. And that cleanup should be backward compatible as any override paths are still searched if provided.16:27
clarkbcorvus: ^ that is related to my confusion finding the ansible venvs on tuesday16:27
clarkbcorvus: did the ara version specifier fix solve the ara on zuul jobs with swift problem?16:27
openstackgerritMerged zuul/zuul master: Render console in js  https://review.opendev.org/67436816:28
*** mattw4 has joined #zuul16:29
openstackgerritMerged zuul/zuul master: Usability tweaks for the build page console  https://review.opendev.org/67514716:34
*** armstrongs has joined #zuul16:35
*** AshBullock has joined #zuul16:37
*** mattw4 has quit IRC16:39
*** mattw4 has joined #zuul16:39
*** chkumar|ruck is now known as raukadah16:42
openstackgerritJeff Liu proposed zuul/zuul-operator master: WIP: Add zuul-operator-functional-openshift job  https://review.opendev.org/67435516:42
AshBullockHey all, I'm interested in passing the comment that triggers a job to the job itself as in zuul vars so that it could be used by our playbooks, does anyone know how feasible this would be?16:44
*** jangutter has quit IRC16:44
AshBullockfor a gitub pr comment being used as a trigger16:45
fungii thought someone said that was already provided as a zuul var16:47
clarkbAshBullock: off the top of my head I think you would have to plumb that comment data through zuul from the trigger driver all the way through the scheduler and down into the jobs16:47
clarkboh /me checks if that is already done16:47
fungii'll see if i can find documenation16:47
fungidocumentation too ;)16:47
corvusi don't think the review comment is, i think just the commit message is16:48
corvusthat's a tricky one, because jobs are meant to be independent of their triggers16:48
*** tosky has quit IRC16:49
fungiahh, okay, so commit message (or pr description presumably?)16:49
corvusso you should get the same result from a job triggered by a patch upload, a 'recheck' comment, a web trigger, an email trigger, etc...16:49
corvusa timer trigger, a zuul trigger....16:49
corvusyou get the idea16:49
corvusAshBullock: can you describe the use case a bit more?16:49
clarkbcorvus: ya confirmed the commit message is base64 encoded but I don't see the review comment16:51
clarkbis it known that zuul's zuul status page links to job logs don't work?16:56
fungiclarkb: yes, if you mean ones for builds in sets which have yet to report16:56
clarkboh ya that explains it16:56
clarkbthe sql reporter doesn't report until jobs complete16:56
clarkb*all jobs in buildset16:56
fungiright now it's linking to the result page which won't exist until sql is reported into16:56
openstackgerritJames E. Blair proposed zuul/zuul master: Add option to report build page  https://review.opendev.org/67540916:57
openstackgerritJames E. Blair proposed zuul/zuul master: Add release note for Pagure driver  https://review.opendev.org/67541016:57
openstackgerritJames E. Blair proposed zuul/zuul master: Move admin-rules setting in tenants doc  https://review.opendev.org/67541116:57
openstackgerritJames E. Blair proposed zuul/zuul master: Make auth docs more boring  https://review.opendev.org/67541216:57
openstackgerritJames E. Blair proposed zuul/zuul master: Don't capitalize Token in docs  https://review.opendev.org/67541316:57
fungiclarkb: i believe the idea was that we would for now switch those to direct log links and later make sql reporting mandatory and shift it to happen as each build completes16:57
corvusand there's the change to do it :)16:57
corvusalso, docs changes since i was in the neighborhood16:58
fungirighteous!16:58
AshBullockYea, after some digging and checking the zuul vars I saw it is only the commit message that gets passed through.16:58
corvusclarkb, fungi, mordred, tobiash: can you put https://review.opendev.org/675409 at the top of your list?  we'll need that merged by monday if we're going to meet my self-imposed deadline to make that switch :)16:59
*** hwangbo has joined #zuul16:59
AshBullockclarkb yea I had looked at the connector for git and it does look non trivial to pass this all the way through the chain16:59
clarkbcorvus: yup16:59
AshBullockcorvus Essentially we had an idea of controlling the flow of our playbooks based on the contents of the message, so placing a variable into the comment17:00
tobiashcorvus: I'll look in a bit17:01
corvusAshBullock: the problem that brings up is that it doesn't match the gating paradigm; if the behavior of the job changes because of manual intervention (ie, text in a comment), then it's not automatically reproducible.  whatever you did to make the job run that way when checking it, you would also have to do for gating, and it may not match the way the job runs on the next change through the gate.17:04
corvusAshBullock: so first, i'd suggest being very careful of going down that path -- the more jobs behave deterministically, the more you can automate and gate things.17:05
corvusAshBullock: however, there are use cases where folks may want to run more experimental variants of jobs, with the understanding they could not be used for gating, or deployment, etc..17:06
corvusAshBullock: we had a long design discussion with tristanC about that, and came up with a solution in https://review.opendev.org/555153 (see the review comments there, but also especially the links to irc discussions).  the outcome of that is the system in https://review.opendev.org/63990517:07
*** sshnaidm is now known as sshnaidm|off17:10
*** igordc has joined #zuul17:13
AshBullockyea completely agree with the fact that jobs should be reproducible tracing back to version control, the use case specifically was to run a development deployment job and to override the target environment without having to update the zuul config. It was an idea to speed up our development workflow17:15
fungiclarkb: regarding your comment on 675409 there's a good reason for the conditional, see reply17:17
clarkbfungi: good point and ya your fix handles that17:18
fungito be clear, i think it's fine as-is, this is not a performance-critical code path and the conditional is more explicit17:18
corvusAshBullock: gotcha, that matches the use case tristanC was working on pretty closely, so i think once we get that in, you should be able to accomodate it17:20
AshBullockcorvus  thanks for all the information, I'll keep an eye on this change :)17:21
*** jamesmcarthur has quit IRC17:22
*** armstrongs has quit IRC17:22
openstackgerritClark Boylan proposed zuul/zuul master: Consistent handling of ansible venv install dirs  https://review.opendev.org/67540317:25
*** AshBullock has quit IRC17:27
tristanCcorvus: AshBullock: actually, we kind of stepped down from that webtrigger proposal and took this git gateway system path: https://pagure.io/software-factory/zuul-gateway17:30
tristanCcorvus: AshBullock: it would be nice if this was supported natively in Zuul (parameterized build), but until then, this trick works quite well for our needs17:31
corvustristanC: yeah, i think we should still work on merging the patches you have up17:32
corvusi think it's a good feature17:32
*** jamesmcarthur has joined #zuul17:33
tristanCcorvus: one use-case missing from the current patches is being able to override nodeset too17:33
tristanCiirc, that was the motivation of writting that zuul-gateway17:35
corvusack; sounds like a good thing to add; i'd have to refresh my memory a bit to know how hard it would be17:38
tristanCcorvus: for the web interface, we would need that to display a drop-down: https://review.opendev.org/#/c/605877/17:43
*** ianychoi has quit IRC17:43
*** ianychoi has joined #zuul17:47
*** panda has quit IRC17:53
*** ianychoi_ has joined #zuul17:54
*** panda has joined #zuul17:54
*** ianychoi_ has quit IRC17:55
*** ianychoi_ has joined #zuul17:55
*** ianychoi has quit IRC17:58
corvusclarkb: can you review topic:console when you have a few mins?17:58
clarkbcorvus: ya17:58
mordredcorvus: https://review.opendev.org/#/c/675409 ... looking at https://review.opendev.org/#/c/675409/1/zuul/scheduler.py - it looks like it always adds t/{tenant.name} to the webroot ... what about white label?18:00
corvusmordred: see tenant.web-root18:00
*** jeliu_ has quit IRC18:01
mordredcorvus: thank you. I was conflating two things in my brainhole :)18:01
*** jeliu_ has joined #zuul18:02
mordredcorvus: that has 3x+2 now - any reason to not +A it?18:04
fungiluckily gertty showed me the documentation changes and release notes and tests/fixtures before the implementation18:04
fungiwhich was probably serendipitous but made it an easy review as a result18:04
mordredfungi: I have this habit of reading zuul changes upside down - it usually helps me but today it did not18:04
fungiyou have to wait longer for all the blood to rush to your head18:05
mordredyeah- but once it does boy howdy18:06
*** igordc has quit IRC18:28
*** jamesmcarthur has quit IRC18:30
pabelangertobiash: have you been running from master for zuul? Curious how you are making how with recent github improvements around github events18:37
*** jamesmcarthur has joined #zuul18:42
tobiashpabelanger: we're running currently from e858b8df (8 days ago)18:44
pabelangerkk, thanks!18:45
tobiashpabelanger: and I didn't notice anything special with github events anymore18:45
tobiashruns smoothly with that regard18:45
pabelangerokay cool, I think we are starting to slow down a little with all the events from ansible/ansible. So looking forward to testing out for next released18:45
*** rfolco has quit IRC18:51
tobiashclarkb: I'm wondering, what the problem with the ansible installation dirs is? The system is meant to either use pre-installed ansible (where the lib dir is correct) or the dynamic variant (where we need to use the state dir because of guaranteed write access).18:52
tobiashit's not supposed to be mixed18:52
clarkbtobiash: the issue for me is lack of consistency and confusion18:57
clarkbwhy cant the manage ansible command install to the same location and then when you want to find the venvs you arent looking in multiple locations?18:58
clarkbwe needed to debug venv contents a couple days ago and I could not find them because code says one thing but really uses another18:58
tobiashclarkb: using the state dir requires a proper zuul configuration and inhibits the possibility to install ansible already into the container image (because you normally need to bind mount a volume there). While installing into the lib dir is only dependent on the install location.19:00
*** rfolco has joined #zuul19:00
tobiashso if we want to make this consistent I'd rather suggest to drop the dynamic installation completely as this is only intended to ease quick start of zuul19:01
clarkbfor some reason I thought docker copied over the contents from image to mount but maybe that was an init process?19:02
clarkbor maybe that is volumes vs bind mounts19:02
tobiashno, it doesn't, any existing directory is completely shadowed and unaccessible when bind mounting a volume there19:02
tobiashso there are real technical reasons that those are different directories19:03
clarkbya its a bind vs volume behavior19:03
clarkbdocker volumes do what I describe19:03
tobiashif we want only one directory the only way I see (maybe I'm wrong) is to drop one possiblility of installing ansible (and that would be the dynamic one)19:04
clarkbas an alternative maybe we can pull that logic into the ansible management classes rather than having executor do something different than manage_ansible?19:07
clarkband add docs (I couldnt find any at least) on where to find the venvs and why the behavior doffered19:07
corvusclarkb: mind if i wip your change for now?19:08
tobiashclarkb: yes, I think that would make sense19:08
openstackgerritMerged zuul/zuul master: Don't always show expansion option on build console  https://review.opendev.org/67516319:08
openstackgerritMerged zuul/zuul master: Adjust results headings in build console page  https://review.opendev.org/67520319:09
tobiashcorvus: 675409 has 4 time +2, shall we merge it now?19:09
clarkbcorvus: sure19:09
corvustobiash: ++19:10
corvusthere's one more js console change that needs a +3 https://review.opendev.org/67523619:11
clarkbcorvus: ya that one was next on my list but had to step out for a few after reviewing the first 319:11
tobiashcorvus: do you have an idea why 675039 didn't enter the gate after successful check?19:12
clarkbtobiash: the other thing that came to mind looking at the venv installations was being able to tell manage_ansible.py what path to install to19:13
corvustobiash: oh i think it's because of the removal of clean check; i think we need to either add something back or add reverify19:13
clarkbI'll take a look at the code again with some of the original intent in mind and see if changes are appropriate19:13
tobiashclarkb: thanks (I thought the installation destination is already overridable but maybe I don't remember correctly)19:15
clarkbtobiash: I think we only load in that path override if doing the runtime install not the manage_ansible.py install19:15
tobiashah ok19:15
clarkbcorvus: left a comment on https://review.opendev.org/#/c/675236/219:21
corvusclarkb: good catch19:36
clarkbcorvus: fwiw I htink that happens in other makeTaskPath usages too19:39
clarkboh ya I think you mention that in your esponse on the change19:39
corvusyup19:39
*** panda has quit IRC19:57
*** panda has joined #zuul19:59
openstackgerritJames E. Blair proposed zuul/zuul master: Add permalinks to task detail popup  https://review.opendev.org/67523620:01
corvusmordred, clarkb: ^20:02
clarkbcorvus: is that doing character by character comparison or path entry by path entry comparison?20:06
corvusclarkb: path entry (they are arrays)20:07
corvusclarkb: javascript is not so good at determining array equality :(20:08
openstackgerritTristan Cacqueray proposed zuul/zuul master: web: extract pure functions from the TaskOutput component  https://review.opendev.org/67546020:08
clarkbcorvus: on line 224 is js like C where the condition applies to the next line only if no {}s are used?20:11
openstackgerritJames E. Blair proposed zuul/zuul master: Hide "root" variable in job web page  https://review.opendev.org/67546120:11
corvustristanC: ^ i learned that working on the console stuff20:12
corvusclarkb: yeah.  if folks want to adopt the always-use-braces style, i don't object20:13
corvus(that's a rare stylistic choice with real consequences so i'm not going to walk out of the room if we start talking about it :)20:13
openstackgerritMerged zuul/zuul master: Add option to report build page  https://review.opendev.org/67540920:13
clarkbcorvus: I'm fine with it as is. I just wanted ot make sure the behavior was what I expected20:14
corvus(i think, really, the behavior is always that the conditional applies to the next statement, but {} makes a compound statement)  (statement is probably not the right word, but i have not paged in all of my compiler theory.)20:15
corvustristanC: i'd like to merge https://review.opendev.org/630079 soon.  do you agree with my proposed change?  if so, do you want to implement it or should i?20:27
corvuspabelanger: have you had a chance to test base-minimal-test since https://github.com/ansible/project-config/pull/171 merged?20:30
tristanCcorvus: i can look into reviving 630079 in a few hours20:31
corvustristanC: thanks!20:31
openstackgerritMerged zuul/zuul master: Use wait for empty update queue before accepting merges  https://review.opendev.org/67503920:33
*** jeliu_ has quit IRC20:46
*** bhavikdbavishi has quit IRC20:47
*** jeliu_ has joined #zuul20:49
openstackgerritMerged zuul/zuul master: Refactor build page tabs  https://review.opendev.org/67523520:54
clarkbtobiash: looking at the need to configure the path for manage_ansible.py one option (though maybe not a great one) would be to add that then if you want to install to say /usr/lib pass that path to manage_ansible.py and set the config for it20:55
clarkbthat does increase users' need to configure things though20:55
*** tjgresha has joined #zuul20:58
openstackgerritJeff Liu proposed zuul/zuul-operator master: WIP: Add zuul-operator-functional-openshift job  https://review.opendev.org/67435521:07
*** jeliu_ has quit IRC21:12
*** igordc has joined #zuul21:13
*** rfolco has quit IRC21:18
*** jamesmcarthur has quit IRC21:19
corvustristanC: can you review https://review.opendev.org/673841 ?21:21
openstackgerritMerged zuul/zuul master: Add permalinks to task detail popup  https://review.opendev.org/67523621:23
mordredcorvus, clarkb: from scrollback - I wouldn't mind adopting always-braces for ifs - largely because it _does_ have impacts, and coming from python if I saw two lines indented but no braces around them I'm pretty sure my brain would take AGES to figure out the logic error21:25
mordredI don't feel absurdly strongly either way - but it's one of those style things that really can help with logic accidents in brace languages21:26
corvusok.  i had been doing always-braces, and only put in a few lines of no-brances; i'll undo those as i see them and stick with always in the future.21:27
*** armstrongs has joined #zuul21:28
fungisteeped in c long enough i'm pretty sure i mostly ignore indentation, but still, can't hurt21:31
corvusooh, i wonder if we can syntax highlight yaml/json files like http://zuul.opendev.org/t/zuul/build/1bf501bb821f41bba727aa00b09eaa39/log/zuul-info/inventory.yaml21:31
fungis/ignore/distrust.21:32
corvusalso, now that i'm starting to use the logs tab more, i kinda want the log viewer to be in the logs tab, so i can switch to a different logfile without hitting back21:32
corvus(the first few weeks of using this stuff is going to be really fun :)21:33
fungithat seems like a worthwhile optimization21:33
*** armstrongs has quit IRC21:38
openstackgerritJames E. Blair proposed zuul/zuul master: web: refactor the errorsIds into the build action  https://review.opendev.org/67535021:40
corvustristanC: rebased ^21:40
mordredfungi: I have enough perl in my background that I've learned to distrust almost any syntactic sugar that lets me express more in fewer characters ...21:42
mordredalthough I do miss the obfuscated perl contests ...21:43
fungifair21:44
mordredhttps://www.foo.be/docs/tpj/issues/vol4_3/tpj0403-0017.html <-- the wc script that compiles in both c and perl continues to be fun21:46
openstackgerritClark Boylan proposed zuul/zuul master: Improve functionality and docs around ansible installation  https://review.opendev.org/67540321:49
Shrewsmordred: i wasn't aware there was a Perl Journal, even within a contest. On a related note, did you see Llinux Journal is closing its doors?21:49
clarkbcorvus: tobiash ^ maybe something like that is what we want in the end? I think the biggest thing was all the docs ignored the automagic state dir install so I wans't aware that there were possibly two things happening21:50
fungiShrews: end of an era21:52
mordredShrews: I did not see that ... but yeah, end of an era22:01
*** panda has quit IRC22:03
*** panda has joined #zuul22:03
*** mattw4 has quit IRC22:04
*** mattw4 has joined #zuul22:04
openstackgerritJames E. Blair proposed zuul/zuul master: web: refactor the errorsIds into the build action  https://review.opendev.org/67535022:05
*** mattw4 has quit IRC22:14
*** mattw4 has joined #zuul22:14
openstackgerritJames E. Blair proposed zuul/zuul master: Correctly identify failed tasks  https://review.opendev.org/67548822:16
openstackgerritJames E. Blair proposed zuul/zuul master: Refactor task result detection  https://review.opendev.org/67548922:16
*** panda has quit IRC22:16
corvusclarkb, tristanC, mordred, tobiash: i thought we were done but we need at least up to 675488 or we'll miss some failed tasks.  489 after it is a simple cleanup.22:17
*** panda has joined #zuul22:20
openstackgerritTristan Cacqueray proposed zuul/zuul master: web: add buildset page  https://review.opendev.org/63007922:20
tristanCcorvus: 675488 sounds correct to me, but without test case it's hard to review...22:22
tristanCcorvus: the last PS for the buildset page should look like what you described22:23
corvustristanC: yeah, that's a good candidate for a test22:23
corvuswe can copy in a whole bunch of different ansible json output test cases22:24
tristanCcorvus: we could also test the whole console component, but the reactdom stuff is not very easy to work with. If we do that, we should look into enzyme to assert rendering22:25
tristanCand then, not worry with the internal procedure22:25
corvusthat sounds like it might be worth a look.. maybe a poc patch?22:26
corvus(i like "assert rendering" but i'm worried about "not very easy to work with"  :)22:26
tristanCcreate-react-app only setup ReactTestUtils and ReactDOM, which is limited to look for dom content, see the App.test.jsx22:28
openstackgerritMerged zuul/zuul master: Provide buildset.uuid in /builds API result  https://review.opendev.org/67475922:30
corvustristanC: buildset page looks great, with that and the change that just merged ^ we should be able to link back to the buildset page from the build page22:32
tristanCwell i'd rather stay as far as possible from the dom, thus unit testing the pure js function sounds like a good first step too22:33
openstackgerritTristan Cacqueray proposed zuul/zuul master: web: link the buildset page from the build  https://review.opendev.org/67549322:38
*** mattw4 has quit IRC22:44
*** mattw4 has joined #zuul22:54
openstackgerritTristan Cacqueray proposed zuul/zuul master: web: extract pure functions from the TaskOutput component  https://review.opendev.org/67546022:55
*** mattw4 has quit IRC23:03
*** mattw4 has joined #zuul23:04
*** mattw4 has quit IRC23:52

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