February 2016 - Infra - Ovirt List Archives

[JIRA] (OVIRT-381) lots of jenkins jobs failing on "syntax error near unexpected token `\ '"

by Tomas Jelinek (oVirt JIRA)

[ https://ovirt-jira.atlassian.net/browse/OVIRT-381?page=com.atlassian.jira... ] Tomas Jelinek commented on OVIRT-381: ------------------------------------- no, I have not seen it for some time, seems fixed > lots of jenkins jobs failing on "syntax error near unexpected token `\ '" > ------------------------------------------------------------------------- > > Key: OVIRT-381 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-381 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Tomas Jelinek > Assignee: infra > > Hi, > lots of jobs are failing now on gerrit, for example: > http://jenkins.ovirt.org/job/ovirt-engine_3.6_check-patch-fc22-x86_64/167... > http://jenkins.ovirt.org/job/ovirt-engine_3.6_check-patch-fc22-x86_64/167... > Thanx, > Tomas -- This message was sent by Atlassian JIRA (v7.1.0-OD-06-005#71002)

8 years, 9 months

1
0
0 / 0

[oVirt Jenkins] ovirt-engine_3.6_upgrade-from-3.6_el6_merged - Build # 883 - Failure!

by jenkins＠ovirt.org

------=_Part_711_1055816293.1455566188746 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Project: http://jenkins.ovirt.org/job/ovirt-engine_3.6_upgrade-from-3.6_el6_merged/ Build: http://jenkins.ovirt.org/job/ovirt-engine_3.6_upgrade-from-3.6_el6_merged... Build Number: 883 Build Status: Failure Triggered By: Triggered by Gerrit: https://gerrit.ovirt.org/53390 ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #883 [Scott J Dickerson] webadmin: Add a scroll panel to SetupNetworks networks list ----------------- Failed Tests: ----------------- No tests ran. ------=_Part_711_1055816293.1455566188746--

8 years, 9 months

1
0
0 / 0

[JIRA] (OVIRT-417) Build oVirt 3.6.2 RC3

by sbonazzo (oVirt JIRA)

[ https://ovirt-jira.atlassian.net/browse/OVIRT-417?page=com.atlassian.jira... ] sbonazzo updated OVIRT-417: --------------------------- Assignee: sbonazzo (was: infra) Status: Accepted (was: New) > Build oVirt 3.6.2 RC3 > --------------------- > > Key: OVIRT-417 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-417 > Project: oVirt - virtualization made easy > Issue Type: Task > Components: Repositories Mgmt > Affects Versions: Test > Reporter: sbonazzo > Assignee: sbonazzo > Priority: Highest > -- This message was sent by Atlassian JIRA (v7.1.0-OD-06-005#71002)

8 years, 9 months

1
0
0 / 0

[JIRA] (OVIRT-417) Build oVirt 3.6.2 RC3

by sbonazzo (oVirt JIRA)

sbonazzo created OVIRT-417: ------------------------------ Summary: Build oVirt 3.6.2 RC3 Key: OVIRT-417 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-417 Project: oVirt - virtualization made easy Issue Type: Task Components: Repositories Mgmt Affects Versions: Test Reporter: sbonazzo Assignee: infra Priority: Highest -- This message was sent by Atlassian JIRA (v7.1.0-OD-06-005#71002)

8 years, 9 months

1
0
0 / 0

[JIRA] (OVIRT-415) [jenkins] increase disk space for jobs archives

by eyal edri [Administrator] (oVirt JIRA)

[ https://ovirt-jira.atlassian.net/browse/OVIRT-415?page=com.atlassian.jira... ] eyal edri [Administrator] reassigned OVIRT-415: ----------------------------------------------- Assignee: snaftaly (was: infra) As we discussed, please review old obselete gerrit backups on the jenkins master and remove. This should clear out 14GB of space. We are already working on migrating the jenkins instance into a production VM in PHX. The migration will get higher speed and priority after we release oVIrt 3.6.3, as we don't want to add risk to the GA. > [jenkins] increase disk space for jobs archives > ----------------------------------------------- > > Key: OVIRT-415 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-415 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: Jenkins > Affects Versions: Production > Reporter: sbonazzo > Assignee: snaftaly > Priority: High > > jenkins master was dead this morning being out of disk space. > there are several jobs archiving more than 1GB of artifacts and the space on the master is too low to save all of them. > Here's a list of biggest jobs: > # du -sh *|grep G| sort -h > 1.1G ovirt-engine_3.6.3_check-merged-el6-x86_64 > 1.1G ovirt-engine_3.6.3_check-merged-el7-x86_64 > 1.1G ovirt-engine_3.6.3_check-merged-fc23-x86_64 > 1.1G ovirt-engine_3.6.3_check-patch-el6-x86_64 > 1.1G ovirt-engine_3.6_check-merged-el6-x86_64 > 1.1G ovirt-engine_3.6_check-merged-fc23-x86_64 > 1.1G ovirt-engine_3.6_check-patch-el6-x86_64 > 1.1G ovirt-engine_3.6_check-patch-el7-x86_64 > 1.1G ovirt-engine-wildfly10_master_create-rpms-el7-x86_64_merged > 1.1G spagobi_master_create-rpms-el7-x86_64_created > 1.1G spagobi_master_create-rpms-el7-x86_64_merged > 1.2G ovirt-appliance-engine_3.5_merged > 1.2G ovirt-engine_3.6.3_check-patch-el7-x86_64 > 1.2G ovirt-engine_3.6_check-merged-el7-x86_64 > 1.2G ovirt_integration-test-poc_created > 1.3G ovirt-engine_master_coverity-analysis_merged > 1.3G ovirt-engine-wildfly10_master_create-rpms-fc22-x86_64_merged > 1.3G ovirt-live_3.6-create-iso > 1.3G ovirt-live_master-create-iso > 1.5G ovirt-engine_master_build-artifacts-el6-x86_64_no_spm_testing > 1.6G ovirt-engine-wildfly10_master_create-rpms-el7-x86_64_created > 1.6G ovirt-engine-wildfly10_master_create-rpms-fc22-x86_64_created > 1.8G ovirt-engine_3.5_create-rpms_merged > 2.8G ovirt-node_master_create-iso-el7_merged > 3.6G ovirt-engine_3.5-gluster_create-rpms_merged > 4.2G ovirt-engine-jboss-as_master_create-rpms_merged > 4.4G ovirt-engine_master_find-bugs_merged > 4.5G ovirt-node_ovirt-3.6_create-iso-el7_merged > 5.0G ovirt-engine_master_build-artifacts-fc23-x86_64 > 5.3G ovirt-engine_master_build-artifacts-el7-x86_64 > 5.4G ovirt-engine_3.6.3_build-artifacts-fc23-x86_64 > 5.6G ovirt-engine_3.6.3_build-artifacts-fc22-x86_64 > 5.9G ovirt-engine_3.6_build-artifacts-fc23-x86_64 > 6.0G ovirt-engine_3.6.3_build-artifacts-el6-x86_64 > 6.1G ovirt-engine_3.6.3_build-artifacts-el7-x86_64 > 6.6G ovirt-appliance_ovirt-3.6_build-artifacts-el7-x86_64 > 7.0G ovirt-engine_3.6_build-artifacts-fc22-x86_64 > 7.5G ovirt-engine_3.6_build-artifacts-el7-x86_64 > 8.0G ovirt-engine_3.6_build-artifacts-el6-x86_64 > 9.7G spagobi_repo_merged > 12G ovirt-appliance_master_build-artifacts-el7-x86_64 > 13G ovirt-node-ng_master_build-artifacts-fc22-x86_64 > Please increase the space on jenkins slave or reduce the number of archived builds on above jobs -- This message was sent by Atlassian JIRA (v7.1.0-OD-06-005#71002)

8 years, 9 months

1
0
0 / 0

[JIRA] (OVIRT-416) [standard-ci] build-artifacts should reuse the artifacts built on check-merged if any

by David Caro Estevez (oVirt JIRA)

[ https://ovirt-jira.atlassian.net/browse/OVIRT-416?page=com.atlassian.jira... ] David Caro Estevez updated OVIRT-416: ------------------------------------- Issue Type: Improvement (was: Bug) > [standard-ci] build-artifacts should reuse the artifacts built on check-merged if any > ------------------------------------------------------------------------------------- > > Key: OVIRT-416 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-416 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Reporter: David Caro Estevez > Assignee: infra > > Right now most projects just rebuild twice the artifacts, what for some means a big waste of resources, if we could just reuse what was built previously there would be no rebuilding. > Something to take into account is that the distributions that check-merged and build-artifacts run for might not match, so you can be running check-merged only on fc23 but building artifacts for fc23, fc22 an el7 (as an example), maybe we should not allow different distros on each stage?| -- This message was sent by Atlassian JIRA (v7.1.0-OD-06-005#71002)

8 years, 9 months

1
0
0 / 0

[JIRA] (OVIRT-416) [standard-ci] build-artifacts should reuse the artifacts built on check-merged if any

by David Caro Estevez (oVirt JIRA)

David Caro Estevez created OVIRT-416: ---------------------------------------- Summary: [standard-ci] build-artifacts should reuse the artifacts built on check-merged if any Key: OVIRT-416 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-416 Project: oVirt - virtualization made easy Issue Type: Bug Reporter: David Caro Estevez Assignee: infra Right now most projects just rebuild twice the artifacts, what for some means a big waste of resources, if we could just reuse what was built previously there would be no rebuilding. Something to take into account is that the distributions that check-merged and build-artifacts run for might not match, so you can be running check-merged only on fc23 but building artifacts for fc23, fc22 an el7 (as an example), maybe we should not allow different distros on each stage?| -- This message was sent by Atlassian JIRA (v7.1.0-OD-06-005#71002)

8 years, 9 months

1
0
0 / 0

[JIRA] (OVIRT-414) [standard-ci] build stage should start only after check-merged stage completes

by David Caro Estevez (oVirt JIRA)

[ https://ovirt-jira.atlassian.net/browse/OVIRT-414?page=com.atlassian.jira... ] David Caro Estevez commented on OVIRT-414: ------------------------------------------ The issue with this is that it effectively duplicates the run time, as most projects for now compile and package twice (see ovirt-engine) the time from merge to built and tested will change from ~1:30 to ~3h if it does not fail (as it's expected not to fail in most cases). I think this should go only after we can reuse artifacts from job to job > [standard-ci] build stage should start only after check-merged stage completes > ------------------------------------------------------------------------------ > > Key: OVIRT-414 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-414 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: Jenkins > Affects Versions: Production > Reporter: sbonazzo > Assignee: infra > > In order to save jenkins resources, build stage should be triggered only after check-merged stage passes. -- This message was sent by Atlassian JIRA (v7.1.0-OD-06-005#71002)

8 years, 9 months

1
0
0 / 0

[JIRA] (OVIRT-415) [jenkins] increase disk space for jobs archives

by sbonazzo (oVirt JIRA)

sbonazzo created OVIRT-415: ------------------------------ Summary: [jenkins] increase disk space for jobs archives Key: OVIRT-415 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-415 Project: oVirt - virtualization made easy Issue Type: Improvement Components: Jenkins Affects Versions: Production Reporter: sbonazzo Assignee: infra Priority: High jenkins master was dead this morning being out of disk space. there are several jobs archiving more than 1GB of artifacts and the space on the master is too low to save all of them. Here's a list of biggest jobs: # du -sh *|grep G| sort -h 1.1G ovirt-engine_3.6.3_check-merged-el6-x86_64 1.1G ovirt-engine_3.6.3_check-merged-el7-x86_64 1.1G ovirt-engine_3.6.3_check-merged-fc23-x86_64 1.1G ovirt-engine_3.6.3_check-patch-el6-x86_64 1.1G ovirt-engine_3.6_check-merged-el6-x86_64 1.1G ovirt-engine_3.6_check-merged-fc23-x86_64 1.1G ovirt-engine_3.6_check-patch-el6-x86_64 1.1G ovirt-engine_3.6_check-patch-el7-x86_64 1.1G ovirt-engine-wildfly10_master_create-rpms-el7-x86_64_merged 1.1G spagobi_master_create-rpms-el7-x86_64_created 1.1G spagobi_master_create-rpms-el7-x86_64_merged 1.2G ovirt-appliance-engine_3.5_merged 1.2G ovirt-engine_3.6.3_check-patch-el7-x86_64 1.2G ovirt-engine_3.6_check-merged-el7-x86_64 1.2G ovirt_integration-test-poc_created 1.3G ovirt-engine_master_coverity-analysis_merged 1.3G ovirt-engine-wildfly10_master_create-rpms-fc22-x86_64_merged 1.3G ovirt-live_3.6-create-iso 1.3G ovirt-live_master-create-iso 1.5G ovirt-engine_master_build-artifacts-el6-x86_64_no_spm_testing 1.6G ovirt-engine-wildfly10_master_create-rpms-el7-x86_64_created 1.6G ovirt-engine-wildfly10_master_create-rpms-fc22-x86_64_created 1.8G ovirt-engine_3.5_create-rpms_merged 2.8G ovirt-node_master_create-iso-el7_merged 3.6G ovirt-engine_3.5-gluster_create-rpms_merged 4.2G ovirt-engine-jboss-as_master_create-rpms_merged 4.4G ovirt-engine_master_find-bugs_merged 4.5G ovirt-node_ovirt-3.6_create-iso-el7_merged 5.0G ovirt-engine_master_build-artifacts-fc23-x86_64 5.3G ovirt-engine_master_build-artifacts-el7-x86_64 5.4G ovirt-engine_3.6.3_build-artifacts-fc23-x86_64 5.6G ovirt-engine_3.6.3_build-artifacts-fc22-x86_64 5.9G ovirt-engine_3.6_build-artifacts-fc23-x86_64 6.0G ovirt-engine_3.6.3_build-artifacts-el6-x86_64 6.1G ovirt-engine_3.6.3_build-artifacts-el7-x86_64 6.6G ovirt-appliance_ovirt-3.6_build-artifacts-el7-x86_64 7.0G ovirt-engine_3.6_build-artifacts-fc22-x86_64 7.5G ovirt-engine_3.6_build-artifacts-el7-x86_64 8.0G ovirt-engine_3.6_build-artifacts-el6-x86_64 9.7G spagobi_repo_merged 12G ovirt-appliance_master_build-artifacts-el7-x86_64 13G ovirt-node-ng_master_build-artifacts-fc22-x86_64 Please increase the space on jenkins slave or reduce the number of archived builds on above jobs -- This message was sent by Atlassian JIRA (v7.1.0-OD-06-005#71002)

8 years, 9 months

1
0
0 / 0

[JIRA] (OVIRT-414) [standard-ci] build stage should start only after check-merged stage completes

by sbonazzo (oVirt JIRA)

sbonazzo created OVIRT-414: ------------------------------ Summary: [standard-ci] build stage should start only after check-merged stage completes Key: OVIRT-414 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-414 Project: oVirt - virtualization made easy Issue Type: Improvement Components: Jenkins Affects Versions: Production Reporter: sbonazzo Assignee: infra In order to save jenkins resources, build stage should be triggered only after check-merged stage passes. -- This message was sent by Atlassian JIRA (v7.1.0-OD-06-005#71002)

8 years, 9 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

Infra February 2016