June 2021 - Infra - Ovirt List Archives

[JIRA] (OVIRT-3101) Add "ci system-test" command

by Yedidyah Bar David (oVirt JIRA)

[ https://ovirt-jira.atlassian.net/browse/OVIRT-3101?page=com.atlassian.jir... ] Yedidyah Bar David commented on OVIRT-3101: ------------------------------------------- On Thu, Jun 24, 2021 at 1:51 PM Marcin Sobczyk <msobczyk(a)redhat.com> wrote: > > > > On 6/23/21 5:44 PM, Nir Soffer wrote: > > Similar to "ci build", "ci test", "ci merge" add a new command that > > triggers OST run. > > > > Running OST is tied now in vdsm (and engine?) to Code-Review: +2. > > This causes trouble and does not allow non-maintainers to use the convenient OST > > infrastructure. > > > > Expected flow: > > > > 1. User add a comment with "ci system-test" > "ci system-test" is sooo long, I vote for "ci ost". +1. Perhaps we can add an optional suite name? E.g. 'ci ost ansible-suite-master' Best regards, -- Didi > Add "ci system-test" command > ---------------------------- > > Key: OVIRT-3101 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-3101 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Nir Soffer > Assignee: infra > > Similar to "ci build", "ci test", "ci merge" add a new command that > triggers OST run. > Running OST is tied now in vdsm (and engine?) to Code-Review: +2. > This causes trouble and does not allow non-maintainers to use the convenient OST > infrastructure. > Expected flow: > 1. User add a comment with "ci system-test" > 2. OST flow building and running OST triggered -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100166)

2 years, 10 months

1
0
0 / 0

[JIRA] (OVIRT-3101) Add "ci system-test" command

by Marcin Sobczyk (oVirt JIRA)

[ https://ovirt-jira.atlassian.net/browse/OVIRT-3101?page=com.atlassian.jir... ] Marcin Sobczyk commented on OVIRT-3101: --------------------------------------- On 6/23/21 5:44 PM, Nir Soffer wrote: > Similar to "ci build", "ci test", "ci merge" add a new command that > triggers OST run. > > Running OST is tied now in vdsm (and engine?) to Code-Review: +2. > This causes trouble and does not allow non-maintainers to use the convenient OST > infrastructure. > > Expected flow: > > 1. User add a comment with "ci system-test" "ci system-test" is sooo long, I vote for "ci ost". Regards, Marcin > 2. OST flow building and running OST triggered > _______________________________________________ > Devel mailing list -- devel(a)ovirt.org > To unsubscribe send an email to devel-leave(a)ovirt.org > Privacy Statement: https://www.ovirt.org/privacy-policy.html > oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ > List Archives: https://lists.ovirt.org/archives/list/devel@ovirt.org/message/2FCJZLFJJ2S... > Add "ci system-test" command > ---------------------------- > > Key: OVIRT-3101 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-3101 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Nir Soffer > Assignee: infra > > Similar to "ci build", "ci test", "ci merge" add a new command that > triggers OST run. > Running OST is tied now in vdsm (and engine?) to Code-Review: +2. > This causes trouble and does not allow non-maintainers to use the convenient OST > infrastructure. > Expected flow: > 1. User add a comment with "ci system-test" > 2. OST flow building and running OST triggered -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100166)

2 years, 10 months

1
0
0 / 0

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

2 years, 10 months

1
0
0 / 0

[oVirt Jenkins] cleanup-gated-dummy-master - Build #551 - FAILURE!

by jenkins＠jenkins.phx.ovirt.org

Build: https://jenkins.ovirt.org/job/cleanup-gated-dummy-master/551/ Build Name: #551 Build Status: FAILURE Gerrit change: null - title: null - project: null - branch: null - author: null <null>

2 years, 10 months

1
0
0 / 0

oVirt infra daily report - unstable production jobs - 1596

by jenkins＠jenkins.phx.ovirt.org

Good morning! Attached is the HTML page with the jenkins status report. You can see it also here: - https://jenkins.ovirt.org/job/system_jenkins-report/1596//artifact/export... Cheers, Jenkins

2 years, 10 months

1
0
0 / 0

[JIRA] (OVIRT-3101) Add "ci system-test" command

by Nir Soffer (oVirt JIRA)

Nir Soffer created OVIRT-3101: --------------------------------- Summary: Add "ci system-test" command Key: OVIRT-3101 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-3101 Project: oVirt - virtualization made easy Issue Type: By-EMAIL Reporter: Nir Soffer Assignee: infra Similar to "ci build", "ci test", "ci merge" add a new command that triggers OST run. Running OST is tied now in vdsm (and engine?) to Code-Review: +2. This causes trouble and does not allow non-maintainers to use the convenient OST infrastructure. Expected flow: 1. User add a comment with "ci system-test" 2. OST flow building and running OST triggered -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100166)

2 years, 10 months

1
0
0 / 0

[JIRA] (OVIRT-3100) Add OST flag to all oVirt projects

by Nir Soffer (oVirt JIRA)

Nir Soffer created OVIRT-3100: --------------------------------- Summary: Add OST flag to all oVirt projects Key: OVIRT-3100 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-3100 Project: oVirt - virtualization made easy Issue Type: By-EMAIL Reporter: Nir Soffer Assignee: infra Similar to Continuous-Integration flag, OST needs its own flag. OST will set this flag when OST build started from gerrit was started. We want to make this field mandatory for merging patches, like Continuous-Integration. Like Continuous-Integration maintainers should be able to override the value after OST completed, or set the value before OST started. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100166)

2 years, 10 months

1
0
0 / 0

[CQ]: 115368, 1 (ovirt-system-tests) 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 115368,1 (ovirt-system-tests) failed. However, this change seems not to be the root cause for this failure. Change 113144,5 (ovirt-system-tests) 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 113144,5 (ovirt-system-tests) 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/ovirt-system-tests/+/#/c/115368/1 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/c/ovirt-system-tests/+/#/c/113144/5 For failed test results see: https://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/30387/

2 years, 10 months

1
0
0 / 0

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

2 years, 10 months

1
0
0 / 0

[oVirt Jenkins] ovirt-system-tests_basic-suite-4.3_nightly - Build # 593 - Failure!

by jenkins＠jenkins.phx.ovirt.org

Project: https://jenkins.ovirt.org/job/ovirt-system-tests_basic-suite-4.3_nightly/ Build: https://jenkins.ovirt.org/job/ovirt-system-tests_basic-suite-4.3_nightly/... Build Number: 593 Build Status: Failure Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #593 [parthdhanjal] Updating max click version ----------------- Failed Tests: ----------------- No tests ran.

2 years, 10 months

1
2
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

Infra June 2021