May 2019 - Infra - oVirt List Archives

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

16 May '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2730?page=com.atlassian.jira.… ] Barak Korren commented on OVIRT-2730: ------------------------------------- On Wed, 15 May 2019 at 18:58, Nir Soffer (oVirt JIRA) < Looking at the stdci.yaml file I get when cloning the patch - I don't see any substages or distroes defined in it, so STDCI does what it can in that case - run the default substage for the specified architectures that it can find script files for. Is this based on a very old version of vdsm's stdci.yaml ? You can see the exact same thing happening for check-patch triggered from Gerrit: https://jenkins.ovirt.org/blue/organizations/jenkins/vdsm_standard-check-pa… In fact running check-patch with manual runner is quite useless, since CI will always run it for you anyway when you push the patch... Because you can't select substages like that. check-network would not work since its not defined in stdci.yaml for that patch. It runs the exact same code. - allow selection of a sub stage? Probably not gonna happen - this would require some deep changes. - nice to have - allow selection of multiple sub stages Same as above, you can only select a stage at this point. -- Barak Korren RHV DevOps team , RHCE, RHCi Red Hat EMEA redhat.com | TRIED. TESTED. TRUSTED. | redhat.com/trusted > 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

[CQ]: 99706, 11 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 16 May '19

16 May '19

A system test invoked by the "ovirt-master" change queue including change 99706,11 (ovirt-engine) failed. However, this change seems not to be the root cause for this failure. Change 99372,6 (ovirt-engine) 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 99372,6 (ovirt-engine) 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/99706/11 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/99372/6 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/14154/

1 0

[CQ]: 99805, 6 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 16 May '19

16 May '19

A system test invoked by the "ovirt-master" change queue including change 99805,6 (ovirt-engine) failed. However, this change seems not to be the root cause for this failure. Change 99372,6 (ovirt-engine) 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 99372,6 (ovirt-engine) 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/99805/6 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/99372/6 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/14152/

1 0

[CQ]: 100093, 2 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 16 May '19

16 May '19

A system test invoked by the "ovirt-master" change queue including change 100093,2 (ovirt-engine) failed. However, this change seems not to be the root cause for this failure. Change 99372,6 (ovirt-engine) 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 99372,6 (ovirt-engine) 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/100093/2 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/99372/6 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/14151/

1 0

[CQ]: 100111,1 (ovirt-host) failed "ovirt-4.3" system tests
by oVirt Jenkins 16 May '19

16 May '19

Change 100111,1 (ovirt-host) 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/100111/1 For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.3_change-queue-tester/905/

1 0

[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