January 2018 - Infra - Ovirt List Archives

[JIRA] (OVIRT-1866) Use PERFORMANCE_OPTIMIZED pipelines instead of MAX_SURVIVABILITY

by Daniel Belenky (oVirt JIRA)

This is a multi-part message in MIME format... ------------=_1517299177-24378-150 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit [ https://ovirt-jira.atlassian.net/browse/OVIRT-1866?page=com.atlassian.jir... ] Daniel Belenky updated OVIRT-1866: ---------------------------------- Labels: jenkins (was: ) > Use PERFORMANCE_OPTIMIZED pipelines instead of MAX_SURVIVABILITY > ---------------------------------------------------------------- > > Key: OVIRT-1866 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1866 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: Jenkins Master > Reporter: Daniel Belenky > Assignee: infra > Labels: jenkins > > It seems that pipelines now have support to configure their behavior of serialization of objects, and since we know that this serialization never worked for us as we'd expect it to, maybe we should consider using PERFORMANCE_OPTIMIZED mode which will avoid serializing and maybe boost the performance. > [Link to subject in jenkincci-dev google|https://groups.google.com/forum/#!msg/jenkinsci-dev/F4zcOWLI32w/51...] -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100077) ------------=_1517299177-24378-150 Content-Type: text/html; charset="UTF-8" Content-Disposition: inline Content-Transfer-Encoding: 7bit <html><body> <pre>[ https://ovirt-jira.atlassian.net/browse/OVIRT-1866?page=com.atlassian.jir... ]</pre> <h3>Daniel Belenky updated OVIRT-1866:</h3> <pre>Labels: jenkins (was: )</pre> <blockquote><h3>Use PERFORMANCE_OPTIMIZED pipelines instead of MAX_SURVIVABILITY</h3> <pre> Key: OVIRT-1866 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1866 Project: oVirt - virtualization made easy Issue Type: Improvement Components: Jenkins Master Reporter: Daniel Belenky Assignee: infra Labels: jenkins</pre> <p>It seems that pipelines now have support to configure their behavior of serialization of objects, and since we know that this serialization never worked for us as we'd expect it to, maybe we should consider using PERFORMANCE_OPTIMIZED mode which will avoid serializing and maybe boost the performance. [Link to subject in jenkincci-dev google|<a href="https://groups.google.com/forum/#!msg/jenkinsci-dev/F4zcOWLI32w/51qixjepCgAJ">https://groups.google.com/forum/#!msg/jenkinsci-dev/F4zcOWLI32w/51qixjepCgAJ</a>]</p></blockquote> <p>— This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100077)</p> <img src="https://u4043402.ct.sendgrid.net/wf/open?upn=i5TMWGV99amJbNxJpSp2-2BJ33BS..." 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> ------------=_1517299177-24378-150--

6 years, 2 months

1
0
0 / 0

[JIRA] (OVIRT-1866) Use PERFORMANCE_OPTIMIZED pipelines instead of MAX_SURVIVABILITY

by Barak Korren (oVirt JIRA)

This is a multi-part message in MIME format... ------------=_1517298659-23592-267 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit [ https://ovirt-jira.atlassian.net/browse/OVIRT-1866?page=com.atlassian.jir... ] Barak Korren updated OVIRT-1866: -------------------------------- Component/s: Jenkins Master > Use PERFORMANCE_OPTIMIZED pipelines instead of MAX_SURVIVABILITY > ---------------------------------------------------------------- > > Key: OVIRT-1866 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1866 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: Jenkins Master > Reporter: Daniel Belenky > Assignee: infra > > It seems that pipelines now have support to configure their behavior of serialization of objects, and since we know that this serialization never worked for us as we'd expect it to, maybe we should consider using PERFORMANCE_OPTIMIZED mode which will avoid serializing and maybe boost the performance. > [Link to subject in jenkincci-dev google|https://groups.google.com/forum/#!msg/jenkinsci-dev/F4zcOWLI32w/51...] -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100077) ------------=_1517298659-23592-267 Content-Type: text/html; charset="UTF-8" Content-Disposition: inline Content-Transfer-Encoding: 7bit <html><body> <pre>[ https://ovirt-jira.atlassian.net/browse/OVIRT-1866?page=com.atlassian.jir... ]</pre> <h3>Barak Korren updated OVIRT-1866:</h3> <pre>Component/s: Jenkins Master</pre> <blockquote><h3>Use PERFORMANCE_OPTIMIZED pipelines instead of MAX_SURVIVABILITY</h3> <pre> Key: OVIRT-1866 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1866 Project: oVirt - virtualization made easy Issue Type: Improvement Components: Jenkins Master Reporter: Daniel Belenky Assignee: infra</pre> <p>It seems that pipelines now have support to configure their behavior of serialization of objects, and since we know that this serialization never worked for us as we'd expect it to, maybe we should consider using PERFORMANCE_OPTIMIZED mode which will avoid serializing and maybe boost the performance. [Link to subject in jenkincci-dev google|<a href="https://groups.google.com/forum/#!msg/jenkinsci-dev/F4zcOWLI32w/51qixjepCgAJ">https://groups.google.com/forum/#!msg/jenkinsci-dev/F4zcOWLI32w/51qixjepCgAJ</a>]</p></blockquote> <p>— This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100077)</p> <img src="https://u4043402.ct.sendgrid.net/wf/open?upn=i5TMWGV99amJbNxJpSp2-2BJ33BS..." 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> ------------=_1517298659-23592-267--

6 years, 2 months

1
0
0 / 0

[JIRA] (OVIRT-1866) Use PERFORMANCE_OPTIMIZED pipelines instead of MAX_SURVIVABILITY

by Daniel Belenky (oVirt JIRA)

Daniel Belenky created OVIRT-1866: ------------------------------------- Summary: Use PERFORMANCE_OPTIMIZED pipelines instead of MAX_SURVIVABILITY Key: OVIRT-1866 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1866 Project: oVirt - virtualization made easy Issue Type: Improvement Reporter: Daniel Belenky Assignee: infra It seems that pipelines now have support to configure their behavior of serialization of objects, and since we know that this serialization never worked for us as we'd expect it to, maybe we should consider using PERFORMANCE_OPTIMIZED mode which will avoid serializing and maybe boost the performance. [Link to subject in jenkincci-dev google|https://groups.google.com/forum/#!msg/jenkinsci-dev/F4zcOWLI32w/51...] -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100077)

6 years, 2 months

1
0
0 / 0

[JIRA] (OVIRT-1866) Use PERFORMANCE_OPTIMIZED pipelines instead of MAX_SURVIVABILITY

by Daniel Belenky (oVirt JIRA)

This is a multi-part message in MIME format... ------------=_1517298465-14824-170 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit [ https://ovirt-jira.atlassian.net/browse/OVIRT-1866?page=com.atlassian.jir... ] Daniel Belenky updated OVIRT-1866: ---------------------------------- Epic Link: OVIRT-400 > Use PERFORMANCE_OPTIMIZED pipelines instead of MAX_SURVIVABILITY > ---------------------------------------------------------------- > > Key: OVIRT-1866 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1866 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Reporter: Daniel Belenky > Assignee: infra > > It seems that pipelines now have support to configure their behavior of serialization of objects, and since we know that this serialization never worked for us as we'd expect it to, maybe we should consider using PERFORMANCE_OPTIMIZED mode which will avoid serializing and maybe boost the performance. > [Link to subject in jenkincci-dev google|https://groups.google.com/forum/#!msg/jenkinsci-dev/F4zcOWLI32w/51...] -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100077) ------------=_1517298465-14824-170 Content-Type: text/html; charset="UTF-8" Content-Disposition: inline Content-Transfer-Encoding: 7bit <html><body> <pre>[ https://ovirt-jira.atlassian.net/browse/OVIRT-1866?page=com.atlassian.jir... ]</pre> <h3>Daniel Belenky updated OVIRT-1866:</h3> <pre>Epic Link: OVIRT-400</pre> <blockquote><h3>Use PERFORMANCE_OPTIMIZED pipelines instead of MAX_SURVIVABILITY</h3> <pre> Key: OVIRT-1866 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1866 Project: oVirt - virtualization made easy Issue Type: Improvement Reporter: Daniel Belenky Assignee: infra</pre> <p>It seems that pipelines now have support to configure their behavior of serialization of objects, and since we know that this serialization never worked for us as we'd expect it to, maybe we should consider using PERFORMANCE_OPTIMIZED mode which will avoid serializing and maybe boost the performance. [Link to subject in jenkincci-dev google|<a href="https://groups.google.com/forum/#!msg/jenkinsci-dev/F4zcOWLI32w/51qixjepCgAJ">https://groups.google.com/forum/#!msg/jenkinsci-dev/F4zcOWLI32w/51qixjepCgAJ</a>]</p></blockquote> <p>— This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100077)</p> <img src="https://u4043402.ct.sendgrid.net/wf/open?upn=i5TMWGV99amJbNxJpSp2-2BJ33BS..." 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> ------------=_1517298465-14824-170--

6 years, 2 months

1
0
0 / 0

[oVirt Jenkins] ovirt-appliance_ovirt-4.2-pre_build-artifacts-el7-x86_64 - Build # 58 - Failure!

by jenkins＠jenkins.phx.ovirt.org

------=_Part_411_1014979441.1517245103403 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Project: http://jenkins.ovirt.org/job/ovirt-appliance_ovirt-4.2-pre_build-artifact... Build: http://jenkins.ovirt.org/job/ovirt-appliance_ovirt-4.2-pre_build-artifact... Build Number: 58 Build Status: Failure Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #58 [Daniel Belenky] Add ipinto(a)redhat.com to whitelist [Sandro Bonazzola] pywin32-py2.7: move to 4.2 and latest fedora [Sandro Bonazzola] python-windows: move to 4.2 and latest fedora [Sandro Bonazzola] py2exe-py2.7: move to 4.2 and latest fedora [Sandro Bonazzola] nsis-simple-service-plugin:: move to 4.2 and latest fedora [Daniel Belenky] Bound vdsm check-merged to el7 hosts only [Barak Korren] Make standard-enqueue support non-ovirt queues [Barak Korren] Allow customizing CQ mail addresses [Barak Korren] Enable customizing the server we deploy tested to [Barak Korren] Make pipeline-loader support upstream sources [Barak Korren] Made clone url for 'jenkins' customizable [Yuval Turgeman] Resolve network issues in kickstart ----------------- Failed Tests: ----------------- No tests ran. ------=_Part_411_1014979441.1517245103403--

6 years, 2 months

1
1
0 / 0

Build failed in Jenkins: system-sync_mirrors-centos-base-el6-x86_64 #1136

by jenkins＠jenkins.phx.ovirt.org

See <http://jenkins.ovirt.org/job/system-sync_mirrors-centos-base-el6-x86_64/1...> Changes: [Barak Korren] Made clone url for 'jenkins' customizable ------------------------------------------ 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-base-el6-x86_64/ws/> > 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/heads/*:refs/remotes/origin/* --prune > git rev-parse origin/master^{commit} # timeout=10 Checking out Revision ffe020fb18b7f872bc817ba9eec0c0d5a82bc489 (origin/master) > git config core.sparsecheckout # timeout=10 > git checkout -f ffe020fb18b7f872bc817ba9eec0c0d5a82bc489 Commit message: "Made clone url for 'jenkins' customizable" > git rev-list b334ef0c5cfd393e9f699aad3d8c201e4df864e3 # timeout=10 [system-sync_mirrors-centos-base-el6-x86_64] $ /bin/bash -xe /tmp/jenkins7771361266593698969.sh + jenkins/scripts/mirror_mgr.sh resync_yum_mirror centos-base-el6 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 local = self.cachedir + '/repomd.xml' File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 774, in <lambda> cachedir = property(lambda self: self._dirGetAttr('cachedir')) File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 757, in _dirGetAttr self.dirSetup() File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 735, in dirSetup self._dirSetupMkdir_p(dir) File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 712, in _dirSetupMkdir_p raise Errors.RepoError, msg yum.Errors.RepoError: Error making cache directory: /home/jenkins/mirrors_cache/fedora-updates-fc24/gen error was: [Errno 17] File exists: '/home/jenkins/mirrors_cache/fedora-updates-fc24/gen' Build step 'Execute shell' marked build as failure

6 years, 2 months

1
1
0 / 0

Build failed in Jenkins: system-sync_mirrors-fedora-updates-fc24-x86_64 #1052

by jenkins＠jenkins.phx.ovirt.org

See <http://jenkins.ovirt.org/job/system-sync_mirrors-fedora-updates-fc24-x86_...> Changes: [Barak Korren] Made clone url for 'jenkins' customizable ------------------------------------------ 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-fedora-updates-fc24-x86_...> > 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/heads/*:refs/remotes/origin/* --prune > git rev-parse origin/master^{commit} # timeout=10 Checking out Revision ffe020fb18b7f872bc817ba9eec0c0d5a82bc489 (origin/master) > git config core.sparsecheckout # timeout=10 > git checkout -f ffe020fb18b7f872bc817ba9eec0c0d5a82bc489 Commit message: "Made clone url for 'jenkins' customizable" > git rev-list b334ef0c5cfd393e9f699aad3d8c201e4df864e3 # timeout=10 [system-sync_mirrors-fedora-updates-fc24-x86_64] $ /bin/bash -xe /tmp/jenkins180117895611239583.sh + jenkins/scripts/mirror_mgr.sh resync_yum_mirror fedora-updates-fc24 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 112, in retrieveAllMD repo._revertOldRepoXML() File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 1331, in _revertOldRepoXML os.rename(old_data['old_local'], old_data['local']) OSError: [Errno 2] No such file or directory Build step 'Execute shell' marked build as failure

6 years, 2 months

1
1
0 / 0

PHX planned maintenance 29.01.2018 @19:00 GMT

by Evgheni Dereveanchin

Hi everyone, Planned works are going to be performed in the PHX data center today. They are related to core networking hardware upgrades and may cause short connectivity loss to services hosted by the oVirt project, including: * Jenkins CI * Package repositories * project website * mailing lists The maintenance window starts at 19:00 GMT and has a duration of one hour. I will pause CI job execution before the maintenance window so builds will be queued and executed after network upgrades are implemented to decrease the possibility of false positives. I will follow up with any further updates. -- Regards, Evgheni Dereveanchin

6 years, 2 months

1
1
0 / 0

[CQ]: 86868, 5 (otopi) failed "ovirt-master" system tests, but isn't the failure root cause

by oVirt Jenkins

A system test invoked by the "ovirt-master" change queue including change 86868,5 (otopi) failed. However, this change seems not to be the root cause for this failure. Change 86679,4 (otopi) that this change depends on or is based on, was detected as the cause of the testing failures. This change had been removed from the testing queue. Artifacts built from this change will not be released until either change 86679,4 (otopi) is fixed and this change is updated to refer to or rebased on the fixed version, or this change is modified to no longer depend on it. For further details about the change see: https://gerrit.ovirt.org/#/c/86868/5 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/86679/4 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/5155/

6 years, 2 months

1
0
0 / 0

[CQ]: 86869, 1 (otopi) failed "ovirt-master" system tests, but isn't the failure root cause

by oVirt Jenkins

A system test invoked by the "ovirt-master" change queue including change 86869,1 (otopi) failed. However, this change seems not to be the root cause for this failure. Change 86679,4 (otopi) that this change depends on or is based on, was detected as the cause of the testing failures. This change had been removed from the testing queue. Artifacts built from this change will not be released until either change 86679,4 (otopi) is fixed and this change is updated to refer to or rebased on the fixed version, or this change is modified to no longer depend on it. For further details about the change see: https://gerrit.ovirt.org/#/c/86869/1 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/86679/4 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/5154/

6 years, 2 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

Infra January 2018