- Infra - oVirt List Archives

[JIRA] (OVIRT-1639) Get a solution to the CI Gerrit vote "race condition"
by Barak Korren (oVirt JIRA) 07 Sep '17

07 Sep '17

This is a multi-part message in MIME format... ------------=_1504768055-26486-254 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Barak Korren created OVIRT-1639: ----------------------------------- Summary: Get a solution to the CI Gerrit vote "race condition" Key: OVIRT-1639 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1639 Project: oVirt - virtualization made easy Issue Type: Improvement Components: oVirt CI Reporter: Barak Korren Assignee: infra We have a certain scenario that repeats itself in our system: # Developer sends a patch # CI jobs start running # Developer send a new patch-set with a trivial change (e.g. commit message fix) # CI jobs complete and send results to Gerrit # Gerrit ignores the Jenkins vote because it was made on the older patch-set. # No vote is made by Jenkins on the new patch-set because it is configured to nor run jobs on trivial patches. We've seen developers encounter this many times. I suspect this because even more frequent recently because PolyGerrit provides a UI for quickly editing commit messages. We need to open tickets to the Gerrit developers and the Gerrit Trigger Plugin authors and see of they will be willing to help with this. -- This message was sent by Atlassian {0} (v1001.0.0-SNAPSHOT#100059) ------------=_1504768055-26486-254 Content-Type: text/html; charset="UTF-8" Content-Disposition: inline Content-Transfer-Encoding: 7bit <html><body> <h3>Barak Korren created OVIRT-1639:</h3> <pre> Summary: Get a solution to the CI Gerrit vote "race condition" Key: OVIRT-1639 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1639 Project: oVirt - virtualization made easy Issue Type: Improvement Components: oVirt CI Reporter: Barak Korren Assignee: infra</pre> <p>We have a certain scenario that repeats itself in our system: # Developer sends a patch # CI jobs start running # Developer send a new patch-set with a trivial change (e.g. commit message fix) # CI jobs complete and send results to Gerrit # Gerrit ignores the Jenkins vote because it was made on the older patch-set. # No vote is made by Jenkins on the new patch-set because it is configured to nor run jobs on trivial patches.</p> <p>We've seen developers encounter this many times. I suspect this because even more frequent recently because PolyGerrit provides a UI for quickly editing commit messages.</p> <p>We need to open tickets to the Gerrit developers and the Gerrit Trigger Plugin authors and see of they will be willing to help with this.</p> <p>— This message was sent by Atlassian {0} (v1001.0.0-SNAPSHOT#100059)</p> <img src="https://u4043402.ct.sendgrid.net/wf/open?upn=i5TMWGV99amJbNxJpSp2-2BCmpYLyz…" alt="" width="1" height="1" border="0" style="height:1px !important;width:1px !important;border-width:0 !important;margin-top:0 !important;margin-bottom:0 !important;margin-right:0 !important;margin-left:0 !important;padding-top:0 !important;padding-bottom:0 !important;padding-right:0 !important;padding-left:0 !important;"/> </body></html> ------------=_1504768055-26486-254--

1 0

[JIRA] (OVIRT-1639) Get a solution to the CI Gerrit vote "race condition"
by Barak Korren (oVirt JIRA) 07 Sep '17

07 Sep '17

This is a multi-part message in MIME format... ------------=_1504768054-18385-248 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit [ https://ovirt-jira.atlassian.net/browse/OVIRT-1639?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1639: -------------------------------- Epic Link: OVIRT-400 > Get a solution to the CI Gerrit vote "race condition" > ----------------------------------------------------- > > Key: OVIRT-1639 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1639 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: oVirt CI > Reporter: Barak Korren > Assignee: infra > Labels: gerrit, jenkins > > We have a certain scenario that repeats itself in our system: > # Developer sends a patch > # CI jobs start running > # Developer send a new patch-set with a trivial change (e.g. commit message fix) > # CI jobs complete and send results to Gerrit > # Gerrit ignores the Jenkins vote because it was made on the older patch-set. > # No vote is made by Jenkins on the new patch-set because it is configured to nor run jobs on trivial patches. > We've seen developers encounter this many times. I suspect this because even more frequent recently because PolyGerrit provides a UI for quickly editing commit messages. > We need to open tickets to the Gerrit developers and the Gerrit Trigger Plugin authors and see of they will be willing to help with this. -- This message was sent by Atlassian {0} (v1001.0.0-SNAPSHOT#100059) ------------=_1504768054-18385-248 Content-Type: text/html; charset="UTF-8" Content-Disposition: inline Content-Transfer-Encoding: 7bit <html><body> <pre>[ https://ovirt-jira.atlassian.net/browse/OVIRT-1639?page=com.atlassian.jira.… ]</pre> <h3>Barak Korren updated OVIRT-1639:</h3> <pre>Epic Link: OVIRT-400</pre> <blockquote><h3>Get a solution to the CI Gerrit vote “race condition”</h3> <pre> Key: OVIRT-1639 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1639 Project: oVirt - virtualization made easy Issue Type: Improvement Components: oVirt CI Reporter: Barak Korren Assignee: infra Labels: gerrit, jenkins</pre> <p>We have a certain scenario that repeats itself in our system: # Developer sends a patch # CI jobs start running # Developer send a new patch-set with a trivial change (e.g. commit message fix) # CI jobs complete and send results to Gerrit # Gerrit ignores the Jenkins vote because it was made on the older patch-set. # No vote is made by Jenkins on the new patch-set because it is configured to nor run jobs on trivial patches. We've seen developers encounter this many times. I suspect this because even more frequent recently because PolyGerrit provides a UI for quickly editing commit messages. We need to open tickets to the Gerrit developers and the Gerrit Trigger Plugin authors and see of they will be willing to help with this.</p></blockquote> <p>— This message was sent by Atlassian {0} (v1001.0.0-SNAPSHOT#100059)</p> <img src="https://u4043402.ct.sendgrid.net/wf/open?upn=i5TMWGV99amJbNxJpSp2-2BCmpYLyz…" alt="" width="1" height="1" border="0" style="height:1px !important;width:1px !important;border-width:0 !important;margin-top:0 !important;margin-bottom:0 !important;margin-right:0 !important;margin-left:0 !important;padding-top:0 !important;padding-bottom:0 !important;padding-right:0 !important;padding-left:0 !important;"/> </body></html> ------------=_1504768054-18385-248--

1 0

[JIRA] (OVIRT-1638) Make CQ keep artifacts longer
by Barak Korren (oVirt JIRA) 07 Sep '17

07 Sep '17

This is a multi-part message in MIME format... ------------=_1504767557-15801-227 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit [ https://ovirt-jira.atlassian.net/browse/OVIRT-1638?page=com.atlassian.jira.… ] Barak Korren reassigned OVIRT-1638: ----------------------------------- Assignee: Barak Korren (was: infra) > Make CQ keep artifacts longer > ----------------------------- > > Key: OVIRT-1638 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1638 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: oVirt CI > Reporter: Barak Korren > Assignee: Barak Korren > Labels: change-queue > > The change queue currently keeps a history of up to 100 builds. This seems not to be enough. Instead, we need to keep 10 days of builds like we do for stdci jobs. -- This message was sent by Atlassian {0} (v1001.0.0-SNAPSHOT#100059) ------------=_1504767557-15801-227 Content-Type: text/html; charset="UTF-8" Content-Disposition: inline Content-Transfer-Encoding: 7bit <html><body> <pre>[ https://ovirt-jira.atlassian.net/browse/OVIRT-1638?page=com.atlassian.jira.… ]</pre> <h3>Barak Korren reassigned OVIRT-1638:</h3> <pre>Assignee: Barak Korren (was: infra)</pre> <blockquote><h3>Make CQ keep artifacts longer</h3> <pre> Key: OVIRT-1638 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1638 Project: oVirt - virtualization made easy Issue Type: Improvement Components: oVirt CI Reporter: Barak Korren Assignee: Barak Korren Labels: change-queue</pre> <p>The change queue currently keeps a history of up to 100 builds. This seems not to be enough. Instead, we need to keep 10 days of builds like we do for stdci jobs.</p></blockquote> <p>— This message was sent by Atlassian {0} (v1001.0.0-SNAPSHOT#100059)</p> <img src="https://u4043402.ct.sendgrid.net/wf/open?upn=i5TMWGV99amJbNxJpSp2-2BCmpYLyz…" alt="" width="1" height="1" border="0" style="height:1px !important;width:1px !important;border-width:0 !important;margin-top:0 !important;margin-bottom:0 !important;margin-right:0 !important;margin-left:0 !important;padding-top:0 !important;padding-bottom:0 !important;padding-right:0 !important;padding-left:0 !important;"/> </body></html> ------------=_1504767557-15801-227--

1 0

[JIRA] (OVIRT-1638) Make CQ keep artifacts longer
by Barak Korren (oVirt JIRA) 07 Sep '17

07 Sep '17

This is a multi-part message in MIME format... ------------=_1504767547-18274-149 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Barak Korren created OVIRT-1638: ----------------------------------- Summary: Make CQ keep artifacts longer Key: OVIRT-1638 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1638 Project: oVirt - virtualization made easy Issue Type: Improvement Components: oVirt CI Reporter: Barak Korren Assignee: infra The change queue currently keeps a history of up to 100 builds. This seems not to be enough. Instead, we need to keep 10 days of builds like we do for stdci jobs. -- This message was sent by Atlassian {0} (v1001.0.0-SNAPSHOT#100059) ------------=_1504767547-18274-149 Content-Type: text/html; charset="UTF-8" Content-Disposition: inline Content-Transfer-Encoding: 7bit <html><body> <h3>Barak Korren created OVIRT-1638:</h3> <pre> Summary: Make CQ keep artifacts longer Key: OVIRT-1638 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1638 Project: oVirt - virtualization made easy Issue Type: Improvement Components: oVirt CI Reporter: Barak Korren Assignee: infra</pre> <p>The change queue currently keeps a history of up to 100 builds. This seems not to be enough. Instead, we need to keep 10 days of builds like we do for stdci jobs.</p> <p>— This message was sent by Atlassian {0} (v1001.0.0-SNAPSHOT#100059)</p> <img src="https://u4043402.ct.sendgrid.net/wf/open?upn=i5TMWGV99amJbNxJpSp2-2BCmpYLyz…" alt="" width="1" height="1" border="0" style="height:1px !important;width:1px !important;border-width:0 !important;margin-top:0 !important;margin-bottom:0 !important;margin-right:0 !important;margin-left:0 !important;padding-top:0 !important;padding-bottom:0 !important;padding-right:0 !important;padding-left:0 !important;"/> </body></html> ------------=_1504767547-18274-149--

1 0

[JIRA] (OVIRT-1638) Make CQ keep artifacts longer
by Barak Korren (oVirt JIRA) 07 Sep '17

07 Sep '17

This is a multi-part message in MIME format... ------------=_1504767546-13608-185 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit [ https://ovirt-jira.atlassian.net/browse/OVIRT-1638?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1638: -------------------------------- Epic Link: OVIRT-400 > Make CQ keep artifacts longer > ----------------------------- > > Key: OVIRT-1638 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1638 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: oVirt CI > Reporter: Barak Korren > Assignee: infra > Labels: change-queue > > The change queue currently keeps a history of up to 100 builds. This seems not to be enough. Instead, we need to keep 10 days of builds like we do for stdci jobs. -- This message was sent by Atlassian {0} (v1001.0.0-SNAPSHOT#100059) ------------=_1504767546-13608-185 Content-Type: text/html; charset="UTF-8" Content-Disposition: inline Content-Transfer-Encoding: 7bit <html><body> <pre>[ https://ovirt-jira.atlassian.net/browse/OVIRT-1638?page=com.atlassian.jira.… ]</pre> <h3>Barak Korren updated OVIRT-1638:</h3> <pre>Epic Link: OVIRT-400</pre> <blockquote><h3>Make CQ keep artifacts longer</h3> <pre> Key: OVIRT-1638 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1638 Project: oVirt - virtualization made easy Issue Type: Improvement Components: oVirt CI Reporter: Barak Korren Assignee: infra Labels: change-queue</pre> <p>The change queue currently keeps a history of up to 100 builds. This seems not to be enough. Instead, we need to keep 10 days of builds like we do for stdci jobs.</p></blockquote> <p>— This message was sent by Atlassian {0} (v1001.0.0-SNAPSHOT#100059)</p> <img src="https://u4043402.ct.sendgrid.net/wf/open?upn=i5TMWGV99amJbNxJpSp2-2BCmpYLyz…" alt="" width="1" height="1" border="0" style="height:1px !important;width:1px !important;border-width:0 !important;margin-top:0 !important;margin-bottom:0 !important;margin-right:0 !important;margin-left:0 !important;padding-top:0 !important;padding-bottom:0 !important;padding-right:0 !important;padding-left:0 !important;"/> </body></html> ------------=_1504767546-13608-185--

1 0

[JIRA] (OVIRT-1637) Make CQ pipelines look better in Blue Ocean
by Barak Korren (oVirt JIRA) 07 Sep '17

07 Sep '17

This is a multi-part message in MIME format... ------------=_1504767431-30976-197 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit [ https://ovirt-jira.atlassian.net/browse/OVIRT-1637?page=com.atlassian.jira.… ] Barak Korren reassigned OVIRT-1637: ----------------------------------- Assignee: Barak Korren (was: infra) > Make CQ pipelines look better in Blue Ocean > ------------------------------------------- > > Key: OVIRT-1637 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1637 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Reporter: Barak Korren > Assignee: Barak Korren > Labels: blue-ocean, change-queue, jenkins > > Change queue pipelines rely heavily on job build title to show important information. > Due to [JENKINS-46657|https://issues.jenkins-ci.org/browse/JENKINS-46657] this is not currently displayed in blue ocean. > We need to move the information we need to the build description which is shown. -- This message was sent by Atlassian {0} (v1001.0.0-SNAPSHOT#100059) ------------=_1504767431-30976-197 Content-Type: text/html; charset="UTF-8" Content-Disposition: inline Content-Transfer-Encoding: 7bit <html><body> <pre>[ https://ovirt-jira.atlassian.net/browse/OVIRT-1637?page=com.atlassian.jira.… ]</pre> <h3>Barak Korren reassigned OVIRT-1637:</h3> <pre>Assignee: Barak Korren (was: infra)</pre> <blockquote><h3>Make CQ pipelines look better in Blue Ocean</h3> <pre> Key: OVIRT-1637 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1637 Project: oVirt - virtualization made easy Issue Type: Improvement Reporter: Barak Korren Assignee: Barak Korren Labels: blue-ocean, change-queue, jenkins</pre> <p>Change queue pipelines rely heavily on job build title to show important information. Due to [JENKINS-46657|<a href="https://issues.jenkins-ci.org/browse/JENKINS-46657">https://issues.jenkins-ci.org/browse/JENKINS-46657</a>] this is not currently displayed in blue ocean. We need to move the information we need to the build description which is shown.</p></blockquote> <p>— This message was sent by Atlassian {0} (v1001.0.0-SNAPSHOT#100059)</p> <img src="https://u4043402.ct.sendgrid.net/wf/open?upn=i5TMWGV99amJbNxJpSp2-2BCmpYLyz…" alt="" width="1" height="1" border="0" style="height:1px !important;width:1px !important;border-width:0 !important;margin-top:0 !important;margin-bottom:0 !important;margin-right:0 !important;margin-left:0 !important;padding-top:0 !important;padding-bottom:0 !important;padding-right:0 !important;padding-left:0 !important;"/> </body></html> ------------=_1504767431-30976-197--

1 0

[JIRA] (OVIRT-1637) Make CQ pipelines look better in Blue Ocean
by Barak Korren (oVirt JIRA) 07 Sep '17

07 Sep '17

Barak Korren created OVIRT-1637: ----------------------------------- Summary: Make CQ pipelines look better in Blue Ocean Key: OVIRT-1637 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1637 Project: oVirt - virtualization made easy Issue Type: Improvement Reporter: Barak Korren Assignee: infra Change queue pipelines rely heavily on job build title to show important information. Due to [JENKINS-46657|https://issues.jenkins-ci.org/browse/JENKINS-46657] this is not currently displayed in blue ocean. We need to move the information we need to the build description which is shown. -- This message was sent by Atlassian {0} (v1001.0.0-SNAPSHOT#100059)

1 0

[JIRA] (OVIRT-1637) Make CQ pipelines look better in Blue Ocean
by Barak Korren (oVirt JIRA) 07 Sep '17

07 Sep '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1637?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1637: -------------------------------- Epic Link: OVIRT-400 > Make CQ pipelines look better in Blue Ocean > ------------------------------------------- > > Key: OVIRT-1637 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1637 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Reporter: Barak Korren > Assignee: infra > Labels: blue-ocean, change-queue, jenkins > > Change queue pipelines rely heavily on job build title to show important information. > Due to [JENKINS-46657|https://issues.jenkins-ci.org/browse/JENKINS-46657] this is not currently displayed in blue ocean. > We need to move the information we need to the build description which is shown. -- This message was sent by Atlassian {0} (v1001.0.0-SNAPSHOT#100059)

1 0

[CQ]: 80371,10 (vdsm) failed "ovirt-master" system tests
by oVirt Jenkins 07 Sep '17

07 Sep '17

Change 80371,10 (vdsm) is probably the reason behind recent system test failures in the "ovirt-master" change queue and needs to be fixed. This change had been removed from the testing queue. Artifacts build from this change will not be released until it is fixed. For further details about the change see: https://gerrit.ovirt.org/#/c/80371/10 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/2389/

1 0

Build failed in Jenkins: system-sync_mirrors-centos-updates-el7-x86_64 #758
by jenkins＠jenkins.phx.ovirt.org 07 Sep '17

07 Sep '17

See <http://jenkins.ovirt.org/job/system-sync_mirrors-centos-updates-el7-x86_64/…> ------------------------------------------ Started by timer [EnvInject] - Loading node environment variables. Building remotely on mirrors.phx.ovirt.org (mirrors) in workspace <http://jenkins.ovirt.org/job/system-sync_mirrors-centos-updates-el7-x86_64/…> > git rev-parse --is-inside-work-tree # timeout=10 Fetching changes from the remote Git repository > git config remote.origin.url http://gerrit.ovirt.org/jenkins.git # timeout=10 Cleaning workspace > git rev-parse --verify HEAD # timeout=10 Resetting working tree > git reset --hard # timeout=10 > git clean -fdx # timeout=10 Pruning obsolete local branches Fetching upstream changes from http://gerrit.ovirt.org/jenkins.git > git --version # timeout=10 > git fetch --tags --progress http://gerrit.ovirt.org/jenkins.git +refs/changes/13/75913/5:patch --prune > git rev-parse origin/patch^{commit} # timeout=10 > git rev-parse patch^{commit} # timeout=10 Checking out Revision 4b0fe3e0c9fba26cdbaafe2b29fddd3411225d6f (patch) Commit message: "Exclude big packages from mirrors" > git config core.sparsecheckout # timeout=10 > git checkout -f 4b0fe3e0c9fba26cdbaafe2b29fddd3411225d6f > git rev-list 4b0fe3e0c9fba26cdbaafe2b29fddd3411225d6f # timeout=10 [system-sync_mirrors-centos-updates-el7-x86_64] $ /bin/bash -xe /tmp/jenkins4618256796840914410.sh + jenkins/scripts/mirror_mgr.sh resync_yum_mirror centos-updates-el7 x86_64 jenkins/data/mirrors-reposync.conf Checking if mirror needs a resync Traceback (most recent call last): File "/usr/bin/reposync", line 343, in <module> main() File "/usr/bin/reposync", line 175, in main my.doRepoSetup() File "/usr/lib/python2.7/site-packages/yum/__init__.py", line 681, in doRepoSetup return self._getRepos(thisrepo, True) File "/usr/lib/python2.7/site-packages/yum/__init__.py", line 721, in _getRepos self._repos.doSetup(thisrepo) File "/usr/lib/python2.7/site-packages/yum/repos.py", line 157, in doSetup self.retrieveAllMD() File "/usr/lib/python2.7/site-packages/yum/repos.py", line 88, in retrieveAllMD dl = repo._async and repo._commonLoadRepoXML(repo) File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 1465, in _commonLoadRepoXML if self._latestRepoXML(local): File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 1434, in _latestRepoXML oxml = self._saveOldRepoXML(local) File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 1292, in _saveOldRepoXML shutil.copy2(local, old_local) File "/usr/lib64/python2.7/shutil.py", line 131, in copy2 copystat(src, dst) File "/usr/lib64/python2.7/shutil.py", line 98, in copystat os.utime(dst, (st.st_atime, st.st_mtime)) OSError: [Errno 2] No such file or directory: '/home/jenkins/mirrors_cache/epel-el7/repomd.xml.old.tmp' Build step 'Execute shell' marked build as failure

1 1