[openstack-dev] [Neutron][3rd Party Testing]Remove voting until your testing structure works.

Anita Kuno anteaya at anteaya.info
Tue Dec 31 02:32:42 UTC 2013


When your third party testing structure votes on patches and your
testing structure is not stable, it will vote with a -1 on patches.

This results in three consequences:
1. The patch it votes on starts a countdown for abandonment, this is
frustrating for developers.
2. Reviewers who use -Verified-1 as a filter criteria will not review a
patch with a -1 in the verification column in the Gerrit dashboard. This
prevents developers from progressing in their work, and this also
prevents reviewers from reviewing patches that need to be assessed.
3. Third party testing that does not provide publicly accessible logs
leave developers with no way to diagnose the issue, which makes it very
difficult for a developer to fix, leaving the patch in a state of limbo.

You can post messages to the patches, including a stable working url to
the logs for your tests, as you continue to work on your third party tests.

You are also welcome to post a success of failure message, just please
refrain from allowing your testing infrastructure to vote on patches
until your testing infrastructure is working, reliably, and has logs
that developers can use to fix problems.

The list of third party testing accounts are found here.[0]

Right now there are three plugins that need to remove voting until they
are stable.

Please be active in #openstack-neutron, #openstack-qa, and the mailing
list so that if there is an issue with your testing structure, people
can come and talk to you.

Thank you,


More information about the OpenStack-dev mailing list