Packages not landed on tested repo
by Sandro Bonazzola
Hi,
looks like we have some packages which never passed OST, never landed
in ovirt-4.2-snapshot repo
and are currently causing failure building the appliance from 4.2 snapshot repo:
03:17:20,893 INFO program:Error: Package:
ovirt-engine-4.2.2.3-0.0.master.20180305171049.git0e81394.el7.centos.noarch
(ovirt-4.2-snapshot)
03:17:20,893 INFO program:Requires: ovirt-ansible-roles >= 1.1.2
03:17:20,894 INFO program:Error: Package:
ovirt-engine-4.2.2.3-0.0.master.20180305171049.git0e81394.el7.centos.noarch
(ovirt-4.2-snapshot)
03:17:20,896 INFO program:Requires: ovirt-js-dependencies
03:17:20,897 INFO program:Error: Package:
ovirt-engine-4.2.2.3-0.0.master.20180305171049.git0e81394.el7.centos.noarch
(ovirt-4.2-snapshot)
03:17:20,897 INFO program:Requires: ovirt-engine-wildfly-overlay >= 11.0.1
03:17:20,899 INFO program:Error: Package:
ovirt-engine-api-explorer-0.0.3-0.alpha.1.20180215git9b54c9c.el7.centos.noarch
(ovirt-4.2-snapshot)
03:17:20,900 INFO program:Requires: ovirt-js-dependencies >= 1.2
I'm now trying to get the missing packages pass thorough the whole testing
pipeline but be aware those packages have already been released 3 months
ago so they are stable and manually tested and were passing master OST.
I've no clue on why they are missing in the 4.2 testing pipeline.
--
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>
6 years, 2 months
[JIRA] (OVIRT-1918) Single project tests in change-queue-tester
by Barak Korren (oVirt JIRA)
This is a multi-part message in MIME format...
------------=_1520340937-32412-262
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
[ https://ovirt-jira.atlassian.net/browse/OVIRT-1918?page=com.atlassian.jir... ]
Barak Korren commented on OVIRT-1918:
-------------------------------------
{quote}
How a pacakge maintainer will know that a package didn't land in tested?
It tooks me 2 months to discover we have packages not getting in tested and I noticed just by mistake.
And I'm one of those maintainers that cares a lot about packages being published.
{quote}
[~dron]/infra-owner is supposed to tell you. This reporting is not fully automated yet because of false positives. Specifically WRT build failures you already get a comment in Gerrit.
> 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)
------------=_1520340937-32412-262
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>Barak Korren commented on OVIRT-1918:</h3>
<p>{quote} How a pacakge maintainer will know that a package didn't land in tested? It tooks me 2 months to discover we have packages not getting in tested and I noticed just by mistake. And I'm one of those maintainers that cares a lot about packages being published. {quote}</p>
<p>[~dron]/infra-owner is supposed to tell you. This reporting is not fully automated yet because of false positives. Specifically WRT build failures you already get a comment in Gerrit.</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 “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 <<a href="https://www.redhat.com/">https://www.redhat.com/</a>> <<a href="https://red.ht/sig">https://red.ht/sig</a>> TRIED. TESTED. TRUSTED. <<a href="https://redhat.com/trusted">https://redhat.com/trusted</a>></p></blockquote>
<p>— This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100081)</p>
<img src="https://u4043402.ct.sendgrid.net/wf/open?upn=i5TMWGV99amJbNxJpSp2-2BJ33BS..." alt="" width="1" height="1" border="0" style="height:1px !important;width:1px !important;border-width:0 !important;margin-top:0 !important;margin-bottom:0 !important;margin-right:0 !important;margin-left:0 !important;padding-top:0 !important;padding-bottom:0 !important;padding-right:0 !important;padding-left:0 !important;"/>
</body></html>
------------=_1520340937-32412-262--
6 years, 2 months
[JIRA] (OVIRT-1918) Single project tests in change-queue-tester
by Barak Korren (oVirt JIRA)
This is a multi-part message in MIME format...
------------=_1520340720-12851-179
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
[ https://ovirt-jira.atlassian.net/browse/OVIRT-1918?page=com.atlassian.jir... ]
Barak Korren commented on OVIRT-1918:
-------------------------------------
{quote}
I'm not sure that the bisection really works then, since we have still packages released 2 months ago not yet landing on tested. I don't recall to have seen any job triggered automatically after a change-queue-tester failure doing bisection tests.
{quote}
It works. 'change-queue-tester' itself gets re-triggered by 'change-queue' with a different set of patches after failure. Only failures that were narrowed down to a single patch are reported to infra-list.
You can see the state of the queue an the bisection status in a graphical display on the status page of the 'change-queue' job.
If you see something that wasn't moved to tested it can be because:
# the HEAD itself that was tested is really broken
# some build job failed because of an infra issue (e.g s390x/fcraw issue)
# OST itself was broken at the time of the test
"ci re-merge please" is for handling the last 2 reasons, essentially [~dron] or the infra owner is supposed to be monitoring the CQ reports, detecting theses cases and issuing "ci re-merge please" as needed.
> 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)
------------=_1520340720-12851-179
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>Barak Korren commented on OVIRT-1918:</h3>
<p>{quote} I'm not sure that the bisection really works then, since we have still packages released 2 months ago not yet landing on tested. I don't recall to have seen any job triggered automatically after a change-queue-tester failure doing bisection tests. {quote}</p>
<p>It works. ‘change-queue-tester’ itself gets re-triggered by ‘change-queue’ with a different set of patches after failure. Only failures that were narrowed down to a single patch are reported to infra-list.</p>
<p>You can see the state of the queue an the bisection status in a graphical display on the status page of the ‘change-queue’ job.</p>
<p>If you see something that wasn't moved to tested it can be because: # the HEAD itself that was tested is really broken # some build job failed because of an infra issue (e.g s390x/fcraw issue) # OST itself was broken at the time of the test</p>
<p>“ci re-merge please” is for handling the last 2 reasons, essentially [~dron] or the infra owner is supposed to be monitoring the CQ reports, detecting theses cases and issuing “ci re-merge please” as needed.</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 “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 <<a href="https://www.redhat.com/">https://www.redhat.com/</a>> <<a href="https://red.ht/sig">https://red.ht/sig</a>> TRIED. TESTED. TRUSTED. <<a href="https://redhat.com/trusted">https://redhat.com/trusted</a>></p></blockquote>
<p>— This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100081)</p>
<img src="https://u4043402.ct.sendgrid.net/wf/open?upn=i5TMWGV99amJbNxJpSp2-2BJ33BS..." alt="" width="1" height="1" border="0" style="height:1px !important;width:1px !important;border-width:0 !important;margin-top:0 !important;margin-bottom:0 !important;margin-right:0 !important;margin-left:0 !important;padding-top:0 !important;padding-bottom:0 !important;padding-right:0 !important;padding-left:0 !important;"/>
</body></html>
------------=_1520340720-12851-179--
6 years, 2 months
[JIRA] (OVIRT-1918) Single project tests in change-queue-tester
by sbonazzo (oVirt JIRA)
[ https://ovirt-jira.atlassian.net/browse/OVIRT-1918?page=com.atlassian.jir... ]
sbonazzo commented on OVIRT-1918:
---------------------------------
bq. Maybe we need to use always the official release repo as fallback to tested?
I don't think so. Tested repo should not require official release repo.
Official release should be eventually generated from tested repo, not the other way around.
bq. In case a specific PKG failed to build and it's maintainer didn't make sure
bq. to fix it and redeploy, it makes sense to get missing pkgs from latest
bq. official release, as we do in OST.
How a pacakge maintainer will know that a package didn't land in tested?
It tooks me 2 months to discover we have packages not getting in tested and I noticed just by mistake.
And I'm one of those maintainers that cares a lot about packages being published.
bq. Once the maintainer of the project will build a new image and it passes, it
bq. will be in tested.
That's not always true. I had several packages that required me to issue "ci re-merge please" multiple times before getting to tested repo without any code change on the project itself.
> 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)
6 years, 2 months
[JIRA] (OVIRT-1915) Add option to filter packages in OST manual
by eyal edri (oVirt JIRA)
This is a multi-part message in MIME format...
------------=_1520339293-14913-290
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
[ https://ovirt-jira.atlassian.net/browse/OVIRT-1915?page=com.atlassian.jir... ]
eyal edri commented on OVIRT-1915:
----------------------------------
Here is the ticket to add this repoman filter option to the upstream job,
can you or Dusan handle it?
A similar code already exists in the old manual job in d/s, which doesn't
work anymore.
On Sun, Mar 4, 2018 at 2:39 PM, Daniel Belenky (oVirt JIRA) <
--
Eyal edri
MANAGER
RHV DevOps
EMEA VIRTUALIZATION R&D
Red Hat EMEA <https://www.redhat.com/>
<https://red.ht/sig> TRIED. TESTED. TRUSTED. <https://redhat.com/trusted>
phone: +972-9-7692018
irc: eedri (on #tlv #rhev-dev #rhev-integ)
> Add option to filter packages in OST manual
> -------------------------------------------
>
> Key: OVIRT-1915
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1915
> Project: oVirt - virtualization made easy
> Issue Type: New Feature
> Reporter: Daniel Belenky
> Assignee: infra
> Labels: jenkins, ost
>
> Sometimes we want to filter packages that are being downloaded through repoman. In order to do so, we need to expose repoman's filtering API through Jenkins build parameters.
--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100081)
------------=_1520339293-14913-290
Content-Type: text/html; charset="UTF-8"
Content-Disposition: inline
Content-Transfer-Encoding: 7bit
<html><body>
<pre>[ https://ovirt-jira.atlassian.net/browse/OVIRT-1915?page=com.atlassian.jir... ]</pre>
<h3>eyal edri commented on OVIRT-1915:</h3>
<p>Here is the ticket to add this repoman filter option to the upstream job, can you or Dusan handle it? A similar code already exists in the old manual job in d/s, which doesn't work anymore.</p>
<p>On Sun, Mar 4, 2018 at 2:39 PM, Daniel Belenky (oVirt JIRA) <</p>
<p>—</p>
<p>Eyal edri</p>
<p>MANAGER</p>
<p>RHV DevOps</p>
<p>EMEA VIRTUALIZATION R&D</p>
<p>Red Hat EMEA <<a href="https://www.redhat.com/">https://www.redhat.com/</a>> <<a href="https://red.ht/sig">https://red.ht/sig</a>> TRIED. TESTED. TRUSTED. <<a href="https://redhat.com/trusted">https://redhat.com/trusted</a>> phone: +972-9-7692018 irc: eedri (on #tlv #rhev-dev #rhev-integ)</p>
<blockquote><h3>Add option to filter packages in OST manual</h3>
<pre> Key: OVIRT-1915
URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1915
Project: oVirt - virtualization made easy
Issue Type: New Feature
Reporter: Daniel Belenky
Assignee: infra
Labels: jenkins, ost</pre>
<p>Sometimes we want to filter packages that are being downloaded through repoman. In order to do so, we need to expose repoman's filtering API through Jenkins build parameters.</p></blockquote>
<p>— This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100081)</p>
<img src="https://u4043402.ct.sendgrid.net/wf/open?upn=i5TMWGV99amJbNxJpSp2-2BJ33BS..." alt="" width="1" height="1" border="0" style="height:1px !important;width:1px !important;border-width:0 !important;margin-top:0 !important;margin-bottom:0 !important;margin-right:0 !important;margin-left:0 !important;padding-top:0 !important;padding-bottom:0 !important;padding-right:0 !important;padding-left:0 !important;"/>
</body></html>
------------=_1520339293-14913-290--
6 years, 2 months
[JIRA] (OVIRT-1915) Add option to filter packages in OST manual
by Daniel Belenky (oVirt JIRA)
This is a multi-part message in MIME format...
------------=_1520167161-24881-147
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
[ https://ovirt-jira.atlassian.net/browse/OVIRT-1915?page=com.atlassian.jir... ]
Daniel Belenky updated OVIRT-1915:
----------------------------------
Labels: jenkins ost (was: )
> Add option to filter packages in OST manual
> -------------------------------------------
>
> Key: OVIRT-1915
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1915
> Project: oVirt - virtualization made easy
> Issue Type: New Feature
> Reporter: Daniel Belenky
> Assignee: infra
> Labels: jenkins, ost
>
> Sometimes we want to filter packages that are being downloaded through repoman. In order to do so, we need to expose repoman's filtering API through Jenkins build parameters.
--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100081)
------------=_1520167161-24881-147
Content-Type: text/html; charset="UTF-8"
Content-Disposition: inline
Content-Transfer-Encoding: 7bit
<html><body>
<pre>[ https://ovirt-jira.atlassian.net/browse/OVIRT-1915?page=com.atlassian.jir... ]</pre>
<h3>Daniel Belenky updated OVIRT-1915:</h3>
<pre>Labels: jenkins ost (was: )</pre>
<blockquote><h3>Add option to filter packages in OST manual</h3>
<pre> Key: OVIRT-1915
URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1915
Project: oVirt - virtualization made easy
Issue Type: New Feature
Reporter: Daniel Belenky
Assignee: infra
Labels: jenkins, ost</pre>
<p>Sometimes we want to filter packages that are being downloaded through repoman. In order to do so, we need to expose repoman's filtering API through Jenkins build parameters.</p></blockquote>
<p>— This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100081)</p>
<img src="https://u4043402.ct.sendgrid.net/wf/open?upn=i5TMWGV99amJbNxJpSp2-2BJ33BS..." alt="" width="1" height="1" border="0" style="height:1px !important;width:1px !important;border-width:0 !important;margin-top:0 !important;margin-bottom:0 !important;margin-right:0 !important;margin-left:0 !important;padding-top:0 !important;padding-bottom:0 !important;padding-right:0 !important;padding-left:0 !important;"/>
</body></html>
------------=_1520167161-24881-147--
6 years, 2 months
[JIRA] (OVIRT-1918) Single project tests in change-queue-tester
by eyal edri (oVirt JIRA)
[ https://ovirt-jira.atlassian.net/browse/OVIRT-1918?page=com.atlassian.jir... ]
eyal edri commented on OVIRT-1918:
----------------------------------
Maybe we need to use always the official release repo as fallback to tested?
In case a specific PKG failed to build and it's maintainer didn't make sure
to fix it and redeploy, it makes sense to get missing pkgs from latest
official release, as we do in OST.
Once the maintainer of the project will build a new image and it passes, it
will be in tested.
On Mar 6, 2018 14:02, "sbonazzo (oVirt JIRA)" <jira(a)ovirt-jira.atlassian.net>
wrote:
[ https://ovirt-jira.atlassian.net/browse/OVIRT-1918?page=com.atlassian.jir...
]
sbonazzo commented on OVIRT-1918:
I'm not sure that the bisection really works then, since we have still
packages released 2 months ago not yet landing on tested. I don't recall to
have seen any job triggered automatically after a change-queue-tester
failure doing bisection tests.
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 t ested 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)
> 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)
6 years, 2 months
Re: [JIRA] (OVIRT-1918) Single project tests in change-queue-tester
by Eyal Edri
Maybe we need to use always the official release repo as fallback to tested?
In case a specific PKG failed to build and it's maintainer didn't make sure
to fix it and redeploy, it makes sense to get missing pkgs from latest
official release, as we do in OST.
Once the maintainer of the project will build a new image and it passes, it
will be in tested.
On Mar 6, 2018 14:02, "sbonazzo (oVirt JIRA)" <jira(a)ovirt-jira.atlassian.net>
wrote:
[ https://ovirt-jira.atlassian.net/browse/OVIRT-1918?page=com.atlassian.jir...
]
sbonazzo commented on OVIRT-1918:
I'm not sure that the bisection really works then, since we have still
packages released 2 months ago not yet landing on tested. I don't recall to
have seen any job triggered automatically after a change-queue-tester
failure doing bisection tests.
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 t ested 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)
_______________________________________________
Infra mailing list
Infra(a)ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra
6 years, 2 months
[JIRA] (OVIRT-1918) Single project tests in change-queue-tester
by sbonazzo (oVirt JIRA)
[ https://ovirt-jira.atlassian.net/browse/OVIRT-1918?page=com.atlassian.jir... ]
sbonazzo commented on OVIRT-1918:
---------------------------------
I'm not sure that the bisection really works then, since we have still packages released 2 months ago not yet landing on tested. I don't recall to have seen any job triggered automatically after a change-queue-tester failure doing bisection tests.
> 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)
6 years, 2 months
