Thursday, 2018-06-21

tristanCfungi: mordred: the linter job goern is using is proposed here: https://review.openstack.org/#/c/530682/ . The sf-jobs projects we setup with software-factory is a staging projects which just contains all those reviews: https://review.openstack.org/#/q/project:openstack-infra/zuul-jobs+owner:self+status:open01:25
tristanCand openstack-infra/zuul-jobs shadow sf-jobs so that there is no conflict if these reviews ever got merged01:26
*** spsurya has joined #zuul02:51
openstackgerritJames E. Blair proposed openstack-infra/zuul master: WIP: Report to gerrit over HTTP  https://review.openstack.org/57702703:10
openstackgerritJames E. Blair proposed openstack-infra/zuul master: WIP: Report to gerrit over HTTP  https://review.openstack.org/57702703:11
*** yolanda has quit IRC03:12
openstackgerritJames E. Blair proposed openstack-infra/zuul master: WIP: Report to gerrit over HTTP  https://review.openstack.org/57702703:59
openstackgerritJames E. Blair proposed openstack-infra/zuul master: WIP: Support line comments in Gerrit  https://review.openstack.org/57703503:59
tobiashcorvus: what I'm asking myself regarding line comments is that the line numbers in the jobs may not match the line numbers in gerrit/github because of zuul's wpeculative merging04:13
tobiashI don't have an idea how to solve that though04:14
*** SpamapS has quit IRC04:29
*** bhavik1 has joined #zuul04:59
*** swest has joined #zuul05:02
*** nchakrab has joined #zuul05:08
*** nchakrab has quit IRC05:21
*** bhavik1 has quit IRC05:23
*** yolanda has joined #zuul05:34
corvustobiash: good point.  maybe it'll be good enough most of the time?  we could try to reconcile them -- find out what line number in the patch corresponds to the line number on disk.  or, folks could choose to use it without the speculative merge (ie, check out the actual change -- it's still in the git history somewhere).  or folks could choose to disable file comments if there's a merge involved.05:44
corvustobiash: also... i was not expecting you to be awake.  :)05:44
tobiashcorvus: that's my normal time to be awake ;)05:46
tobiashcorvus: thinking about the logs, my problem is that I need the debug logging but the start/stop messages don't scale well with the number of tenants/pipelines05:47
tobiashcorvus: is there a way that I can filter them without sacrificing debug logging?05:47
corvustobiash: i basically picked the gerrit data structure for file comments -- it seemed like a good one; if you have a second to think about whether it would pose any problems for github, i'd appreciate it.05:48
tobiashcorvus: regarding github there is that new checks api05:48
tobiashI think that's also line based05:48
tobiashso the best thing I can come up with is to document that there might be mismatches and how to check out the original commit within the job (which would be useful for linting jobs anyway)05:49
corvustobiash: what's your goal with the logging?  i'd like to get everything to a point where an operator can know what's happening with just the info log.  debug should only be useful for.. well, actualy debugging of zuul, where we need lots of spam...05:49
tobiashcorvus: in openshift I the console logs are aggregated and displayed and that's my primary source of coping with 'oh hey something was wrong with my change' can you take a look at it?05:50
tobiashand the info log is pretty limited05:50
corvustobiash: can you help identify what's missing from the info log for your use cases?  maybe we can promote some debug lines to info?05:51
tobiashcorvus: I could try to set it to info and promote anything which prevents common analysis over time05:52
tobiashgah, github3.py levels are also weird05:53
tobiash2018-06-21 05:51:26,667 INFO github3: JSON was returned05:53
corvusyeah, that doesn't look very info05:53
tobiashthat's useless for info05:53
corvusoh but that's github305:53
corvuswe shouldn't be logging that anyway05:53
corvuswe should be supressing github3 to warning or above05:54
tobiashI log github3 info level (not debug) to be able to see the requests to our github05:54
*** nchakrab has joined #zuul05:54
tobiashbut that's my personal log config for that05:54
tobiashthat makes it easy to spot too chatty communication with github05:55
corvusah ok05:55
corvuswell, you could do github3@info to your debug log, and github3@warn to the info log05:55
tobiashactually github3.py info is pretty ok beside that json message05:56
tobiashmaybe I'll create a pull request for that05:56
corvusmaybe a pr.. ya :)05:56
*** Rohaan has joined #zuul06:43
*** gtema has joined #zuul06:46
*** abelur has quit IRC07:03
*** abelur has joined #zuul07:09
*** Rohaan has quit IRC07:13
*** pcaruana has joined #zuul07:22
*** sshnaidm|off has quit IRC07:40
*** jpena|off is now known as jpena07:42
*** electrofelix has joined #zuul07:59
*** sshnaidm has joined #zuul08:18
*** hashar has joined #zuul08:20
*** nchakrab has quit IRC08:42
*** nchakrab has joined #zuul08:55
*** gtema has quit IRC09:13
*** sshnaidm is now known as sshnaidm|lnch09:26
*** spsurya has quit IRC09:58
openstackgerritIan Wienand proposed openstack-infra/zuul-jobs master: Use https for security.debian.org  https://review.openstack.org/57711910:08
*** snapiri has joined #zuul10:29
*** sshnaidm|lnch is now known as sshnaidm11:04
*** nchakrab has quit IRC12:12
*** rlandy has joined #zuul12:14
*** swest has quit IRC13:07
*** myoung|off is now known as myoung13:09
openstackgerritTristan Cacqueray proposed openstack-infra/zuul master: gerrit: remove suspicious change number str cast  https://review.openstack.org/57715413:11
mhuHello, I'm trying to set up an environment to run unit tests, tox -ep35 fails for me with "Exception: More than one thread is running" on master. Anybody knows how to fix that?13:17
tristanCcorvus: we are having an odd behavior since we upgraded to gerrit-2.14.7, we suspect 577154 to be the root cause, but we could use your expert eyes on that matter13:18
tristanCcorvus: basically child change doesn't get dequeue when parent changes are updated, here is the relevant debug logs: http://paste.openstack.org/show/724023/13:18
tristanCtobiash: perhaps you had a similar issue after a gerrit upgrade? or did you stay in 2.13?13:25
*** nchakrab has joined #zuul13:27
*** gtema has joined #zuul13:29
tristanCoops, paste got truncated, complete version is: https://paste.fedoraproject.org/paste/mDbj1L-1RYeOleiGSAOVJw13:34
tobiashtristanC: I don't manage a gerrit anymore and the one we currenty use in addition to github is an externally managed gerrit 2.913:37
*** spsurya has joined #zuul13:44
tristanCfbo: btw, the change that introduced this cast ( https://review.openstack.org/433748 ) mention an issue with some code that isn't there anymore13:47
fbotristanC: ah yes so it seems to be safe to remove then13:52
tobiashclarkb: I'm a step further into understanding the github multi-enqueue issue13:57
tobiashand I'm afraid it's a complicated heavily timing based thing13:57
tobiashso the use case is you have pull request 1,aaaaa with a review13:58
tobiashnow you push an update to that and get pull request 1,bbbbb13:58
tobiashgithub sends two events in this case: dismissed stale review and synchronized13:59
tobiashif zuul gets the dismissed stale review first it updates its data of 1,aaaaa14:00
tobiashthat includes the github supplied updated_at timestamp of PR #1 (note that github has no patchset concept as gerrit)14:00
tobiashthen zuul processes 1,bbbbb, enqueues it into the pipeline14:01
tobiashduring that it checks if 1,bbbbb is an update of 1,aaaaa14:01
tobiashnote that because github only knows PR 1 both PullRequest objects in zuul get the same timestamp14:02
tobiashand then the isUpdateOf check fails: http://git.openstack.org/cgit/openstack-infra/zuul/tree/zuul/driver/github/githubmodel.py#n4514:03
tobiashand if that fails zuul doesn't dequeue the old pr14:03
tobiashat first glance I don't know a way how we could fix that14:08
*** nchakrab has quit IRC14:08
*** nchakrab has joined #zuul14:09
*** acozine1 has joined #zuul14:14
clarkbmaybe dont update the timestamp using the dismissal event?14:16
clarkbthen the original push timestamp remains and b canupdate it and be newer?14:16
tobiashclarkb: the problem is that zuul *updates* this timestamp on the dismissal event14:16
tobiashit uses the updated_at timestamp of the PR which is the same for any version when newly requested14:17
clarkbright can we special case the dismissal event to not update the timestamp?14:17
tobiashit's not only the dismissal event but any event that causes an update of the pr14:18
tobiashso we would need to switch that to *never* update the timestamp14:18
tobiash(if we already have one)14:18
clarkbhrm14:18
tobiashor we don't rely on the timestamp and just compare the git sha's and hope that if they differ that's an update14:19
tobiashthat's the second thing I could think of14:19
tobiashthe problem is that the timestamp in github is not attached to the commit but to the pull request14:20
tobiashin gerrit there's no problem with that as we have a 1:1 relationship between zuul changes and gerrit patchsets14:20
tobiashin github we have a n:1 relation between zuul changes and the github pr14:21
openstackgerritTobias Henkel proposed openstack-infra/zuul master: WIP First try to solve github multi-enqueue error  https://review.openstack.org/57717314:23
openstackgerritTobias Henkel proposed openstack-infra/zuul master: WIP First try to solve github multi-enqueue error  https://review.openstack.org/57717314:24
openstackgerritTobias Henkel proposed openstack-infra/zuul master: WIP: Second try to fix github multi-enqueue issue  https://review.openstack.org/57717514:25
tobiashclarkb: that would be basically the two ideas to fix that ^14:26
*** pcaruana has quit IRC14:56
*** nchakrab has quit IRC15:18
*** ianychoi has joined #zuul15:48
*** spsurya has quit IRC16:28
*** nchakrab has joined #zuul16:59
*** nchakrab has quit IRC17:04
*** elyezer has quit IRC17:06
*** zaro__ is now known as zaro17:08
*** jpena is now known as jpena|off17:12
openstackgerritMatthieu Huin proposed openstack-infra/zuul master: [WIP] web: add tenant-scoped autohold, enqueue  https://review.openstack.org/57690717:53
openstackgerritDavid Shrewsbury proposed openstack-infra/nodepool master: Remove a done TODO in static driver  https://review.openstack.org/57724418:01
*** gtema has quit IRC18:08
openstackgerritMatthieu Huin proposed openstack-infra/zuul master: [WIP] web: add tenant-scoped autohold, enqueue  https://review.openstack.org/57690718:18
openstackgerritMerged openstack-infra/nodepool master: Pass zk connection to ProviderManager.start()  https://review.openstack.org/57489519:00
openstackgerritMerged openstack-infra/nodepool master: Make a proper driver notification API  https://review.openstack.org/57489619:01
*** weshay|ruck is now known as weshay_PTO19:12
openstackgerritMerged openstack-infra/nodepool master: Pre-register static nodes  https://review.openstack.org/57489719:16
openstackgerritMerged openstack-infra/nodepool master: Clarify static node name uniqueness in docs  https://review.openstack.org/57515919:17
Shrewsoh yay. those are satisfying merges19:20
*** SpamapS has joined #zuul19:23
tobiashlooks like we have a race in tox-remote: http://logs.openstack.org/22/572522/3/gate/zuul-tox-remote/168c0a1/job-output.txt.gz#_2018-06-20_14_12_23_72659619:26
mordredShrews: \o/19:27
*** acozine1 has quit IRC19:29
openstackgerritTobias Henkel proposed openstack-infra/zuul master: Fix race in tox-remote test_command  https://review.openstack.org/57727919:30
openstackgerritTobias Henkel proposed openstack-infra/zuul master: Fix race in tox-remote test_command  https://review.openstack.org/57727919:32
*** trishnag has quit IRC19:32
tobiashthat should fix the race ^19:33
mordredtobiash: lgtm19:35
tobiash\o/19:35
tobiashmordred: that would be an easy review too: https://review.openstack.org/57364119:35
tobiashreduces logging noise19:36
tobiash(test logging noise)19:36
tobiashShrews: I guess 572342 is obsolete now?19:38
openstackgerritMerged openstack-infra/nodepool master: Remove a done TODO in static driver  https://review.openstack.org/57724419:39
Shrewstobiash: i think so19:39
tobiashk, thx19:39
mordredtobiash: done19:42
tobiash:)19:42
openstackgerritMerged openstack-infra/zuul master: Don't use GRANT to create new MySQL users  https://review.openstack.org/57364120:06
*** yolanda_ has joined #zuul20:07
openstackgerritMerged openstack-infra/zuul master: Make streaming test run longer than connection timeout  https://review.openstack.org/57252220:07
*** trishnag has joined #zuul20:09
*** trishnag has quit IRC20:09
*** trishnag has joined #zuul20:09
*** yolanda has quit IRC20:11
openstackgerritMerged openstack-infra/zuul master: Fix race in tox-remote test_command  https://review.openstack.org/57727920:20
*** myoung is now known as myoung|off21:30
*** hashar has quit IRC22:12
openstackgerritTristan Cacqueray proposed openstack-infra/zuul master: gerrit: cast change and patchset numbers to str  https://review.openstack.org/57715423:00
*** rlandy has quit IRC23:09

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