*** jamesmcarthur has quit IRC | 00:00 | |
*** jamesmcarthur has joined #zuul | 00:00 | |
*** jamesmcarthur has quit IRC | 00:02 | |
*** jamesmcarthur has joined #zuul | 00:32 | |
*** jamesmcarthur has quit IRC | 01:01 | |
*** sdake has joined #zuul | 01:06 | |
*** jesusaur has quit IRC | 01:19 | |
*** jesusaur has joined #zuul | 01:25 | |
*** sdake has quit IRC | 01:44 | |
*** sdake has joined #zuul | 01:48 | |
*** sdake has quit IRC | 01:59 | |
*** sdake has joined #zuul | 02:05 | |
*** sdake has quit IRC | 02:08 | |
*** sdake has joined #zuul | 02:42 | |
*** sdake has quit IRC | 02:44 | |
*** sdake has joined #zuul | 02:50 | |
*** jamesmcarthur has joined #zuul | 03:01 | |
*** jamesmcarthur has quit IRC | 03:05 | |
*** sdake has quit IRC | 03:24 | |
*** sdake has joined #zuul | 03:26 | |
*** jamesmcarthur has joined #zuul | 03:27 | |
*** sdake has quit IRC | 03:41 | |
*** jamesmcarthur has quit IRC | 03:41 | |
*** sdake has joined #zuul | 05:09 | |
*** snapiri has joined #zuul | 05:19 | |
tristanC | pabelanger: zuul-maint: i've started a zuul-discuss thread about https://review.openstack.org/632620 , what's the next step to land this change? | 05:22 |
---|---|---|
*** saneax has joined #zuul | 05:26 | |
openstackgerrit | Tristan Cacqueray proposed openstack-infra/zuul master: Separate out executor server from runner https://review.openstack.org/607079 | 05:41 |
openstackgerrit | Tristan Cacqueray proposed openstack-infra/zuul master: zuul-runner: implement prep-workspace https://review.openstack.org/607082 | 05:41 |
*** raukadah has quit IRC | 05:45 | |
*** chandankumar has joined #zuul | 05:46 | |
*** sdake has quit IRC | 05:48 | |
*** sdake has joined #zuul | 05:53 | |
*** sdake has quit IRC | 06:01 | |
*** sdake has joined #zuul | 06:02 | |
*** sdake has quit IRC | 06:03 | |
openstackgerrit | Tristan Cacqueray proposed openstack-infra/zuul master: Add API endpoint to get frozen jobs https://review.openstack.org/607077 | 06:26 |
openstackgerrit | Tristan Cacqueray proposed openstack-infra/zuul master: Get executor job params https://review.openstack.org/607078 | 06:26 |
openstackgerrit | Tristan Cacqueray proposed openstack-infra/zuul master: Separate out executor server from runner https://review.openstack.org/607079 | 06:26 |
openstackgerrit | Tristan Cacqueray proposed openstack-infra/zuul master: zuul-runner: implement prep-workspace https://review.openstack.org/607082 | 06:26 |
openstackgerrit | Tristan Cacqueray proposed openstack-infra/zuul master: zuul-runner: add yaml based configuration file https://review.openstack.org/640672 | 06:26 |
*** badboy has joined #zuul | 06:54 | |
tristanC | corvus: is there an example of job using provides/requires in opendev's zuul? | 07:00 |
*** quiquell|off is now known as quiquell | 07:03 | |
*** [GNU] has joined #zuul | 07:19 | |
*** quiquell is now known as quiquell|brb | 07:43 | |
*** themroc has joined #zuul | 07:44 | |
*** snapiri has quit IRC | 07:52 | |
*** gtema has joined #zuul | 07:58 | |
*** jesusaur has quit IRC | 08:06 | |
*** delhage has left #zuul | 08:10 | |
*** jesusaur has joined #zuul | 08:10 | |
*** panda|ruck|off is now known as panda|ruck | 08:12 | |
*** quiquell|brb is now known as quiquell | 08:18 | |
*** pcaruana has joined #zuul | 08:25 | |
*** hashar has joined #zuul | 08:36 | |
*** jpena|off is now known as jpena | 08:56 | |
openstackgerrit | Matthieu Huin proposed openstack-infra/zuul master: [WIP] Add Authorization Rules configuration https://review.openstack.org/639855 | 09:43 |
*** electrofelix has joined #zuul | 10:07 | |
openstackgerrit | Matthieu Huin proposed openstack-infra/zuul master: Proposed spec: tenant-scoped admin web API https://review.openstack.org/562321 | 10:25 |
*** gtema has quit IRC | 10:34 | |
*** gtema has joined #zuul | 10:47 | |
*** saneax has quit IRC | 10:52 | |
*** gtema has quit IRC | 10:56 | |
badboy | hi | 11:23 |
badboy | is it possible to trigger a job based on a label? | 11:23 |
*** dkehn has quit IRC | 11:32 | |
*** gtema has joined #zuul | 11:33 | |
*** hashar has quit IRC | 11:43 | |
*** hashar has joined #zuul | 12:08 | |
*** saneax has joined #zuul | 12:29 | |
*** jpena is now known as jpena|lunch | 12:38 | |
*** edmondsw has joined #zuul | 12:50 | |
*** zbr has quit IRC | 12:53 | |
*** zbr|ssbarnea has joined #zuul | 12:54 | |
*** zbr|ssbarnea has quit IRC | 12:54 | |
*** zbr has joined #zuul | 12:55 | |
*** rlandy has joined #zuul | 12:57 | |
*** saneax has quit IRC | 13:15 | |
*** sdake has joined #zuul | 13:24 | |
*** jamesmcarthur has joined #zuul | 13:24 | |
*** jpena|lunch is now known as jpena | 13:31 | |
*** jamesmcarthur has quit IRC | 13:32 | |
*** jamesmcarthur has joined #zuul | 13:33 | |
*** mhu has quit IRC | 13:36 | |
*** mhu has joined #zuul | 13:37 | |
*** jamesmcarthur has quit IRC | 13:38 | |
*** rfolco is now known as rfolco|pto | 13:50 | |
*** jamesmcarthur has joined #zuul | 14:03 | |
*** jamesmcarthur has quit IRC | 14:06 | |
*** jamesmcarthur has joined #zuul | 14:06 | |
*** pwhalen has quit IRC | 14:13 | |
*** sdake has quit IRC | 14:14 | |
*** gtema has quit IRC | 14:23 | |
*** jamesmcarthur has quit IRC | 14:24 | |
*** sdake has joined #zuul | 14:25 | |
*** pwhalen has joined #zuul | 14:25 | |
*** sdake has quit IRC | 14:25 | |
*** pcaruana has quit IRC | 14:31 | |
*** sdake has joined #zuul | 14:38 | |
*** jamesmcarthur has joined #zuul | 14:38 | |
tobiash | badboy: in github? | 14:41 |
tobiash | yes | 14:41 |
tobiash | badboy: you can use the labeled action: https://zuul-ci.org/docs/zuul/admin/drivers/github.html#trigger-configuration | 14:42 |
tobiash | (in the pipeline config) | 14:42 |
*** sdake has quit IRC | 14:49 | |
*** sdake has joined #zuul | 14:55 | |
openstackgerrit | Matthieu Huin proposed openstack-infra/zuul master: [WIP] Add Authorization Rules configuration https://review.openstack.org/639855 | 14:56 |
openstackgerrit | Monty Taylor proposed openstack-infra/nodepool master: Remove TaskManager and just use keystoneauth https://review.openstack.org/640643 | 15:08 |
*** sdake has quit IRC | 15:11 | |
openstackgerrit | Monty Taylor proposed openstack-infra/nodepool master: Remove TaskManager and just use keystoneauth https://review.openstack.org/640643 | 15:12 |
corvus | tristanC: re provides/requires -- not fully functioning yet, but this one does: http://git.openstack.org/cgit/opendev/base-jobs/tree/zuul.yaml#n177 -- we need to restart nodepool/zuul for provider affinity to continue testing that (we had jobs unable to contact the buildset registry because ipv4-only regions couldn't talk to ipv6-only) | 15:14 |
*** sdake has joined #zuul | 15:15 | |
Shrews | oh, speaking of nodepool restarts, i don't think we've restarted launchers since we added back the port cleanup code | 15:16 |
Shrews | so we'll have a couple of things to watch there | 15:17 |
jkt | tristanC: I think opendev doesn't use provides/requires yet (it hasn't been in a releae yet), but I've used it successfuly | 15:17 |
mordred | Shrews: also - we cut a new openstacksdk release which touched image uploading code ... it's been tested, obviously - but also gremlins exist in the world, so we should watch the builders next restart too | 15:18 |
jkt | tristanC: this is my producer, https://gerrit.cesnet.cz/plugins/gitiles/CzechLight/dependencies/+/master , and here's one consumer: https://gerrit.cesnet.cz/plugins/gitiles/CzechLight/netconf-cli/+/master | 15:19 |
mordred | (the changes to image code were organizational - the code is ultimately the same code, but it got moved around) | 15:19 |
Shrews | mordred: wheeeee | 15:19 |
jkt | tristanC: it's passing three different artifacts; some additional pieces are at https://gerrit.cesnet.cz/plugins/gitiles/ci/zuul-jobs-cesnet/+/master | 15:19 |
fungi | jkt: being in a release isn't a requirement for opendev's zuul to use a new feature... we continuously deploy from master and even act as a frequent proving ground for unreleased features | 15:24 |
fungi | though i don't know of any provides/requires examples in our configuration right off the top of my head | 15:25 |
*** pcaruana has joined #zuul | 15:25 | |
*** chandankumar is now known as raukadah | 15:32 | |
openstackgerrit | Monty Taylor proposed openstack-infra/nodepool master: Remove TaskManager and just use keystoneauth https://review.openstack.org/640643 | 15:38 |
*** quiquell is now known as quiquell|off | 15:47 | |
*** sdake has quit IRC | 16:00 | |
*** themroc has quit IRC | 16:00 | |
tobiash | corvus: I have an interesting case where the ansible ssh connection retry mechanism (we hard code 3 atm) causes more harm than it helps | 16:10 |
tobiash | corvus: during a compile job ansible thought the connection has been lost and it retried that single task (while the first try in fact was still running). So in the end we had two compile processes running at the same time which failed the job. | 16:11 |
tobiash | corvus: so I think this is even potentially dangerous and we should think about whether we want this behavior or instead rely on unreachable nodes detection and retry the whole job instead | 16:12 |
tobiash | the idea of ansible is that everything is idempotent so executing the same task multiple times is normally ok in normal use cases. But in ci use cases this is not necessarily the case | 16:13 |
tobiash | and then it might be just incorrect to retry a task we don't even know if it's still running | 16:14 |
mordred | tobiash: did the connection get lost because the compile was making the machine seem unresponsive? | 16:14 |
mordred | retrying a task that could be running does seem more dangerous than retrying a task where we weren't able to connect in the first place - do we have any way of distinguishing the two? | 16:15 |
tobiash | mordred: I don't know. I just saw that the json log looks normal (because ansible doesn't store the result of the first try somewhere) while the job-output.txt showed what actually happened (task restart in parallel to the still running task) | 16:16 |
tobiash | no, we even don't get any hint about it because that's deep inside ansible | 16:17 |
tobiash | and if the connection is terminated there is no way of knowing if the process executed by that ssh session was interrupted or successful or failed. | 16:21 |
Shrews | mordred or SpamapS: have opinions on a good rust tutorial? | 16:21 |
tobiash | so I think the most correct thing here would be to not do a retry which should result in an unreachable result of the task and thus a retry of the job | 16:21 |
mordred | Shrews: the rust book is actually pretty solid https://doc.rust-lang.org/book/ | 16:23 |
mordred | tobiash: great - yeah - not being able to distinguish the two is not awesome | 16:24 |
Shrews | mordred: thx | 16:24 |
corvus | Shrews, mordred: i spent a good deal of the weekend reading the rust book. i'm in chapter 18 now. it is quite good. keep in mind there's also "rust by example", depending on your learning style. https://doc.rust-lang.org/#learn-rust | 16:30 |
corvus | there are some things that are completely new in rust though (eg, ownership and lifetime annotations), so that even if you don't start with the book, there are probably some things worth going to the book and reading later to get more background. | 16:33 |
corvus | tobiash, mordred: we may want to pull in pabelanger on the retry question too, istr he worked on that a bit. | 16:34 |
Shrews | corvus: ch 18? fast reader | 16:35 |
clarkb | corvus: Shrews the rust zuul preview tool is actually a really good illustration of ownership too due to its use of anonymous functions and variables with limited scope life stored in long lived cache | 16:35 |
corvus | Shrews: it rained a lot this weekend | 16:36 |
Shrews | corvus: since i'm mostly still laid up from my injuries, hopefully i can plow through as quickly | 16:37 |
corvus | Shrews: it's like you planned it! :) | 16:38 |
pabelanger | tobiash: what type of task was your compile job? some sort of long lived shell / command? | 16:43 |
tobiash | looks like I have to learn rust too once y'all reimplement zuul in rust ;) | 16:43 |
tobiash | pabelanger: yes, long lived shell task | 16:43 |
pabelanger | I'm not sure I'd want to remove retries completely, but we did discuss maybe exposing the value to users to modify | 16:43 |
corvus | pabelanger: do you think retries help, or are necessary? | 16:44 |
tobiash | pabelanger: we already have job retries in place for connection failures | 16:44 |
pabelanger | corvus: in our case, I think they have helped. We have pretty poor networking in our cloud, however I don't really have numbers to back it up | 16:45 |
tobiash | But maybe a config option is a reasanoble comprimise. But I have to say that this can lead to hard to debug job failures | 16:45 |
pabelanger | I'm open to a revert, but need to let people know this could result in a higher number of retries for jobs | 16:47 |
pabelanger | but also okay with config options too | 16:48 |
SpamapS | Shrews: mordred and corvus have you covered. The book is everything. :) | 16:48 |
tobiash | the retry mechanism as ansible implements it is actually only valid if every task is idempotent and concurrency safe | 16:48 |
tobiash | which is not the case for typical build jobs | 16:48 |
SpamapS | Shrews: also to contrast with the preview tool code, which is tight and focused on a single thing, here's a more scripty Rust thing that I wrote: https://github.com/ToolsForHumans/shyaml/blob/master/src/main.rs | 16:49 |
tobiash | so it's a trade of | 16:49 |
SpamapS | (and I use every day) | 16:49 |
pabelanger | tobiash: right, we try to use creates field for shell when possible, but agree that is much harder with long running tasks. | 16:50 |
corvus | tobiash, pabelanger: when the retries=3 setting was added, we had not yet implemented the job_unreachable_file. my understanding is that means we were missing some cases where ansible should have been reporting unreachable (where, if it had, we would have retried the job) | 16:50 |
corvus | tobiash, pabelanger: since we added retries=3 to deal with "unreachable" situations, i wonder if, now that we have the job_unreachable_file, if it would be okay to remove retries=3 and rely on job retries? | 16:51 |
tobiash | corvus, pabelanger: I think that would at least the 100% correct way | 16:52 |
tobiash | so retries=3 would be just an optimization to do a smaller scoped retry at the expense of possible races | 16:52 |
pabelanger | just looking to see what job_unreachable_file does, first I have heard of that | 16:53 |
tobiash | so I would vote for either removing it or defaulting to 0 and explain in the docs that this is a potentially dangerous optimization | 16:53 |
tobiash | pabelanger: tldr is that ansible doesn't return the correct result code for unreachable so we use the callback to detect that | 16:54 |
openstackgerrit | Matthieu Huin proposed openstack-infra/zuul master: [WIP] Add Authorization Rules configuration https://review.openstack.org/639855 | 16:54 |
tobiash | pabelanger: https://git.zuul-ci.org/cgit/zuul/tree/zuul/ansible/callback/zuul_unreachable.py#n40 | 16:55 |
pabelanger | tobiash: corvus: I would be okay with a revert, however I do think there might be cases where operators understand the usage of retries and want to enable / disable it. Retrying a job but having nodepool relaunch it again, is expensive compared to ansible just retrying again. | 16:57 |
pabelanger | and given the $$$ cost to boot another VM, could affect budgets | 16:57 |
mhu | Hello, could I get some eyes on the tenant-scoped web API spec: https://review.openstack.org/#/c/562321/ ? I've added authZ handling and I'd like to get some feedback before I get too much into my PoC | 16:57 |
tobiash | corvus, pabelanger: so is it a reasonable compromise for all of us to default to 0 and make it configurable (with warning in the docs)? | 16:58 |
pabelanger | tobiash: that wfm if others are good | 16:59 |
corvus | pabelanger: hrm. it seems like it would be difficult for an operator to say that it's correct. based on what tobiash is saying, whether it's correct to use retries= depends on exactly how an individual task is written | 16:59 |
*** hashar has quit IRC | 17:00 | |
corvus | (does ansible have a "mosh" connection plugin? :) | 17:01 |
tobiash | mosh would probably solve that ;) | 17:02 |
pabelanger | corvus: I would agree, depending on which task for sure. And possible the reason why we haven't seem more of the case | 17:04 |
mordred | corvus: we should totally write a mosh connection plugin :) | 17:07 |
pabelanger | just asked on internal ansible channel, there seems to have been attempts at mock connection plugin, but nothing more then friday hacking it seems | 17:14 |
*** sdake has joined #zuul | 17:22 | |
*** hashar has joined #zuul | 17:28 | |
*** saneax has joined #zuul | 17:28 | |
openstackgerrit | Matthieu Huin proposed openstack-infra/zuul master: [WIP] Add Authorization Rules configuration https://review.openstack.org/639855 | 17:28 |
mordred | pabelanger: s/mock/mosh/ right? :) | 17:32 |
pabelanger | mordred: yes! | 17:32 |
clarkb | as a side note, the jobs themselves would have to avoid the network as well if the network is flaky for improvements to ansible network connectivity to have a major impact on job reliability | 17:33 |
clarkb | I'm not sure how practical it is to invest significantly in making the ansible "ssh" connection reliable on flaky entworks when pip install will fail | 17:33 |
tobiash | A mock plugin would be great too and make all users happy ;) | 17:37 |
mordred | tobiash: ++ | 17:43 |
clarkb | Hey I've been asked if we can get reviews on https://review.openstack.org/#/c/639871/ to get the summit banner thing up on the zuul site | 17:43 |
pabelanger | clarkb: in our use case, the executors are on the bad network, test nodes work well. However, we still haven't made the change to zuul executor zones, so that is likely another way we'll be better with out retries | 17:45 |
corvus | clarkb: lgtm | 17:46 |
clarkb | ty | 17:46 |
dmsimard | The failure mode of zuul-web during whatever is occuring in upstream openstack-infra is not very cool | 17:47 |
fungi | as in zuul-web running and accepting connections while the scheduler is offline? | 17:48 |
dmsimard | Yeah, there should be something better than a white page | 17:48 |
fungi | looks like it's back up now, but yeah, i agree it tends to look confusing when the scheduler is out of service | 17:49 |
dmsimard | Maybe a message to the effect that the web interface was not able to connect to the scheduler ? Would be useful as an end user :D | 17:49 |
dmsimard | I can create a story about it perhaps. | 17:50 |
corvus | dmsimard: it's supposed to do that. there is a javascript bug. a bugfix would be appreciated. | 17:50 |
dmsimard | corvus: my javascript/react skills are most definitely limited but I'll create a story | 17:51 |
corvus | dmsimard: assign tristanC to it, he said he'd fix it last time this was reported | 17:52 |
dmsimard | wfm | 17:52 |
dmsimard | https://storyboard.openstack.org/#!/story/2005134 for ^ | 17:57 |
josefwells | my change: https://review.openstack.org/640548 failed testing, but I looked and it seems unrelated. Didn't see it on elastic-search or a launchpad-bug | 17:58 |
openstackgerrit | Merged openstack-infra/zuul-website master: Add a promotional message banner and events list https://review.openstack.org/639871 | 17:58 |
fungi | josefwells: yeah, looks like test_client_dequeue_change_by_ref had opposite the expected result | 18:21 |
fungi | it's possible that test is racy | 18:21 |
fungi | i agree i don't see how a change to example playbooks in the documentation could cause that | 18:21 |
fungi | josefwells: if you leave a review comment on that change starting with the word "recheck" (no quotes) it should get tested again | 18:22 |
*** electrofelix has quit IRC | 18:22 | |
*** saneax has quit IRC | 18:25 | |
*** jpena is now known as jpena|off | 18:27 | |
*** jamesmcarthur_ has joined #zuul | 18:32 | |
*** hashar is now known as hasharDinner | 18:32 | |
*** jamesmcarthur has quit IRC | 18:35 | |
*** jamesmcarthur_ has quit IRC | 18:41 | |
*** panda|ruck is now known as panda|ruck|off | 18:41 | |
fungi | looks like corvus did that already | 18:49 |
corvus | yep! the job that matters passed, so we should be able to land that soon :) | 18:50 |
*** jamesmcarthur has joined #zuul | 18:53 | |
*** pcaruana has quit IRC | 18:56 | |
josefwells | thanks fungi and corvus, I found this stuff while getting my quickstart going (and making changes for github instead of gerrit) thought I would share the love and walk through your process as well | 18:57 |
josefwells | I find the elastic-search stuff very interesting too, might end up picking that up for my processes as well | 18:57 |
fungi | thanks josefwells! it's much appreciated | 18:57 |
*** jlvillal has quit IRC | 18:58 | |
*** jamesmcarthur has quit IRC | 18:59 | |
*** jlvillal has joined #zuul | 18:59 | |
*** jamesmcarthur has joined #zuul | 18:59 | |
*** electrofelix has joined #zuul | 19:02 | |
*** jamesmcarthur has quit IRC | 19:04 | |
*** sdake has quit IRC | 19:07 | |
fungi | and tox-py36 did pass when the change was rechecked, so test_client_dequeue_change_by_ref doesn't seem to be consistently broken | 19:09 |
*** electrofelix has quit IRC | 19:10 | |
*** jamesmcarthur has joined #zuul | 19:22 | |
*** openstackgerrit has quit IRC | 19:23 | |
josefwells | yes, reducing false-fails is very important in my system as well, where test times can easily reach into 4 hours. | 19:33 |
*** openstackgerrit has joined #zuul | 19:34 | |
openstackgerrit | Merged openstack-infra/zuul master: quickstart: web and others wait on mysql to start https://review.openstack.org/640548 | 19:34 |
tobiash | corvus: responded on 634597 | 19:46 |
tobiash | corvus: do you still need 638596 for testing docker stuff or is it safe to recheck and land it? | 19:49 |
corvus | tobiash: it can land | 20:03 |
corvus | tobiash: re reply: ack, thanks | 20:04 |
tobiash | corvus: thx | 20:04 |
openstackgerrit | Tobias Henkel proposed openstack-infra/zuul master: Log exception on module failure with empty stdout https://review.openstack.org/640650 | 20:09 |
openstackgerrit | Tobias Henkel proposed openstack-infra/zuul master: Manage ansible installations within zuul https://review.openstack.org/631930 | 20:09 |
*** jamesmcarthur has quit IRC | 20:19 | |
*** jamesmcarthur has joined #zuul | 20:19 | |
*** hasharDinner is now known as hashar | 20:34 | |
*** sdake has joined #zuul | 20:52 | |
*** jamesmcarthur has quit IRC | 20:58 | |
*** jamesmcarthur has joined #zuul | 20:59 | |
*** jamesmcarthur has quit IRC | 20:59 | |
*** jamesmcarthur has joined #zuul | 20:59 | |
openstackgerrit | Tobias Henkel proposed openstack-infra/zuul master: Manage ansible installations within zuul https://review.openstack.org/631930 | 21:00 |
tobiash | josefwells, corvus, fungi: commented on https://review.openstack.org/640548 | 21:04 |
openstackgerrit | Merged openstack-infra/zuul master: Optionally disable disk_limit_per_job https://review.openstack.org/638596 | 21:05 |
*** jamesmcarthur has quit IRC | 21:06 | |
corvus | tobiash: how did the job work if the playbook wasn't mounted? | 21:06 |
tobiash | corvus: because the startup script doesn't care about the failure | 21:06 |
tobiash | due to ';' instead of '&&' | 21:06 |
corvus | tobiash: i guess we should fix both of those things :) | 21:06 |
tobiash | corvus: the fix is also part of the ansible stack (because it will replace the playbook with a shell script) | 21:07 |
tobiash | so we could fix this or wait for the multi-ansible stack depending how urgent this is | 21:07 |
tobiash | I'm fine with both options | 21:08 |
openstackgerrit | Tobias Henkel proposed openstack-infra/zuul master: Manage ansible installations within zuul https://review.openstack.org/631930 | 21:08 |
fungi | tobiash: mm, good catch on both counts | 21:08 |
tobiash | lemme fix that real quick | 21:09 |
openstackgerrit | Tobias Henkel proposed openstack-infra/zuul master: Fix missing wait-to-start playbook in quick start https://review.openstack.org/640871 | 21:11 |
tobiash | corvus, fungi, josefwells: ^ | 21:11 |
corvus | tobiash: thx! | 21:12 |
tobiash | yw | 21:12 |
fungi | much obliged | 21:12 |
openstackgerrit | Tobias Henkel proposed openstack-infra/zuul master: Fix test race in test_client_dequeue_change_by_ref https://review.openstack.org/640878 | 21:30 |
tobiash | corvus, fungi: I think this might fix the test race that josefwells hit in 640548 ^ | 21:31 |
*** jamesmcarthur has joined #zuul | 21:37 | |
*** sdake has quit IRC | 21:41 | |
corvus | i wonder why that uses a timer trigger in the first place? | 21:43 |
*** sdake has joined #zuul | 21:43 | |
corvus | tobiash: thanks! | 21:44 |
tobiash | corvus: the comment says because it wants a ref based change | 21:44 |
tobiash | however that could probably be a post job as well | 21:44 |
corvus | or tag | 21:46 |
openstackgerrit | Tobias Henkel proposed openstack-infra/zuul master: Manage ansible installations within zuul https://review.openstack.org/631930 | 21:47 |
tobiash | yepp | 21:48 |
*** klindgren_ has joined #zuul | 21:52 | |
*** shanemcd has quit IRC | 21:53 | |
*** klindgren has quit IRC | 21:53 | |
*** smcginnis has quit IRC | 21:53 | |
*** jamesmcarthur has quit IRC | 21:57 | |
*** shanemcd has joined #zuul | 21:57 | |
*** jamesmcarthur has joined #zuul | 21:58 | |
openstackgerrit | Matthieu Huin proposed openstack-infra/zuul master: [WIP] Web: plug the authorization engine https://review.openstack.org/640884 | 21:59 |
*** jamesmcarthur has quit IRC | 22:12 | |
*** jamesmcarthur has joined #zuul | 22:13 | |
*** sdake has quit IRC | 22:50 | |
openstackgerrit | Matthieu Huin proposed openstack-infra/zuul master: [WIP] Web: plug the authorization engine https://review.openstack.org/640884 | 22:51 |
*** smcginnis has joined #zuul | 22:54 | |
*** jamesmcarthur has quit IRC | 22:57 | |
*** jamesmcarthur has joined #zuul | 22:58 | |
*** jamesmcarthur has quit IRC | 23:00 | |
*** hashar has quit IRC | 23:10 | |
*** sdake has joined #zuul | 23:12 | |
*** openstackgerrit has quit IRC | 23:28 | |
*** sdake has quit IRC | 23:35 | |
*** rlandy has quit IRC | 23:45 |
Generated by irclog2html.py 2.15.3 by Marius Gedminas - find it at mg.pov.lt!