- Infra - oVirt List Archives

[CQ]: 99372,6 (ovirt-engine) failed "ovirt-master" system tests
by oVirt Jenkins 16 May '19

16 May '19

Change 99372,6 (ovirt-engine) 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/99372/6 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/14148/

1 0

[CQ]: 100083,1 (ovirt-node-ng-image) failed "ovirt-4.3" system tests
by oVirt Jenkins 16 May '19

16 May '19

Change 100083,1 (ovirt-node-ng-image) is probably the reason behind recent system test failures in the "ovirt-4.3" 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/100083/1 For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.3_change-queue-tester/897/

1 0

adding myself to CI whitelist
by Liran Rotenberg 16 May '19

16 May '19

Hi, I would like to add myself to the CI whitelist. I need it in order to build CI and check my patch for example: https://gerrit.ovirt.org/#/c/99970/ Thanks, Liran.

3 3

[CQ]: 100067, 1 (ovirt-engine-api-explorer) failed "ovirt-4.3" system tests
by oVirt Jenkins 16 May '19

16 May '19

Change 100067,1 (ovirt-engine-api-explorer) is probably the reason behind recent system test failures in the "ovirt-4.3" 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/100067/1 For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.3_change-queue-tester/896/

1 0

[JIRA] (OVIRT-2730) Running sub stages using https://jenkins.ovirt.org/job/standard-manual-runner/
by Nir Soffer (oVirt JIRA) 16 May '19

16 May '19

Nir Soffer created OVIRT-2730: --------------------------------- Summary: Running sub stages using https://jenkins.ovirt.org/job/standard-manual-runner/ Key: OVIRT-2730 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2730 Project: oVirt - virtualization made easy Issue Type: By-EMAIL Reporter: Nir Soffer Assignee: infra I tried to run check-patch and check-patch linters substage from the command line: using: https://github.com/nirs/oci/pull/37 I assumed that this will run the entire check-patch stage, including all the sub stages: ./ovirt-ci run -s check-patch 100007 But it run something that looks like check-patch with el7: https://jenkins.ovirt.org/blue/organizations/jenkins/standard-manual-runner… The test environment seems to be different that what we have when check-patch is triggered from gerrit. Then I tried to run the linters substage: ./ovirt-ci run -s check-patch.linters 100007 https://jenkins.ovirt.org/blue/organizations/jenkins/standard-manual-runner… ./ovirt-ci run -s check-patch.linters 100007 https://jenkins.ovirt.org/blue/organizations/jenkins/standard-manual-runner… Both succeeded without running anything :-) Running build-artifacts works, not sure about check-network. Can we fix the manual job so: - it run exactly the same way as it run when gerrit trigger the job - allow selection of a sub stage? - nice to have - allow selection of multiple sub stages Nir -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100102)

2 1

[oVirt Jenkins] ovirt-system-tests_compat-4.2-suite-master - Build # 579 - Failure!
by jenkins＠jenkins.phx.ovirt.org 15 May '19

15 May '19

Project: http://jenkins.ovirt.org/job/ovirt-system-tests_compat-4.2-suite-master/ Build: http://jenkins.ovirt.org/job/ovirt-system-tests_compat-4.2-suite-master/579/ Build Number: 579 Build Status: Failure Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #579 No changes ----------------- Failed Tests: ----------------- No tests ran.

1 1

oVirt infra daily report - unstable production jobs - 826
by jenkins＠jenkins.phx.ovirt.org 15 May '19

15 May '19

Good morning! Attached is the HTML page with the jenkins status report. You can see it also here: - http://jenkins.ovirt.org/job/system_jenkins-report/826//artifact/exported-a… Cheers, Jenkins

1 0

[CQ]: 100050, 1 (ovirt-engine-metrics) failed "ovirt-master" system tests
by oVirt Jenkins 15 May '19

15 May '19

Change 100050,1 (ovirt-engine-metrics) 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/100050/1 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/14130/

1 0

[JIRA] (OVIRT-2730) Running sub stages using https://jenkins.ovirt.org/job/standard-manual-runner/
by Nir Soffer (oVirt JIRA) 15 May '19

15 May '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2730?page=com.atlassian.jira.… ] Nir Soffer commented on OVIRT-2730: ----------------------------------- On Wed, May 15, 2019 at 6:56 PM Nir Soffer <nsoffer(a)redhat.com> wrote: > I tried to run check-patch and check-patch linters substage from the > command line: > > using: > https://github.com/nirs/oci/pull/37 > > I assumed that this will run the entire check-patch stage, including all > the sub stages: > ./ovirt-ci run -s check-patch 100007 > > But it run something that looks like check-patch with el7: > > https://jenkins.ovirt.org/blue/organizations/jenkins/standard-manual-runner… > > The test environment seems to be different that what we have when > check-patch is triggered > from gerrit. > For reference, I started only this build, from Jenkins UI: https://jenkins.ovirt.org/blue/organizations/jenkins/standard-manual-runner… Which seem to the same thing. > > Then I tried to run the linters substage: > > ./ovirt-ci run -s check-patch.linters 100007 > > https://jenkins.ovirt.org/blue/organizations/jenkins/standard-manual-runner… > > ./ovirt-ci run -s check-patch.linters 100007 > > https://jenkins.ovirt.org/blue/organizations/jenkins/standard-manual-runner… > > Both succeeded without running anything :-) > > Running build-artifacts works, not sure about check-network. > > Can we fix the manual job so: > - it run exactly the same way as it run when gerrit trigger the job > - allow selection of a sub stage? > - nice to have - allow selection of multiple sub stages > > Nir > > Running sub stages using https://jenkins.ovirt.org/job/standard-manual-runner/ > ------------------------------------------------------------------------------ > > Key: OVIRT-2730 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2730 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Nir Soffer > Assignee: infra > > I tried to run check-patch and check-patch linters substage from the > command line: > using: > https://github.com/nirs/oci/pull/37 > I assumed that this will run the entire check-patch stage, including all > the sub stages: > ./ovirt-ci run -s check-patch 100007 > But it run something that looks like check-patch with el7: > https://jenkins.ovirt.org/blue/organizations/jenkins/standard-manual-runner… > The test environment seems to be different that what we have when > check-patch is triggered > from gerrit. > Then I tried to run the linters substage: > ./ovirt-ci run -s check-patch.linters 100007 > https://jenkins.ovirt.org/blue/organizations/jenkins/standard-manual-runner… > ./ovirt-ci run -s check-patch.linters 100007 > https://jenkins.ovirt.org/blue/organizations/jenkins/standard-manual-runner… > Both succeeded without running anything :-) > Running build-artifacts works, not sure about check-network. > Can we fix the manual job so: > - it run exactly the same way as it run when gerrit trigger the job > - allow selection of a sub stage? > - nice to have - allow selection of multiple sub stages > Nir -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100102)

1 0

[CQ]: 3ea7a2a (ovirt-ansible-vm-infra) failed "ovirt-4.3" system tests
by oVirt Jenkins 15 May '19

15 May '19

Change 3ea7a2a (ovirt-ansible-vm-infra) is probably the reason behind recent system test failures in the "ovirt-4.3" 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://github.com/oVirt/ovirt-ansible-vm-infra/commit/3ea7a2a576d7e4413123… For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.3_change-queue-tester/888/

1 0