[oVirt Jenkins] ovirt-appliance_ovirt-4.1-pre_build-artifacts-el7-x86_64 - Build # 98 - Failure!
by jenkins＠jenkins.phx.ovirt.org
------=_Part_278_1370906505.1504775580516
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Project: http://jenkins.ovirt.org/job/ovirt-appliance_ovirt-4.1-pre_build-artifact...
Build: http://jenkins.ovirt.org/job/ovirt-appliance_ovirt-4.1-pre_build-artifact...
Build Number: 98
Build Status: Failure
Triggered By: Started by user Lev Veyde
-------------------------------------
Changes Since Last Success:
-------------------------------------
Changes for Build #98
[Eyal Edri] Add Eitan Raviv to whitelist
[Daniel Belenky] Run infra-docs_check-patch and check-merged on el7
[Daniel Belenky] try to build container if related files were changed
[Gil Shinar] Suppress git ls-remote output to stderr
[Yuval Turgeman] Add 4.2 jobs for imgbased, node-ng and appliance
[Daniel Belenky] Fix bugs in mock_runner secrets binding
[Daniel Belenky] Prevent post merge Jobs from voting in Gerrit
[Gil Shinar] suppress git fetch output in upstream source collector
[Daniel Belenky] Add env inject to ost template
[Daniel Belenky] Move gerrit-trigger-ci-label inject to be first
[Sandro Bonazzola] ovirt-release: add 4.2 branch
[Daniel Belenky] Fix race condition in docker cleanup
[Barak Korren] Remove old ovirt-ansible jobs
[Barak Korren] Added pipeline-std-ci jobs for GitHub PRs
[Barak Korren] Add support for building on demand from GitHub PRs
[Sandro Bonazzola] cockpit-ovirt: add 4.2 branch
[Ryan Barry] engine-appliance: make swap partition first
-----------------
Failed Tests:
-----------------
No tests ran.
------=_Part_278_1370906505.1504775580516--
7 years, 3 months
[JIRA] (OVIRT-1639) Get a solution to the CI Gerrit vote "race condition"
by Barak Korren (oVirt JIRA)
This is a multi-part message in MIME format...
------------=_1504768061-20929-206
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
[ https://ovirt-jira.atlassian.net/browse/OVIRT-1639?page=com.atlassian.jir... ]
Barak Korren reassigned OVIRT-1639:
-----------------------------------
Assignee: Barak Korren (was: infra)
> Get a solution to the CI Gerrit vote "race condition"
> -----------------------------------------------------
>
> Key: OVIRT-1639
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1639
> Project: oVirt - virtualization made easy
> Issue Type: Improvement
> Components: oVirt CI
> Reporter: Barak Korren
> Assignee: Barak Korren
> Labels: gerrit, jenkins
>
> We have a certain scenario that repeats itself in our system:
> # Developer sends a patch
> # CI jobs start running
> # Developer send a new patch-set with a trivial change (e.g. commit message fix)
> # CI jobs complete and send results to Gerrit
> # Gerrit ignores the Jenkins vote because it was made on the older patch-set.
> # No vote is made by Jenkins on the new patch-set because it is configured to nor run jobs on trivial patches.
> We've seen developers encounter this many times. I suspect this because even more frequent recently because PolyGerrit provides a UI for quickly editing commit messages.
> We need to open tickets to the Gerrit developers and the Gerrit Trigger Plugin authors and see of they will be willing to help with this.
--
This message was sent by Atlassian {0}
(v1001.0.0-SNAPSHOT#100059)
------------=_1504768061-20929-206
Content-Type: text/html; charset="UTF-8"
Content-Disposition: inline
Content-Transfer-Encoding: 7bit
<html><body>
<pre>[ https://ovirt-jira.atlassian.net/browse/OVIRT-1639?page=com.atlassian.jir... ]</pre>
<h3>Barak Korren reassigned OVIRT-1639:</h3>
<pre>Assignee: Barak Korren (was: infra)</pre>
<blockquote><h3>Get a solution to the CI Gerrit vote “race condition”</h3>
<pre> Key: OVIRT-1639
URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1639
Project: oVirt - virtualization made easy
Issue Type: Improvement
Components: oVirt CI
Reporter: Barak Korren
Assignee: Barak Korren
Labels: gerrit, jenkins</pre>
<p>We have a certain scenario that repeats itself in our system: # Developer sends a patch # CI jobs start running # Developer send a new patch-set with a trivial change (e.g. commit message fix) # CI jobs complete and send results to Gerrit # Gerrit ignores the Jenkins vote because it was made on the older patch-set. # No vote is made by Jenkins on the new patch-set because it is configured to nor run jobs on trivial patches. We've seen developers encounter this many times. I suspect this because even more frequent recently because PolyGerrit provides a UI for quickly editing commit messages. We need to open tickets to the Gerrit developers and the Gerrit Trigger Plugin authors and see of they will be willing to help with this.</p></blockquote>
<p>— This message was sent by Atlassian {0} (v1001.0.0-SNAPSHOT#100059)</p>
<img src="https://u4043402.ct.sendgrid.net/wf/open?upn=i5TMWGV99amJbNxJpSp2-2BCmpYL..." 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>
------------=_1504768061-20929-206--
7 years, 3 months
[JIRA] (OVIRT-1639) Get a solution to the CI Gerrit vote "race condition"
by Barak Korren (oVirt JIRA)
This is a multi-part message in MIME format...
------------=_1504768055-26486-254
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Barak Korren created OVIRT-1639:
-----------------------------------
Summary: Get a solution to the CI Gerrit vote "race condition"
Key: OVIRT-1639
URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1639
Project: oVirt - virtualization made easy
Issue Type: Improvement
Components: oVirt CI
Reporter: Barak Korren
Assignee: infra
We have a certain scenario that repeats itself in our system:
# Developer sends a patch
# CI jobs start running
# Developer send a new patch-set with a trivial change (e.g. commit message fix)
# CI jobs complete and send results to Gerrit
# Gerrit ignores the Jenkins vote because it was made on the older patch-set.
# No vote is made by Jenkins on the new patch-set because it is configured to nor run jobs on trivial patches.
We've seen developers encounter this many times. I suspect this because even more frequent recently because PolyGerrit provides a UI for quickly editing commit messages.
We need to open tickets to the Gerrit developers and the Gerrit Trigger Plugin authors and see of they will be willing to help with this.
--
This message was sent by Atlassian {0}
(v1001.0.0-SNAPSHOT#100059)
------------=_1504768055-26486-254
Content-Type: text/html; charset="UTF-8"
Content-Disposition: inline
Content-Transfer-Encoding: 7bit
<html><body>
<h3>Barak Korren created OVIRT-1639:</h3>
<pre> Summary: Get a solution to the CI Gerrit vote "race condition"
Key: OVIRT-1639
URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1639
Project: oVirt - virtualization made easy
Issue Type: Improvement
Components: oVirt CI
Reporter: Barak Korren
Assignee: infra</pre>
<p>We have a certain scenario that repeats itself in our system: # Developer sends a patch # CI jobs start running # Developer send a new patch-set with a trivial change (e.g. commit message fix) # CI jobs complete and send results to Gerrit # Gerrit ignores the Jenkins vote because it was made on the older patch-set. # No vote is made by Jenkins on the new patch-set because it is configured to nor run jobs on trivial patches.</p>
<p>We've seen developers encounter this many times. I suspect this because even more frequent recently because PolyGerrit provides a UI for quickly editing commit messages.</p>
<p>We need to open tickets to the Gerrit developers and the Gerrit Trigger Plugin authors and see of they will be willing to help with this.</p>
<p>— This message was sent by Atlassian {0} (v1001.0.0-SNAPSHOT#100059)</p>
<img src="https://u4043402.ct.sendgrid.net/wf/open?upn=i5TMWGV99amJbNxJpSp2-2BCmpYL..." 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>
------------=_1504768055-26486-254--
7 years, 3 months
[JIRA] (OVIRT-1639) Get a solution to the CI Gerrit vote "race condition"
by Barak Korren (oVirt JIRA)
This is a multi-part message in MIME format...
------------=_1504768054-18385-248
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
[ https://ovirt-jira.atlassian.net/browse/OVIRT-1639?page=com.atlassian.jir... ]
Barak Korren updated OVIRT-1639:
--------------------------------
Epic Link: OVIRT-400
> Get a solution to the CI Gerrit vote "race condition"
> -----------------------------------------------------
>
> Key: OVIRT-1639
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1639
> Project: oVirt - virtualization made easy
> Issue Type: Improvement
> Components: oVirt CI
> Reporter: Barak Korren
> Assignee: infra
> Labels: gerrit, jenkins
>
> We have a certain scenario that repeats itself in our system:
> # Developer sends a patch
> # CI jobs start running
> # Developer send a new patch-set with a trivial change (e.g. commit message fix)
> # CI jobs complete and send results to Gerrit
> # Gerrit ignores the Jenkins vote because it was made on the older patch-set.
> # No vote is made by Jenkins on the new patch-set because it is configured to nor run jobs on trivial patches.
> We've seen developers encounter this many times. I suspect this because even more frequent recently because PolyGerrit provides a UI for quickly editing commit messages.
> We need to open tickets to the Gerrit developers and the Gerrit Trigger Plugin authors and see of they will be willing to help with this.
--
This message was sent by Atlassian {0}
(v1001.0.0-SNAPSHOT#100059)
------------=_1504768054-18385-248
Content-Type: text/html; charset="UTF-8"
Content-Disposition: inline
Content-Transfer-Encoding: 7bit
<html><body>
<pre>[ https://ovirt-jira.atlassian.net/browse/OVIRT-1639?page=com.atlassian.jir... ]</pre>
<h3>Barak Korren updated OVIRT-1639:</h3>
<pre>Epic Link: OVIRT-400</pre>
<blockquote><h3>Get a solution to the CI Gerrit vote “race condition”</h3>
<pre> Key: OVIRT-1639
URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1639
Project: oVirt - virtualization made easy
Issue Type: Improvement
Components: oVirt CI
Reporter: Barak Korren
Assignee: infra
Labels: gerrit, jenkins</pre>
<p>We have a certain scenario that repeats itself in our system: # Developer sends a patch # CI jobs start running # Developer send a new patch-set with a trivial change (e.g. commit message fix) # CI jobs complete and send results to Gerrit # Gerrit ignores the Jenkins vote because it was made on the older patch-set. # No vote is made by Jenkins on the new patch-set because it is configured to nor run jobs on trivial patches. We've seen developers encounter this many times. I suspect this because even more frequent recently because PolyGerrit provides a UI for quickly editing commit messages. We need to open tickets to the Gerrit developers and the Gerrit Trigger Plugin authors and see of they will be willing to help with this.</p></blockquote>
<p>— This message was sent by Atlassian {0} (v1001.0.0-SNAPSHOT#100059)</p>
<img src="https://u4043402.ct.sendgrid.net/wf/open?upn=i5TMWGV99amJbNxJpSp2-2BCmpYL..." 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>
------------=_1504768054-18385-248--
7 years, 3 months
[JIRA] (OVIRT-1638) Make CQ keep artifacts longer
by Barak Korren (oVirt JIRA)
This is a multi-part message in MIME format...
------------=_1504767557-15801-227
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
[ https://ovirt-jira.atlassian.net/browse/OVIRT-1638?page=com.atlassian.jir... ]
Barak Korren reassigned OVIRT-1638:
-----------------------------------
Assignee: Barak Korren (was: infra)
> Make CQ keep artifacts longer
> -----------------------------
>
> Key: OVIRT-1638
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1638
> Project: oVirt - virtualization made easy
> Issue Type: Improvement
> Components: oVirt CI
> Reporter: Barak Korren
> Assignee: Barak Korren
> Labels: change-queue
>
> The change queue currently keeps a history of up to 100 builds. This seems not to be enough. Instead, we need to keep 10 days of builds like we do for stdci jobs.
--
This message was sent by Atlassian {0}
(v1001.0.0-SNAPSHOT#100059)
------------=_1504767557-15801-227
Content-Type: text/html; charset="UTF-8"
Content-Disposition: inline
Content-Transfer-Encoding: 7bit
<html><body>
<pre>[ https://ovirt-jira.atlassian.net/browse/OVIRT-1638?page=com.atlassian.jir... ]</pre>
<h3>Barak Korren reassigned OVIRT-1638:</h3>
<pre>Assignee: Barak Korren (was: infra)</pre>
<blockquote><h3>Make CQ keep artifacts longer</h3>
<pre> Key: OVIRT-1638
URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1638
Project: oVirt - virtualization made easy
Issue Type: Improvement
Components: oVirt CI
Reporter: Barak Korren
Assignee: Barak Korren
Labels: change-queue</pre>
<p>The change queue currently keeps a history of up to 100 builds. This seems not to be enough. Instead, we need to keep 10 days of builds like we do for stdci jobs.</p></blockquote>
<p>— This message was sent by Atlassian {0} (v1001.0.0-SNAPSHOT#100059)</p>
<img src="https://u4043402.ct.sendgrid.net/wf/open?upn=i5TMWGV99amJbNxJpSp2-2BCmpYL..." 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>
------------=_1504767557-15801-227--
7 years, 3 months
[JIRA] (OVIRT-1638) Make CQ keep artifacts longer
by Barak Korren (oVirt JIRA)
This is a multi-part message in MIME format...
------------=_1504767547-18274-149
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Barak Korren created OVIRT-1638:
-----------------------------------
Summary: Make CQ keep artifacts longer
Key: OVIRT-1638
URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1638
Project: oVirt - virtualization made easy
Issue Type: Improvement
Components: oVirt CI
Reporter: Barak Korren
Assignee: infra
The change queue currently keeps a history of up to 100 builds. This seems not to be enough. Instead, we need to keep 10 days of builds like we do for stdci jobs.
--
This message was sent by Atlassian {0}
(v1001.0.0-SNAPSHOT#100059)
------------=_1504767547-18274-149
Content-Type: text/html; charset="UTF-8"
Content-Disposition: inline
Content-Transfer-Encoding: 7bit
<html><body>
<h3>Barak Korren created OVIRT-1638:</h3>
<pre> Summary: Make CQ keep artifacts longer
Key: OVIRT-1638
URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1638
Project: oVirt - virtualization made easy
Issue Type: Improvement
Components: oVirt CI
Reporter: Barak Korren
Assignee: infra</pre>
<p>The change queue currently keeps a history of up to 100 builds. This seems not to be enough. Instead, we need to keep 10 days of builds like we do for stdci jobs.</p>
<p>— This message was sent by Atlassian {0} (v1001.0.0-SNAPSHOT#100059)</p>
<img src="https://u4043402.ct.sendgrid.net/wf/open?upn=i5TMWGV99amJbNxJpSp2-2BCmpYL..." 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>
------------=_1504767547-18274-149--
7 years, 3 months
