November 2019 - Infra - Ovirt List Archives

[CQ]: 103616, 32 (ovirt-engine) 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 103616,32 (ovirt-engine) failed. However, this change seems not to be the root cause for this failure. Change 103437,35 (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 103437,35 (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/103616/32 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/103437/35 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/17420/

4 years, 5 months

1
0
0 / 0

[JENKINS] Failed to setup proejct vdsm_standard-check-patch

by jenkins＠jenkins.phx.ovirt.org

Failed to run project_setup.sh for: #15075 vdsm [check-patch]. It probably means that docker_cleanup.py failed. This step doesn't fail the job, but we do collect data about such failures to find the root cause. Infra owner, ensure that we're not running out of disk space on vm0009.workers-phx.ovirt.org.

4 years, 5 months

1
0
0 / 0

[CQ]: 104962, 3 (ovirt-engine) 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 104962,3 (ovirt-engine) failed. However, this change seems not to be the root cause for this failure. Change 103437,35 (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 103437,35 (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/104962/3 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/103437/35 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/17416/

4 years, 5 months

1
0
0 / 0

[JIRA] (OVIRT-2843) Whitlisting users for CI on GitHub does not work

by Barak Korren (oVirt JIRA)

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2843?page=com.atlassian.jir... ] Barak Korren reassigned OVIRT-2843: ----------------------------------- Assignee: Barak Korren (was: infra) > Whitlisting users for CI on GitHub does not work > ------------------------------------------------ > > Key: OVIRT-2843 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2843 > Project: oVirt - virtualization made easy > Issue Type: Bug > Components: GitHub > Reporter: Tomas Golembiovsky > Assignee: Barak Korren > > I've tried multiple times to whitelist multiple different people in CI integration with GitHub by using the `ci add to whitelist` but it does not seem to work. IIRC it runs the tests but does not whitelist the PR originator. > By the way there's a typo in Infra documentation in the command -- the word _whitelist_ is misspelled. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100114)

4 years, 5 months

1
0
0 / 0

[JENKINS] Failed to setup proejct ovirt-engine-ui-extensions_standard-check-patch

by jenkins＠jenkins.phx.ovirt.org

Failed to run project_setup.sh for: #300 ovirt-engine-ui-extensions [check-patch]. It probably means that docker_cleanup.py failed. This step doesn't fail the job, but we do collect data about such failures to find the root cause. Infra owner, ensure that we're not running out of disk space on vm0009.workers-phx.ovirt.org.

4 years, 5 months

1
0
0 / 0

[JIRA] (OVIRT-2843) Whitlisting users for CI on GitHub does not work

by Tomas Golembiovsky (oVirt JIRA)

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2843?page=com.atlassian.jir... ] Tomas Golembiovsky commented on OVIRT-2843: ------------------------------------------- Btw it’s this project: [https://github.com/oVirt/v2v-conversion-host|https://github.com/oVirt/v2v...] > Whitlisting users for CI on GitHub does not work > ------------------------------------------------ > > Key: OVIRT-2843 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2843 > Project: oVirt - virtualization made easy > Issue Type: Bug > Components: GitHub > Reporter: Tomas Golembiovsky > Assignee: infra > > I've tried multiple times to whitelist multiple different people in CI integration with GitHub by using the `ci add to whitelist` but it does not seem to work. IIRC it runs the tests but does not whitelist the PR originator. > By the way there's a typo in Infra documentation in the command -- the word _whitelist_ is misspelled. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100114)

4 years, 5 months

1
0
0 / 0

[JIRA] (OVIRT-2843) Whitlisting users for CI on GitHub does not work

by Tomas Golembiovsky (oVirt JIRA)

Tomas Golembiovsky created OVIRT-2843: ----------------------------------------- Summary: Whitlisting users for CI on GitHub does not work Key: OVIRT-2843 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2843 Project: oVirt - virtualization made easy Issue Type: Bug Components: GitHub Reporter: Tomas Golembiovsky Assignee: infra I've tried multiple times to whitelist multiple different people in CI integration with GitHub by using the `ci add to whitelist` but it does not seem to work. IIRC it runs the tests but does not whitelist the PR originator. By the way there's a typo in Infra documentation in the command -- the word _whitelist_ is misspelled. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100114)

4 years, 5 months

1
0
0 / 0

[CQ]: 105134, 2 (vdsm-jsonrpc-java) 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 105134,2 (vdsm-jsonrpc-java) failed. However, this change seems not to be the root cause for this failure. Change 105027,2 (vdsm-jsonrpc-java) 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 105027,2 (vdsm-jsonrpc-java) 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/105134/2 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/105027/2 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/17412/

4 years, 5 months

1
0
0 / 0

[JENKINS] Failed to setup proejct ovirt-engine_standard-check-patch

by jenkins＠jenkins.phx.ovirt.org

Failed to run project_setup.sh for: #1934 ovirt-engine [check-patch]. It probably means that docker_cleanup.py failed. This step doesn't fail the job, but we do collect data about such failures to find the root cause. Infra owner, ensure that we're not running out of disk space on vm0009.workers-phx.ovirt.org.

4 years, 5 months

1
0
0 / 0

[JENKINS] Failed to setup proejct vdsm_standard-check-patch

by jenkins＠jenkins.phx.ovirt.org

Failed to run project_setup.sh for: #15042 vdsm [check-patch]. It probably means that docker_cleanup.py failed. This step doesn't fail the job, but we do collect data about such failures to find the root cause. Infra owner, ensure that we're not running out of disk space on vm0009.workers-phx.ovirt.org.

4 years, 5 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

Infra November 2019