oVirt infra daily report - unstable production jobs - 354
by jenkins@jenkins.phx.ovirt.org
------=_Part_448_1958926703.1497567601423
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Good morning!
Attached is the HTML page with the jenkins status report. You can see it also here:
- http://jenkins.ovirt.org/job/system_jenkins-report/354//artifact/exported...
Cheers,
Jenkins
------=_Part_448_1958926703.1497567601423
Content-Type: text/html; charset=us-ascii; name=upstream_report.html
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment; filename=upstream_report.html
Content-ID: <upstream_report.html>
<!DOCTYPE html><head><style type="text/css">
table.gridtable {
border-collapse: collapse;
table-layout:fixed;
width:1600px;
font-family: monospace;
font-size:13px;
}
.head {
font-size:20px;
font-family: arial;
}
.sub {
font-size:18px;
background-color:#e5e5e5;
font-family: arial;
}
pre {
font-family: monospace;
display: inline;
white-space: pre-wrap;
white-space: -moz-pre-wrap !important;
white-space: -pre-wrap;
white-space: -o-pre-wrap;
word-wrap: break-word;
}
</style>
</head>
<body>
<table class="gridtable" border=2>
<tr><th colspan=2 class=head>
RHEVM CI Jenkins Daily Report - 15/06/2017
</th></tr><tr><th colspan=2 class=sub>
<font color="blue"><a href="http://jenkins.ovirt.org/">00 Unstable Critical</a></font>
</th></tr>
<tr><td>
<a href="http://jenkins.ovirt.org/job/ovirt_4.1_image-ng-system-tests/">ovirt_4.1_image-ng-system-tests</a>
</td><td>
This job is automatically updated by jenkins job builder, any manual
change will be lost in the next update. If you want to make permanent
changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;h...">
jenkins</a> repo.
<!-- Managed by Jenkins Job Builder -->
</td></tr>
<tr><td>
<a href="http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_master/">test-repo_ovirt_experimental_master</a>
</td><td>
This job is automatically updated by jenkins job builder, any manual
change will be lost in the next update. If you want to make permanent
changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;h...">
jenkins</a> repo.
<!-- Managed by Jenkins Job Builder -->
</td></tr>
------=_Part_448_1958926703.1497567601423--
7 years, 5 months
[JIRA] (OVIRT-1449) Add upgrade suits to change-queue tests
by Barak Korren (oVirt JIRA)
Barak Korren created OVIRT-1449:
-----------------------------------
Summary: Add upgrade suits to change-queue tests
Key: OVIRT-1449
URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1449
Project: oVirt - virtualization made easy
Issue Type: Improvement
Components: oVirt CI
Reporter: Barak Korren
Assignee: infra
The change queue tester jobs currently only run the basic suits.
We need to add the upgrade suits as, but need to ensure we have enough hardware first, or alternatively disable 'experimental'.
--
This message was sent by Atlassian JIRA
(v1000.1065.1#100048)
7 years, 5 months
[JIRA] (OVIRT-1448) Enable devs to specifiy patch dependencies for OST
by Barak Korren (oVirt JIRA)
[ https://ovirt-jira.atlassian.net/browse/OVIRT-1448?page=com.atlassian.jir... ]
Barak Korren updated OVIRT-1448:
--------------------------------
Description:
We have an issue with our system ATM where if there are patches for different projects that depend on one another, the system is unaware of that dependency.
What typically happens in this scenario is that sending the dependent patch makes the experimental test fail and keep failing until the other patch is also merged.
The change queue will handle this better, but the typical behaviour for it would be to reject both patches, unless they are somehow coordinated to make it into the same test.
The change queue core code already includes the ability to track and understand dependencies between changes. What is missing is the ability for developers to specify theses dependencies.
We would probably want to adopt OpenStack's convention here.
> Enable devs to specifiy patch dependencies for OST
> --------------------------------------------------
>
> Key: OVIRT-1448
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1448
> Project: oVirt - virtualization made easy
> Issue Type: Improvement
> Components: oVirt CI
> Reporter: Barak Korren
> Assignee: infra
> Labels: change-queue
>
> We have an issue with our system ATM where if there are patches for different projects that depend on one another, the system is unaware of that dependency.
> What typically happens in this scenario is that sending the dependent patch makes the experimental test fail and keep failing until the other patch is also merged.
> The change queue will handle this better, but the typical behaviour for it would be to reject both patches, unless they are somehow coordinated to make it into the same test.
> The change queue core code already includes the ability to track and understand dependencies between changes. What is missing is the ability for developers to specify theses dependencies.
> We would probably want to adopt OpenStack's convention here.
--
This message was sent by Atlassian JIRA
(v1000.1065.1#100048)
7 years, 5 months