[
https://ovirt-jira.atlassian.net/browse/OVIRT-2092?page=com.atlassian.jir...
]
Barak Korren commented on OVIRT-2092:
-------------------------------------
You linked to [
91900|https://gerrit.ovirt.org/#/c/91900/] in this ticket, but the patch
you actually re added according to the link you provided here is
[
91886|https://gerrit.ovirt.org/#/c/91886].
You can see that change had gone into testing here:
https://jenkins.ovirt.org/view/Change%20queue%20jobs/job/ovirt-4.2_change...
And that test finished successfully:
https://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/2282/
The success was reported here:
https://jenkins.ovirt.org/view/Change%20queue%20jobs/job/ovirt-4.2_change...
Which is why the queue became empty.
Non of this indicated any issue with standard enqueue. If you re-add a change by
re-running the "add" build on the main CQ job - standard-enqueue is not even a
part of the process.
standard-enqueue 4.2 not running
--------------------------------
Key: OVIRT-2092
URL:
https://ovirt-jira.atlassian.net/browse/OVIRT-2092
Project: oVirt - virtualization made easy
Issue Type: Bug
Reporter: Dafna Ron
Assignee: infra
Priority: Highest
Labels: ost_failures, ost_infra
I was looking to see if
https://gerrit.ovirt.org/#/c/91900/ fixed the issues on the dwh
alerts and I found that we re-added the change to cq this morning:
http://jenkins.ovirt.org/view/Change%20queue%20jobs/job/ovirt-4.2_change-...
but the tested is showing that it only ran once (yesterday):
http://jenkins.ovirt.org/view/Change%20queue%20jobs/job/ovirt-4.2_change-...
and "next test" job is showing empty queue:
http://jenkins.ovirt.org/view/Change%20queue%20jobs/job/ovirt-4.2_change-...
seems like there is an issue in:
http://jenkins.ovirt.org/view/Change%20queue%20jobs/job/standard-enqueue/...
--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100086)