May 2018 - Infra - oVirt List Archives

[CQ]: 91609, 5 (ovirt-engine) failed "ovirt-4.2" system tests, but isn't the failure root cause
by oVirt Jenkins 28 May '18

28 May '18

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

1 0

[CQ]: 91610, 4 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 28 May '18

28 May '18

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

1 0

[CQ]: 91668, 2 (ovirt-engine) failed "ovirt-4.2" system tests, but isn't the failure root cause
by oVirt Jenkins 28 May '18

28 May '18

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

1 0

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

28 May '18

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

1 0

[JIRA] (OVIRT-1182) Make a nice Garavter icon for Jenkins to show up in Gerrit comments
by Barak Korren (oVirt JIRA) 28 May '18

28 May '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1182?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1182: -------------------------------- Assignee: Barak Korren (was: infra) Status: In Progress (was: To Do) > Make a nice Garavter icon for Jenkins to show up in Gerrit comments > ------------------------------------------------------------------- > > Key: OVIRT-1182 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1182 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: oVirt CI > Reporter: Barak Korren > Assignee: Barak Korren > > Its nice if comments from Jenkins will have a Gravatar to make that clear, and more "friendly". > See for example the Kubernetes CI bot. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100086)

1 0

[JIRA] (OVIRT-2061) Real time updates in STDCI status page
by Daniel Belenky (oVirt JIRA) 28 May '18

28 May '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2061?page=com.atlassian.jira.… ] Daniel Belenky reassigned OVIRT-2061: ------------------------------------- Assignee: Daniel Belenky (was: infra) > Real time updates in STDCI status page > -------------------------------------- > > Key: OVIRT-2061 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2061 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Components: Standard CI (Pipelines) > Reporter: Daniel Belenky > Assignee: Daniel Belenky > > As an STDCI user, I want to see "real time" updates of my code's output and to have access to artifacts without > having to wait for the job to finish so that I can address issues quickly. > BlueOcean seems to be slow, and in many cases, it takes almost half a minute to load. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100086)

1 0

[CQ]: 90569, 5 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 28 May '18

28 May '18

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

1 0

[JIRA] (OVIRT-2061) Real time updates in STDCI status page
by Daniel Belenky (oVirt JIRA) 28 May '18

28 May '18

Daniel Belenky created OVIRT-2061: ------------------------------------- Summary: Real time updates in STDCI status page Key: OVIRT-2061 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2061 Project: oVirt - virtualization made easy Issue Type: New Feature Components: Standard CI (Pipelines) Reporter: Daniel Belenky Assignee: infra As an STDCI user, I want to see "real time" updates of my code's output and to have access to artifacts without having to wait for the job to finish so that I can address issues quickly. BlueOcean seems to be slow, and in many cases, it takes almost half a minute to load. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100086)

1 0

[JIRA] (OVIRT-2061) Real time updates in STDCI status page
by Daniel Belenky (oVirt JIRA) 28 May '18

28 May '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2061?page=com.atlassian.jira.… ] Daniel Belenky updated OVIRT-2061: ---------------------------------- Epic Link: OVIRT-400 > Real time updates in STDCI status page > -------------------------------------- > > Key: OVIRT-2061 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2061 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Components: Standard CI (Pipelines) > Reporter: Daniel Belenky > Assignee: infra > > As an STDCI user, I want to see "real time" updates of my code's output and to have access to artifacts without > having to wait for the job to finish so that I can address issues quickly. > BlueOcean seems to be slow, and in many cases, it takes almost half a minute to load. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100086)

1 0

[CQ]: 91608, 4 (ovirt-engine) failed "ovirt-4.2" system tests, but isn't the failure root cause
by oVirt Jenkins 28 May '18

28 May '18

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

1 0