[openstack-dev] [neutron] [third-party] Some third party results are not showing up in the CI summary on Gerrit

Dane Leblanc (leblancd) leblancd at cisco.com
Thu Aug 21 15:52:11 UTC 2014

If you look at review page for any of our Neutron commits, e.g.:
You'll see that there is a handy summary of CI results (with links to logs) in the upper right. However, there are some CIs which are missing from this summary, although we know that they had left a review comment or voted +1/-1 because they're listed in the Reviewer list on the left.

Note that there is an indirect way to find the logs for these CIs, by clicking on <Toggle CI> at the very bottom and scrolling through the results.

Henry Gessau checked with the openstack-infra team for clarification, and the explanation he got was that the Gerrit review page will only be able to include summaries for the CIs which leave review comments in the same format that the community Jenkins CI uses.

Here's an example of the Jenkins format (for illustration, hyperlinks and tabs are lost here in text mode):

Jenkins		Aug 20 6:52 PM

Patch Set 9: Verified+1

Build succeeded.

    gate-neutron-pep8 SUCCESS in 5m 36s
    gate-neutron-docs SUCCESS in 3m 46s
    gate-neutron-python26 SUCCESS in 37m 37s
    gate-neutron-python27 SUCCESS in 29m 26s
    check-tempest-dsvm-neutron-heat-slow SUCCESS in 26m 40s
    check-tempest-dsvm-neutron-pg SUCCESS in 1h 04m 55s
    check-tempest-dsvm-neutron-full SUCCESS in 1h 03m 18s
    check-tempest-dsvm-neutron-pg-full FAILURE in 1h 11m 01s (non-voting)
    gate-tempest-dsvm-neutron-large-ops SUCCESS in 25m 11s
    check-grenade-dsvm-neutron FAILURE in 32m 38s (non-voting)
    check-neutron-dsvm-functional SUCCESS in 21m 20s
    gate-rally-dsvm-neutron-neutron SUCCESS in 19m 31s (non-voting)
    check-tempest-dsvm-neutron-pg-2 SUCCESS in 1h 00m 40s
    check-tempest-dsvm-neutron-full-2 SUCCESS in 55m 28s
    check-tempest-dsvm-neutron-pg-full-2 FAILURE in 1h 05m 17s (non-voting)

For CIs which use a Zuul front end, this format comes automatic. But for others, the format of review comments may need some changes in order to match the Jenkins review comment format.

I don't think this is critical, but it would be nice to have everything summarized consistently.


More information about the OpenStack-dev mailing list