Monday, 2019-05-20

openstackgerritTristan Cacqueray proposed zuul/zuul master: Revert "Revert "web: upgrade react and react-scripts to ^2.0.0""  https://review.opendev.org/65999100:59
tristanCmordred: i couldn't find the issue with the react bump, here is a vanilla revert of the revert ^00:59
mordredtristanC: cool. hopefully it will show up in the build output00:59
mordredtristanC: I think it might have something to do with the data coming from the openstack status endpoint - when it was failing, it was only failing on openstack, not on opendev01:00
tristanCmordred: let's see, running it locally with start:openstack doesn't show issue atm01:03
*** threestrands has joined #zuul02:34
*** bhavikdbavishi has joined #zuul03:35
*** swest has joined #zuul05:22
*** chkumar|pto is now known as chandankumar05:58
openstackgerritMerged zuul/zuul master: Get playbook data from extra_vars  https://review.opendev.org/65980206:20
*** zxiiro has quit IRC06:47
*** jbryce has quit IRC06:47
*** tima has quit IRC06:47
*** Shrews has quit IRC06:47
*** tima has joined #zuul06:47
*** Shrews has joined #zuul06:47
*** jbryce has joined #zuul06:47
*** clayg has quit IRC06:47
*** clayg has joined #zuul06:47
*** jtanner has quit IRC06:48
*** johnsom has quit IRC06:48
*** mnasiadka has quit IRC06:48
*** jtanner has joined #zuul06:48
*** mnasiadka has joined #zuul06:48
*** johnsom has joined #zuul06:48
*** zxiiro has joined #zuul06:48
*** saneax has joined #zuul07:08
*** themroc has joined #zuul07:11
*** yolanda_ has quit IRC07:13
*** yolanda_ has joined #zuul07:20
*** threestrands has quit IRC07:23
*** pcaruana has joined #zuul07:23
*** bhavikdbavishi has quit IRC07:30
*** hashar has joined #zuul07:42
*** jpena|off is now known as jpena07:52
*** gtema has joined #zuul08:04
*** jangutter has joined #zuul08:18
*** bhavikdbavishi has joined #zuul08:21
*** gtema has quit IRC08:24
*** markwork has joined #zuul08:27
*** gtema has joined #zuul08:27
*** panda|rover|off is now known as panda|rover08:41
openstackgerritFabien Boucher proposed zuul/zuul master: A reporter for Elasticsearch with the capability to index build and buildset results in an index.  https://review.opendev.org/64492709:32
openstackgerritFabien Boucher proposed zuul/zuul master: A reporter for Elasticsearch  https://review.opendev.org/64492709:38
openstackgerritMerged zuul/zuul-website master: Add slides for Spring 2019 Board Update  https://review.opendev.org/65618209:42
*** gtema has quit IRC10:38
*** flaper87 has quit IRC10:42
*** panda|rover is now known as panda|lunch10:52
*** panda|lunch is now known as panda|rover|eat10:53
*** flaper87 has joined #zuul11:01
*** hashar has quit IRC11:03
*** yolanda_ has quit IRC11:04
*** hashar has joined #zuul11:07
*** yolanda_ has joined #zuul11:08
*** jpena is now known as jpena|lunch11:25
corvusit looks like the image build jobs are broken again?11:44
corvus[0m[91mCould not open requirements file: [Errno 2] No such file or directory: '/output/zuul_base/requirements.txt'11:45
*** gtema has joined #zuul11:49
openstackgerritMarkus Hosch proposed zuul/zuul master: Evaluate CODEOWNERS settings during canMerge check  https://review.opendev.org/64455711:51
AJaegerzuul-jobs maintainer, what do you think about https://review.opendev.org/648658 ?11:56
openstackgerritSimon Westphahl proposed zuul/zuul master: Keep task stdout/stderr separate in result object  https://review.opendev.org/65027611:57
*** panda|rover|eat is now known as panda|rover11:57
openstackgerritSimon Westphahl proposed zuul/zuul master: Keep task stdout/stderr separate in result object  https://review.opendev.org/65027611:59
corvusoh, that's not a problem with the build job -- that's actually an error in that change: //review.opendev.org/65925512:02
corvuser... sorry about the copy/paste but you get the idea12:02
corvusmordred: ^ i left a -1 comment on that12:06
openstackgerritChristian Fetzer proposed zuul/zuul master: pass-to-parent: Fix passing multiple secrets to parent  https://review.opendev.org/66010512:16
*** bhavikdbavishi has quit IRC12:20
*** jpena|lunch is now known as jpena12:22
*** bhavikdbavishi has joined #zuul12:23
*** rlandy has joined #zuul12:27
*** ianychoi has quit IRC12:28
*** ianychoi has joined #zuul12:29
*** markwork has quit IRC12:34
Shrewsso odd to see corvus active before, well, anyone12:35
corvusthanks for not "accidentally" hitting [enter] after the word 'active' :)12:42
AJaegertristanC: did you see my comment on https://review.opendev.org/532083 ? Shouldn't we cap ansible-lint version like we do in requirements today?12:48
AJaegercorvus: did you see my question on the zuul list regarding version for ansible to run in linters? Right now we use 2.5 - should we update to 2.7? Do we have a policy for this already?12:49
AJaegertristanC: could you look at https://review.opendev.org/#/c/632620/ ? There's an open comment waiting for your followup...12:51
corvusAJaeger: no, i'm not caught up on email; however, i'm concerned that ansible-lint is getting far too opinionated -- we discussed maybe we need to rethink that.  (cc pabelanger)12:54
AJaegercorvus: ok, keep my WIP on the changes a bit longer until I hear feedback.12:55
AJaegerregarding ansnible-lint: yes, the recent changes make me wonder whether an uncapped version is the right thing...12:56
fungiwell, if an uncapped version is not the right thing, then we should probably also reconsider our use of it overall12:56
fungibecause we won't want to leave it on last week's version forever12:57
fungicapping and raising the cap are fine if we expect to want to follow the new rules they're adding and just need time to nondisruptively adjust all the code to conform to them12:57
fungiif we think they're going in a different (more opinionated) direction than is compatible with our projects, we should probably just replace those jobs with something like yamllint or even just a parser12:59
AJaegergood point12:59
fungii wish more linters would follow the same model as lintian does, where rules are ranked by importance and you don't get the really opinionated stuff without passing --pedantic13:01
fungii think bandit's going in the right direction, allowing you to configure it to only warn about violations of rules at or above a certain severity13:02
*** bhavikdbavishi has quit IRC13:13
*** bhavikdbavishi has joined #zuul13:14
tristanCAJaeger: thank you for the feedback, i'll update/comment the review13:19
openstackgerritTristan Cacqueray proposed zuul/zuul-jobs master: add-build-sshkey: remove previously authorized build-sshkey  https://review.opendev.org/63262013:22
*** bhavikdbavishi has quit IRC13:32
*** pcaruana has quit IRC13:33
*** gtema has quit IRC13:34
openstackgerritChristian Fetzer proposed zuul/zuul master: pass-to-parent: Fix passing multiple secrets to parent  https://review.opendev.org/66010513:34
pabelangerq: does zuul dashboard support regex for builds tab?13:37
corvuspabelanger: i don't think so, though i believe it shuold support multiple values13:41
pabelangercorvus: ack, thanks13:42
corvus(so you should be able to add two projects and see all the builds for both)13:43
openstackgerritFlavio Percoco proposed zuul/zuul master: Fix typo in log message  https://review.opendev.org/66011813:43
openstackgerritSimon Westphahl proposed zuul/zuul master: Keep task stdout/stderr separate in result object  https://review.opendev.org/65027613:46
corvusShrews: when you have a sec, can you look at https://review.opendev.org/658889 wrt the implications for nodepool handling that info?13:54
Shrewscorvus: sure13:58
corvusShrews, tobiash: i like that feature, but maybe we should think about the best way to pass that info to nodepool so it's not too zuul-specific (since i don't think it needs to be -- an external identifier for a request makes sense generically)14:00
tobiashcorvus: you mean something more like meta.event_id? instead of meta.zuul_event_id?14:02
tobiashor something completely different?14:02
Shrewsnon-zuul specific name is a good idea. any reason the event ID is within a 'meta' dict and not a direct attribute?14:04
Shrewsare you expecting more metadata?14:05
tobiashI was thinking that we might want to add more in the future14:05
tobiashbut I also can easily remove the meta if you like14:06
tobiashmeta just sounded good for stuff that's not needed for request processing and nodepool might or might not care about14:07
Shrewsi mean, it's either relevant for the request or isn't. we have metadata on node objects b/c of the various drivers and whatnot, so it makes sense there. it seems like a level of abstraction not needed for a request.14:08
Shrewsif nodepool doesn't care about it, why send it?14:08
Shrewsnothing else is going to process it14:09
Shrewsmaybe i'm alone in that line of thinking though14:09
tobiashShrews: the idea is to send it and if it exists nodepool can annotate the logs with it14:11
tobiashbut the idea is to keep that optional14:11
Shrewsright. that doesn't explain why it can't be its own attribute14:11
tobiashsure it can, I'm completely fine with both options14:12
Shrewsnodepool can just as easily say request.get('event_id') or request.meta.get('event_id), so i don't follow the reasoning14:12
*** hashar has quit IRC14:13
tobiashI just looked at it as some kind of metadata14:13
tobiashbut I'm not opinionated on this point14:13
tobiashso I'm completely fine making it its own attribute14:14
Shrewswell, i'm the only dissenting voice, so go with what the majority likes   :)14:16
Shrewsi'll leave my comment on the review and let someone else make the final call14:17
tobiashShrews: right now, you're the majority as I'm split on that topic ;)14:17
tobiashlet's hear how corvus thinks about it14:17
Shrewscommented14:21
tobiashShrews: thanks, will update14:22
*** jamesmcarthur has joined #zuul14:22
Shrewstobiash: i do like that we will have that for problem tracing... finally!14:22
tobiashyes :)14:22
corvustobiash, Shrews: i think Shrews proposal makes sense, so if there's no technical reason to avoid it, dropping "meta.zuul" makes sense14:23
*** armstrongs has joined #zuul14:24
openstackgerritTobias Henkel proposed zuul/zuul master: Annotate node request processing with event id  https://review.opendev.org/65888914:25
armstrongshey guys why you start the zuul-executor using systemd then when its running execute zuul-executor verbose is it expected that the live streamed logs when a job is in progress are run with ansible verbosity -vvv? It doesn't seem to be having any impact ...14:25
armstrongswhen*14:25
armstrongsor is the verbosity only applied to the final saved log?14:26
corvusarmstrongs: it should apply to the ansible output saved in the executor's own logs -- i don't think it should affect the log output saved by the job14:27
armstrongsso the web uis streamed ansible logs won't be -vvv?14:28
fungie.g. /var/log/zuul/executor-debug.log14:29
armstrongsis there any way to make them more verbose?14:29
Shrewstobiash: you need to replace all the request.meta.get('zuul_event_id') portions14:29
armstrongsat job level or project level14:29
*** jamesmcarthur has quit IRC14:29
tobiashShrews: oops, fixing14:30
tobiashthanks14:30
openstackgerritTobias Henkel proposed zuul/zuul master: Annotate node request processing with event id  https://review.opendev.org/65888914:32
tobiasharmstrongs: no, buildlog.txt stays as is, but you can look into buildlog.json which has much more information14:32
armstrongsok so just clarify you currently can't up the verbosity on the streamed logs to the zuul interface. buildlog.txt is the completed version of that, for more verbose ansible information i should look in buildlog.json14:35
armstrongscorrect?14:35
fungithat's correct as far as i know14:36
armstrongsthanks guys14:36
fungiif we did add something to make it configurable, i'd expect that would be exposed as a settable attribute along the lines of job.ansible-verbosity (but with the detailed json output i'm not sure it's warranted)14:37
*** jamesmcarthur has joined #zuul14:37
armstrongsthat would be great14:38
armstrongsas our users are asking for more verbosity14:39
armstrongsas for long running tests they are used to watching it in some instances14:39
clarkbI think our users rely on ara for that extra ansible insight14:40
armstrongsany pointers on setting it up alongside zuul?14:40
armstrongswe are doing a poc so may be worth a look14:41
fungiwell, ara's postprocessed so doesn't help the users who like to spend their time sitting and staring at the screen while the job runs14:41
* fungi feels like that's akin to watching paint dry, but each to their own14:42
armstrongswe have test qa engineers14:42
armstrongsso no comment14:42
armstrongs:)14:42
fungiheh14:42
armstrongsthey are used to jenkins output14:42
armstrongsand looked different14:42
armstrongssigh14:43
*** jamesmcarthur_ has joined #zuul14:43
fungiif you were interested in trying to implement it, you could try to plumb in an attribute using https://zuul-ci.org/docs/zuul/user/config.html#attr-job.ansible-version as an example, and maybe just have it as an integer count of the number of -v's to pass to the command14:44
clarkbarmstrongs: there is an ara output role in zuul-jobs you can add to your jobs14:44
clarkbfungi: it is sublter than that. Console logs are generated within ansible by a shim we ship14:44
clarkbthey arent prt of the normal -vvvv processing in ansible iirc14:45
fungiohh... so it wouldn't matter how ansible itself was invoked by the executor anyway?14:45
clarkbcorrect14:46
fungiarmstrongs: an example of the ara integration you get by adding the ara output role from zuul-jobs: http://logs.openstack.org/46/657046/5/promote/swift-promote-image/ffb657d/ara-report/14:46
fungiagain, that's only after the job completes though, not available while it's in progress14:46
*** jamesmcarthur has quit IRC14:47
armstrongsthanks for the info everyone14:47
corvusarmstrongs: zuul does have streaming console logs for watching tests as they run -- so anything that goes to stdout of a command task should stream in real time14:47
fungione thing we've talked about wanting for in-progress jobs, and the streaming protocol choice explicitly allows for this if the necessary glue is written, is the ability to stream additional logs from the job by specifying a particular logfile you want to see14:47
corvusfungi: oh yeah, i still think that will be great to add :)14:48
fungiso that would be something possibly worth working on if you have qa engineers who like to watch logs14:48
clarkbthr way to think of the console log is it shows you what your job us doing not what ansible is doing14:49
armstrongsah ok so if i shell out to tests they will be captured. Its just teh ansible bits that are surpressed14:49
clarkbso you can invrease the verbosityof your commands run by ansible14:49
armstrongsthe ara reports look cool14:49
corvusalso if there's something in particular that shows up if you run ansible from the command line but is missing in the streaming/saved logs, we might be able to correct that (the logging plugin is custom zuul code which is similar to the standard ansible log, but not 100% the same)14:49
*** hashar has joined #zuul14:50
corvusarmstrongs: yeah, we did the command streaming specifically to preserve the behavior for people who liked to watch "test..OK" a lot :)14:50
fungiarmstrongs: yeah, as an example, in our deployment we have some fairly complex integration test suites implemented as massive shell script spaghetti, and use `set -x` to turn on echoing of every shell command run by the script14:50
*** pcaruana has joined #zuul14:53
Shrewstobiash: lgtm. is there a nodepool equivalent change yet? i couldn't find it14:54
tobiashShrews: not yet14:57
tobiashI'm working iteratively through the whole stack14:57
Shrewsk14:57
corvuseverything up to that point is +3d (again!)15:08
tobiashand the first change failed in the gate :(15:09
tobiashI've rechecked only the first three for now15:09
tobiashmaybe it's easier to get them in slowly ;)15:09
corvusi'm heading out, probably away again until wednesday (though i'll try to review on the plane again)15:09
corvustobiash: it must get nervious with all those changes behind them15:10
*** themroc has quit IRC15:22
openstackgerritMerged zuul/zuul master: Fix typo in log message  https://review.opendev.org/66011815:29
*** hashar has quit IRC16:00
*** chandankumar is now known as raukadah16:01
*** mattw4 has joined #zuul16:06
*** mattw4 has quit IRC16:20
*** jangutter has quit IRC16:50
*** sshnaidm is now known as sshnaidm|afk17:00
*** jpena is now known as jpena|off17:07
*** mattw4 has joined #zuul17:14
fungipabelanger: i'm about to update https://review.opendev.org/659674 but not sure if you've seen my replies to your comments17:16
mordredtobiash: did we ever land your statsd_exporter mapping file?17:19
tobiashmordred: I don't think so17:20
mordredtobiash: good, that explains why I can't find it - and not just that I'm dumb :)17:20
tobiashmordred: I'm not sure if it was a change or just somewhere on paste.openstack.org17:21
mordredtobiash: yeah - I don't see anything in gerrit, so I'm guessing it was just a paste - and then I think tristanC and I went somewhat down the path of seeing if we could support both sanely, and then didn't finish that17:22
tobiashmordred: http://paste.openstack.org/show/729542/17:23
tobiashand http://paste.openstack.org/show/729541/17:23
tobiashmordred: I think that's why I didn't create a change17:24
tobiashthose are probably a bit outdated17:24
tobiashI think I'll create a change with my recent mappings tomorrow17:24
mordredcool - that'll be a good thing to point people to who are doing k8s deploys17:30
*** jamesmcarthur has joined #zuul17:31
*** jamesmcarthur_ has quit IRC17:34
openstackgerritTobias Henkel proposed zuul/zuul master: Annotate node request processing with event id  https://review.opendev.org/65888917:40
openstackgerritTobias Henkel proposed zuul/zuul master: WIP: Annotate builds with event id  https://review.opendev.org/65889517:40
openstackgerritJeremy Stanley proposed zuul/zuul master: Install latest git-review from PyPI in quickstart  https://review.opendev.org/65967417:48
*** bhavikdbavishi has joined #zuul17:50
*** armstrongs has quit IRC18:04
openstackgerritMerged zuul/zuul master: Annotate github logs with the event id  https://review.opendev.org/65864518:15
tobiash\o/18:20
openstackgerritDavid Shrewsbury proposed zuul/nodepool master: WIP: Convert to using py3 pathlib  https://review.opendev.org/66019118:31
openstackgerritMerged zuul/zuul master: Annotate gerrit event logs  https://review.opendev.org/65864618:39
mordredtobiash: woot!18:44
tobiashNext one failed :(18:45
*** bhavikdbavishi has quit IRC19:00
*** jamesmcarthur has quit IRC19:05
*** jamesmcarthur has joined #zuul19:19
mordredbooo19:35
*** toabctl has quit IRC19:43
*** toabctl has joined #zuul19:46
*** dmsimard5 has joined #zuul19:50
*** dmsimard has quit IRC19:51
openstackgerritDavid Shrewsbury proposed zuul/nodepool master: Use py3 pathlib in DibImageFile  https://review.opendev.org/66019120:07
openstackgerritMerged zuul/zuul master: Attach event to queue item  https://review.opendev.org/65864720:17
mordredShrews: your python3 is too modern for my old brainhole20:28
Shrewsmordred: i find it more palatable than all the os.foo.bar calls20:29
mordredShrews: yah. looks non-insane20:30
Shrewsplus... objects and stuff20:30
openstackgerritMerged zuul/zuul master: Annotate some logs in the scheduler with event id  https://review.opendev.org/65864820:30
Shrewsi think my -2 was unnecessary. still convincing myself20:30
Shrewsmordred: fwiw, i blame https://datawhatnow.com/things-you-are-probably-not-using-in-python-3-but-should/20:31
fungiwow, i should read this20:34
Shrewsi can't wait to enum all the things20:34
fungipathlib overloaded the / operator as concatenation? intriguing20:34
mordredShrews: ooh. dataclasses look nice20:35
mordredShrews, fungi: yes - that was a helpful post20:35
fungiyep, looking forward to being able to use data classes once 3.7 is better entrenched20:39
fungii have to say though, while the items on that list were usefully obscure, it was disappointingly short20:39
fungithere's a ton of great stuff in py3k which folks fail to take advantage of if they're too used to 2.x20:40
Shrewsthe problem with all the great new things in py3 is the greatness being distributed across multiple versions, so it makes discovering them rather difficult unless you really go digging, so most people (myself included) don't make a whole-hearted attempt.20:43
fungiand i'll be the first to admit i still write c-style printf format strings20:43
Shrewsblogs that point them out (like that one) are super useful20:43
Shrewsi like the f-strings. i'd like to move our min version for that alone20:45
fungiyeah, i just need to remember about them long enough to actually start using them20:46
fungi"foo %s bar %s baz" % (xyzzy, plugh) is just too ingrained in my fingers20:47
fungineed to remember i can f"foo {xyzzy} bar {plugh} baz" and save a ton of typing20:47
openstackgerritMerged zuul/zuul master: Annotate logs in the zuul driver with event ids  https://review.opendev.org/65864920:48
fungigranted, that example save 6 characters, of which 3 were optional ;)20:49
mordredfungi: :)21:02
mordredShrews: I concur, I am looking forward to f strings and am excited to move our min21:03
*** tjgresha has joined #zuul21:03
*** mattw4 has quit IRC21:04
*** tjgresha has quit IRC21:05
openstackgerritMerged zuul/zuul master: Add event id to timer events  https://review.opendev.org/65865021:08
clarkbShrews: left a couple notes on the pathlib change. Its possible the second one is realted to the failing tests, but of that I am not certain21:23
*** mattw4 has joined #zuul21:24
Shrewsi am looking into the fail already. it's related to file ext21:24
clarkbya my second comment is related to that as well21:24
clarkbbasically there is ab ehavior change between the old and new code21:24
Shrewsclarkb: i think your rsplit comment is wrong21:26
Shrews>>> s = "foo.qcow2.md5"21:27
Shrews>>> s.rsplit('.', 1)21:27
Shrews['foo.qcow2', 'md5']21:27
clarkboh bah I read is as lsplit for some reason but its rsplit21:27
clarkbso ya nevermind I think it is the same then21:27
openstackgerritMerged zuul/zuul master: Annotate pipeline processing with event id  https://review.opendev.org/65865121:27
clarkbI think because lsplit is what makes sense to me there21:27
clarkbbut I guess filenames could haev .'s in them21:28
Shrewsclarkb: well that's where the new code makes that easier to read  :)  i still have a problem with cleaning up the checksum files though. will have to figure that one out tomorrow21:38
*** pcaruana has quit IRC21:40
Shrewsbut yeah, i have problems remembering rsplit vs lsplit too. Path.suffix reads much better21:40
clarkbya the only thing that reads weirder to me is the / concatenation (+ is used for that everywhere else in python so uh why not here)21:41
*** jamesmcarthur has quit IRC21:45
openstackgerritMerged zuul/zuul master: Annotate merger logs with event id  https://review.opendev.org/65865221:45
*** jamesmcarthur has joined #zuul21:46
fungiclarkb: especially since / is only the unix file separator. other platforms use \ or : and python's path handling figures it out22:09
fungiso to choose one of them which happens to be an available operator and overload that is... an odd choice22:09
openstackgerritMerged zuul/zuul master: Annotate job freezing logs with event id  https://review.opendev.org/65888822:18
pabelangerI cannot remember, does https://zuul-ci.org/docs/zuul/user/config.html#attr-job.files affect jobs in a periodic pipeline?22:29
pabelangermy gut says no22:29
clarkbpabelanger: iirc no because periodic timer triggers don't have files22:30
clarkbits possible the result is that you'll never get that job to run in periodic with a files matcher22:31
pabelangeryah, I'll test it out tomorrow for sure22:32
*** dmsimard5 is now known as dmsimard22:44
SpamapSpabelanger: IIRC you can use  `files: []` in the attachment to the periodic pipeline.23:21
SpamapSbut that may also just backfire and still match nothing23:22
*** rlandy has quit IRC23:25
*** jamesmcarthur has quit IRC23:44
tristanCmordred: Shrews: still no reproducer for the react-script bump ( https://review.opendev.org/659991 ). Do you remember on which page it failed?23:47
clarkbtristanC: it failed on zuul.openstack.org's status page23:47
mordredtristanC, clarkb: yeah.23:47
mordredalthough that seems to be working this time23:48
clarkbit also failed on zuul.opendev.org's openstack tenant status page23:48
clarkbso it was likely something to do with the openstack status json23:48
mordredhrm23:48
mordredclarkb: the old builds are also now working23:48
tristanCcurrently in the multi-tenant build, ansible status there are 2 changes from github that also seems to be working fine23:48
clarkbmaybe the thing to do is fix the minimization breaks debugging problem, then we can reenable it and if it happens again hopefully we get the data necessary to debug23:48
mordredso it may have been something in the status.json at that moment that isn't there now23:49
mordredtristanC: yes - what clarkb said - the biggest issue was that the error message in the js debugger had no context for debugging at all23:50
tristanCthat's odd, the console log should give a pointer at the map or source file23:50
clarkbit gave a link to a generic react debug site23:50
mordredyes - that would be my expectations - instead it gave a message with a link to ^^23:50
mordredyeah, that23:50
mordredit was very strange23:51
tristanClet me introduce a bug then...23:52
openstackgerritTristan Cacqueray proposed zuul/zuul master: DNM: this should cause a React exception  https://review.opendev.org/66023123:53
openstackgerritTristan Cacqueray proposed zuul/zuul master: DNM: this should cause a React exception  https://review.opendev.org/66023123:54

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