OpenStack CI Loop for Xen-Libvirt

From Xen
Jump to: navigation, search

CI Loop

This article provides some information about, which is the front-end for the Xen Project OpenStack CI loop, which is a 3rd party OpenStack CI loop (3rd party because it is operated by the Xen Project, not the OpenStack Foundation). You can find more information about 3rd party OpenStack testing systems in the following articles

Information on how this CI loop is deployed can be found in this repo:

It follows instruction provide at third_party_ci.


Our baseline for testing is ...

Ubuntu Xenial Xerus 16.04 LTS. It comes with:

  • Xen 4.6
  • Libvirt 1.3.1
  • Linux 4.4

Usage Instructions

Our OpenStack CI loop interface is available at The CI loop is now integrated with OpenStack Gerrit, in voting mode (Group B). This means that functional testing provided by our CI loop does not gate commits, but advises patch authors and reviewers of results in gerrit.

Icon Ambox.png Note that the DNS is broken, but you can access the CI loop via and

The CI loop tests our baseline against each Nova OpenStack commit.


The most useful view to get an overview over test failures can be found at the Build History page.

Screenshot of the Dashboard

OpenStack review: Each build maps onto a changeset on The following figure shows how to map a test run on our CI loop to a specific OpenStack review.

Shows how you get from a test to an OpenStack review

Aborted builds: Sometimes, jobs are aborted. The main reason for aborted jobs is that the OpenStack CI loop run at the OpenStack Foundation (or another voting 3rd party CI loop) may have determined that a change breaks a test. In other words, it is not necessary to complete the test in this case. Aborted jobs are typically marked with a grey circle. Note that this is nothing to worry about

Checking up on Test Failures

Test failures can be caused by

The first thing to do is to check whether a failure has been caused by an OpenStack commit If that is the case, the OpenStack community will fix the issue and re-submit the changeset.

Shows a test failure against the OpenStack CI Loop hosted by the OpenStack Foundation

That is unless, the issue is specific to the Xen Project. In that case, there is an expectation that we help the committer investigate the issue. Note that you can also use to get a comparison which tests failures were Xen specific.

The figure below, shows how you can find the test reports and how you verify that an issue is Xen+Libvirt specific.

In this figure you see that the change was verified on the CI Loop hosted by the OpenStack Foundation. The figure also shows you how you get to the test reports.

The figure below, shows you how you get to the libvirt and libxl libvirt driver log files, which you will need to investigate and reproduce an issue.

In this figure you see how you get to the libvirt and libxl libvirt driver log files.

Scripts to investigate issues

A simple couple of bash lines to download the full console logs from the jobs and create a histogram of tempest tests caused the majority of the failures:

# for i in {1106..1374}; do wget${i}/consoleFull -O ${i}_console; done
# grep -h "\.\.\. FAIL" * | sed -e 's/.*\(tempest[^) ]*\).*/\1/' | sort | uniq -c | sort -n
Note that the
in {<start test-run>..<end test-run>}
portion of the script needs to be adjusted to the start and end test run.

Community Activities

Training Session (week of May 4th)

We are planning a training session the week of May 4th or the week after, For more details see here. This will also include a discussion on how to integrate the CI loop into the project's workflow.

Meeting Minutes