July 2017 - Infra - oVirt List Archives

[JIRA] (OVIRT-1502) gerrit does not print check_merged output
by Barak Korren (oVirt JIRA) 03 Jul '17

03 Jul '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1502?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1502: -------------------------------- Issue Type: Bug (was: By-EMAIL) > gerrit does not print check_merged output > ----------------------------------------- > > Key: OVIRT-1502 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1502 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: ybronhei > Assignee: infra > > Hello, > Recently vdsm gerrit job check-merged doesn't send report after its done - > check all recent jobs - they were done but the gerrit url doesn't show the > output nor send email about failures. > Thanks in advance > Yaniv Bronhaim. > -- > Yaniv Bronhaim. -- This message was sent by Atlassian JIRA (v1000.1092.1#100053)

1 0

[JIRA] (OVIRT-1502) gerrit does not print check_merged output
by Barak Korren (oVirt JIRA) 03 Jul '17

03 Jul '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1502?page=com.atlassian.jira.… ] Barak Korren commented on OVIRT-1502: ------------------------------------- [~eedri] no this is completely unrelated to that ticket. In this case we see that the build success/failure comment by jenkins is not added at all, as if the Gerrit plugin "forgot" to return results. See these patches for example: * https://gerrit.ovirt.org/#/c/78890/ * https://gerrit.ovirt.org/#/c/78189/ Here are links to the full set of post-merge jobs for [78189|https://gerrit.ovirt.org/78189] # http://jenkins.ovirt.org/job/vdsm_master_check-merged-el7-x86_64/2091/ # http://jenkins.ovirt.org/job/vdsm_master_build-artifacts-fc25-x86_64/1098/ # http://jenkins.ovirt.org/job/vdsm_master_build-artifacts-el7-x86_64/2686/ # http://jenkins.ovirt.org/job/vdsm_master_build-artifacts-el7-ppc64le/2100/ # http://jenkins.ovirt.org/job/deploy-to-ovirt_experimental/3053/ # http://jenkins.ovirt.org/job/standard-enqueue/2232/ I don't see any obvious issues with the jobs ATM. For engine things seem to work ok: https://gerrit.ovirt.org/#/c/78901/ > gerrit does not print check_merged output > ----------------------------------------- > > Key: OVIRT-1502 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1502 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: ybronhei > Assignee: infra > > Hello, > Recently vdsm gerrit job check-merged doesn't send report after its done - > check all recent jobs - they were done but the gerrit url doesn't show the > output nor send email about failures. > Thanks in advance > Yaniv Bronhaim. > -- > Yaniv Bronhaim. -- This message was sent by Atlassian JIRA (v1000.1092.1#100053)

1 0

[JIRA] (OVIRT-686) Find a better way to show unstable status in CI
by eedri (oVirt JIRA) 03 Jul '17

03 Jul '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-686?page=com.atlassian.jira.p… ] eedri updated OVIRT-686: ------------------------ Priority: Low (was: Medium) > Find a better way to show unstable status in CI > ----------------------------------------------- > > Key: OVIRT-686 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-686 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Reporter: eedri > Assignee: infra > Priority: Low > > Today we have the main view on jenkins.ovirt.org showing the unstable list of jobs, > While its effective in showing the current stable jobs, its not optimal in showing trends, history or dashboard view of the jenkins itself. > We need to find a jenkins plugin or a dashboard to show the current status of Jenkins in a more efficient and informative way. > There are numerous dashboards and view plugins, just need to find the right one for oVirt. -- This message was sent by Atlassian JIRA (v1000.1092.1#100053)

1 0

[JIRA] (OVIRT-638) Tune Gerrit
by eedri (oVirt JIRA) 03 Jul '17

03 Jul '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-638?page=com.atlassian.jira.p… ] eedri updated OVIRT-638: ------------------------ Priority: Low (was: Medium) > Tune Gerrit > ----------- > > Key: OVIRT-638 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-638 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Reporter: Barak Korren > Assignee: infra > Priority: Low > > We should probably tune Gerrit to take proper advantage of the bigger server we now have. > This could be useful: > http://ctf-dev-environment-vagrant.s3.amazonaws.com/Gerrit-Performance-Tuni… > Few notable details: > # Most RAM on the new server is currently taken by the FS cache instead of the Gerrit Java processes. > # It seems that the Gerrit can do Git garbage collection on its own, and do so more efficiently then doing so with the Git command line. -- This message was sent by Atlassian JIRA (v1000.1092.1#100053)

1 0

[JIRA] (OVIRT-1173) Please use git shallow clone as jobs default
by eedri (oVirt JIRA) 03 Jul '17

03 Jul '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1173?page=com.atlassian.jira.… ] eedri updated OVIRT-1173: ------------------------- Priority: Low (was: Medium) > Please use git shallow clone as jobs default > -------------------------------------------- > > Key: OVIRT-1173 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1173 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Reporter: rgolan(a)redhat.com > Assignee: infra > Priority: Low > Labels: standard-ci > > Most if not all the git clone of the jobs don't need history at all. > For ovirt-engine I see it downloading *11Mb* using --depth 1 vs. *157Mb* > for regular clone. > R -- This message was sent by Atlassian JIRA (v1000.1092.1#100053)

1 0

[JIRA] (OVIRT-978) Move ovirt-engine & vdsm projects from git:// to http:// to reduce load from git service
by eedri (oVirt JIRA) 03 Jul '17

03 Jul '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-978?page=com.atlassian.jira.p… ] eedri commented on OVIRT-978: ----------------------------- havn't seen failures due to it for quite some time, keeping it as low priority in case we hit it again. > Move ovirt-engine & vdsm projects from git:// to http:// to reduce load from git service > ---------------------------------------------------------------------------------------- > > Key: OVIRT-978 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-978 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Reporter: danken > Assignee: infra > Priority: Low > > Occasionally, e.g. > http://jenkins.ovirt.org/job/vdsm_master_check-patch-fc24-x86_64/6870/conso… > I see these failures > 07:29:50 Manually triggered by user ishaby(a)redhat.com for Gerrit: > https://gerrit.ovirt.org/68804 > 07:29:50 [EnvInject] - Loading node environment variables. > 07:29:50 Building remotely on fc24-vm15.phx.ovirt.org (fc24 phx > local_disk nested) in workspace > /home/jenkins/workspace/vdsm_master_check-patch-fc24-x86_64 > 07:29:50 > git rev-parse --is-inside-work-tree # timeout=10 > 07:29:50 Fetching changes from the remote Git repository > 07:29:50 > git config remote.origin.url > git://gerrit.ovirt.org/vdsm.git # timeout=10 > 07:29:50 Cleaning workspace > 07:29:50 > git rev-parse --verify HEAD # timeout=10 > 07:29:50 Resetting working tree > 07:29:50 > git reset --hard # timeout=10 > 07:29:51 > git clean -fdx # timeout=10 > 07:29:51 Pruning obsolete local branches > 07:29:51 Fetching upstream changes from git://gerrit.ovirt.org/vdsm.git > 07:29:51 > git --version # timeout=10 > 07:29:51 > git -c core.askpass=true fetch --tags --progress > git://gerrit.ovirt.org/vdsm.git refs/changes/04/68804/3 --prune > 07:29:51 ERROR: Error fetching remote repo 'origin' > 07:29:51 hudson.plugins.git.GitException: Failed to fetch from > git://gerrit.ovirt.org/vdsm.git -- This message was sent by Atlassian JIRA (v1000.1092.1#100053)

1 0

[JIRA] (OVIRT-978) Move ovirt-engine & vdsm projects from git:// to http:// to reduce load from git service
by eedri (oVirt JIRA) 03 Jul '17

03 Jul '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-978?page=com.atlassian.jira.p… ] eedri updated OVIRT-978: ------------------------ Priority: Low (was: Medium) > Move ovirt-engine & vdsm projects from git:// to http:// to reduce load from git service > ---------------------------------------------------------------------------------------- > > Key: OVIRT-978 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-978 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Reporter: danken > Assignee: infra > Priority: Low > > Occasionally, e.g. > http://jenkins.ovirt.org/job/vdsm_master_check-patch-fc24-x86_64/6870/conso… > I see these failures > 07:29:50 Manually triggered by user ishaby(a)redhat.com for Gerrit: > https://gerrit.ovirt.org/68804 > 07:29:50 [EnvInject] - Loading node environment variables. > 07:29:50 Building remotely on fc24-vm15.phx.ovirt.org (fc24 phx > local_disk nested) in workspace > /home/jenkins/workspace/vdsm_master_check-patch-fc24-x86_64 > 07:29:50 > git rev-parse --is-inside-work-tree # timeout=10 > 07:29:50 Fetching changes from the remote Git repository > 07:29:50 > git config remote.origin.url > git://gerrit.ovirt.org/vdsm.git # timeout=10 > 07:29:50 Cleaning workspace > 07:29:50 > git rev-parse --verify HEAD # timeout=10 > 07:29:50 Resetting working tree > 07:29:50 > git reset --hard # timeout=10 > 07:29:51 > git clean -fdx # timeout=10 > 07:29:51 Pruning obsolete local branches > 07:29:51 Fetching upstream changes from git://gerrit.ovirt.org/vdsm.git > 07:29:51 > git --version # timeout=10 > 07:29:51 > git -c core.askpass=true fetch --tags --progress > git://gerrit.ovirt.org/vdsm.git refs/changes/04/68804/3 --prune > 07:29:51 ERROR: Error fetching remote repo 'origin' > 07:29:51 hudson.plugins.git.GitException: Failed to fetch from > git://gerrit.ovirt.org/vdsm.git -- This message was sent by Atlassian JIRA (v1000.1092.1#100053)

1 0

[JIRA] (OVIRT-1500) CI on ovirt-engine patch succeeded, but didn't mark CI=+1 on gerrit
by Barak Korren (oVirt JIRA) 03 Jul '17

03 Jul '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1500?page=com.atlassian.jira.… ] Barak Korren commented on OVIRT-1500: ------------------------------------- [~eedri] Its the gerrit plugin, but it simple runs a gerrit command on ssh. You can try it yourself, send a command to update the vote for a patchset that is not the most recent one, Gerrit will add a comment that says you updated the vote but not update it in practice because it only keeps votes for the most recent patcheset. What we have here is a race condition - A new patchset was added before jenkins managed to add its vote, and because the new patchset was a trivial rebase no new jenkins job was invoked. A hook to copy the votes will not help here because they were not registered by Gerrit in the 1st place. The only solution I can think of ATM is to make Jenkins run jobs on trivial rebase too. > CI on ovirt-engine patch succeeded, but didn't mark CI=+1 on gerrit > ------------------------------------------------------------------- > > Key: OVIRT-1500 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1500 > Project: oVirt - virtualization made easy > Issue Type: Bug > Components: Gerrit/git, oVirt CI > Reporter: Allon Mureinik > Assignee: infra > > In my recent engine patch https://gerrit.ovirt.org/#/c/78911 the CI passed, but was not marked as so in gerrit. > Looking through gerrit's history, here's what I *think* is going on: > 08:41 - patchset #1 is submitted > 08:41 - CI (check-patch) starts for both EL7 and fc25 > _At this point I noticed a typo in the commit method. I fixed it and posted patchset #2_ > 08:42 - patchset #2 is submitted > _CI was never triggered for patchset #2. Is this because the only difference between it and patchset #1 is the commit message?_ > 09:15 - CI for patchset #1 completes, and marks *patchset #1* with CI=+1. This is not inherited to patchset #2 for some reason. > Expected behavior: > If CI for patchset #1 passed and the only difference is the commit message (not the parent commit and not the content), I'd expect the CI score to be inherited. -- This message was sent by Atlassian JIRA (v1000.1092.1#100053)

1 0

[JIRA] (OVIRT-1502) gerrit does not print check_merged output
by eedri (oVirt JIRA) 03 Jul '17

03 Jul '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1502?page=com.atlassian.jira.… ] eedri commented on OVIRT-1502: ------------------------------ I'm not sure it was sending emails, this might be duplicate: https://ovirt-jira.atlassian.net/browse/OVIRT-833 > gerrit does not print check_merged output > ----------------------------------------- > > Key: OVIRT-1502 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1502 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: ybronhei > Assignee: infra > > Hello, > Recently vdsm gerrit job check-merged doesn't send report after its done - > check all recent jobs - they were done but the gerrit url doesn't show the > output nor send email about failures. > Thanks in advance > Yaniv Bronhaim. > -- > Yaniv Bronhaim. -- This message was sent by Atlassian JIRA (v1000.1092.1#100053)

1 0

[JIRA] (OVIRT-1500) CI on ovirt-engine patch succeeded, but didn't mark CI=+1 on gerrit
by eedri (oVirt JIRA) 03 Jul '17

03 Jul '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1500?page=com.atlassian.jira.… ] eedri commented on OVIRT-1500: ------------------------------ [~bkorren(a)redhat.com][~ederevea] do we know who manages the flag scores on Gerrit? Is it configured on Gerrit Trigger side or on Gerrit conf itself? Is it configurable at all? I vaguely remember a hook that was maintaining the scores on trivial rebase. > CI on ovirt-engine patch succeeded, but didn't mark CI=+1 on gerrit > ------------------------------------------------------------------- > > Key: OVIRT-1500 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1500 > Project: oVirt - virtualization made easy > Issue Type: Bug > Components: Gerrit/git, oVirt CI > Reporter: Allon Mureinik > Assignee: infra > > In my recent engine patch https://gerrit.ovirt.org/#/c/78911 the CI passed, but was not marked as so in gerrit. > Looking through gerrit's history, here's what I *think* is going on: > 08:41 - patchset #1 is submitted > 08:41 - CI (check-patch) starts for both EL7 and fc25 > _At this point I noticed a typo in the commit method. I fixed it and posted patchset #2_ > 08:42 - patchset #2 is submitted > _CI was never triggered for patchset #2. Is this because the only difference between it and patchset #1 is the commit message?_ > 09:15 - CI for patchset #1 completes, and marks *patchset #1* with CI=+1. This is not inherited to patchset #2 for some reason. > Expected behavior: > If CI for patchset #1 passed and the only difference is the commit message (not the parent commit and not the content), I'd expect the CI score to be inherited. -- This message was sent by Atlassian JIRA (v1000.1092.1#100053)

1 0