[JIRA] (OVIRT-1918) Single project tests in change-queue-tester

Tuesday, 6 March 2018

This is a multi-part message in MIME format...

------------=_1520344092-23374-193
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit

    [
https://ovirt-jira.atlassian.net/browse/OVIRT-1918?page=com.atlassian.jir...
] 

Dafna Ron commented on OVIRT-1918:
----------------------------------

we monitor and report an issue once its identified. 
we do not however, report every failed change which has failed because of the original
root cause. 

I do try to go and either re-trigger or re-merge changes if they failed cq once the root
cause is fixed but if an issue lasts for a day or two it would be difficult to make sure
we do not miss anything. 

maybe we need to add a warning message after an issue is fixed which lists all changes
that need to be re-triggered or re-merged? 

...
 Single project tests in change-queue-tester
 -------------------------------------------

                 Key: OVIRT-1918
                 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1918
             Project: oVirt - virtualization made easy
          Issue Type: By-EMAIL
            Reporter: sbonazzo
            Assignee: infra

 Please change change-queue-tester jobs for testing a single project at a
 time (ok for multiple patches at once, but from the same project).
 Right now if multiple patches are merged between a change-queue-tester
 execution and the next one are done, all of them will be tested in the next
 run, even if the changes are in different projects.
 So, supposing project A and B are completely fine, a failure in project C
 can still prevent changes in A and B to go ahead through the pipeline and
 get released.
 This cause major headaches at least to me, requiring me to go again over
 all the HEAD of the projects not being published and run yet again "ci
 re-merge please" again and again and again until I'm lucky enough to have
 nobody else merging patches or having all the ttested patches pass at once.
 I understand the need to reduce the amount of executions of the job since
 it takes an hour to execute but right now it's stealing days of execution
 for getting a patch landing on tested repo.
 -- 
 SANDRO BONAZZOLA
 ASSOCIATE MANAGER, SOFTWARE ENGINEERING, EMEA ENG VIRTUALIZATION R&D
 Red Hat EMEA <https://www.redhat.com/>
 <https://red.ht/sig>
 TRIED. TESTED. TRUSTED. <https://redhat.com/trusted> 

--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100081)

------------=_1520344092-23374-193
Content-Type: text/html; charset="UTF-8"
Content-Disposition: inline
Content-Transfer-Encoding: 7bit

<html><body>
<pre>[
https://ovirt-jira.atlassian.net/browse/OVIRT-1918?page=com.atlassian.jir...
]</pre>
<h3>Dafna Ron commented on OVIRT-1918:</h3>
<p>we monitor and report an issue once its identified. we do not however, report
every failed change which has failed because of the original root cause.</p>
<p>I do try to go and either re-trigger or re-merge changes if they failed cq once
the root cause is fixed but if an issue lasts for a day or two it would be difficult to
make sure we do not miss anything.</p>
<p>maybe we need to add a warning message after an issue is fixed which lists all
changes that need to be re-triggered or re-merged?</p>
<blockquote><h3>Single project tests in change-queue-tester</h3>
<pre>     Key: OVIRT-1918
     URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1918
 Project: oVirt - virtualization made easy
         Issue Type: By-EMAIL
Reporter: sbonazzo
Assignee: infra</pre>
<p>Please change change-queue-tester jobs for testing a single project at a time (ok
for multiple patches at once, but from the same project). Right now if multiple patches
are merged between a change-queue-tester execution and the next one are done, all of them
will be tested in the next run, even if the changes are in different projects. So,
supposing project A and B are completely fine, a failure in project C can still prevent
changes in A and B to go ahead through the pipeline and get released. This cause major
headaches at least to me, requiring me to go again over all the HEAD of the projects not
being published and run yet again &ldquo;ci re-merge please&rdquo; again and again
and again until I'm lucky enough to have nobody else merging patches or having all the
ttested patches pass at once. I understand the need to reduce the amount of executions of
the job since it takes an hour to execute but right now it's stealing days of
execution for getting a patch landing on tested repo. &mdash; SANDRO BONAZZOLA
ASSOCIATE MANAGER, SOFTWARE ENGINEERING, EMEA ENG VIRTUALIZATION R&amp;D Red Hat EMEA
&lt;<a
href="https://www.redhat.com/">https://www.redhat.com/</a...
&lt;<a href="https://red.ht/sig">https://red.ht/sig</a>&gt;
TRIED. TESTED. TRUSTED. &lt;<a
href="https://redhat.com/trusted">https://redhat.com/trusted...
<p>&mdash; This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100081)</p>

------------=_1520344092-23374-193--

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011