[vdsm] Jenkins testing.
Itamar Heim
iheim at redhat.com
Tue Aug 21 07:22:49 UTC 2012
On 08/14/2012 10:22 AM, Deepak C Shetty wrote:
> On 08/14/2012 11:13 AM, Robert Middleswarth wrote:
>> After a few false starts it looks like we have per patch testing
>> working on VDSM, oVirt-engine, oVirt-engine-sdk and oVirt-engine-cli.
>> There are 3 status a patch can get. 1) Success - Means the patch ran
>> though the tests without issue. 2) Failure - Means the tests failed.
>> 3) Aborted - Generally means the submitter is not in the whitelist and
>> the tests were never run. If you have any questions please feel free
>> to ask.
>>
> So what is needed for the submitted to be in whitelist ?
> I once for Success for few of my patches.. then got failure for some
> other patch( maybe thats due to the false starts u had) and then for the
> latest patch of mine, it says aborted.
>
> So not sure if i am in whitelist or not ?
> If not, what do i need to do to be part of it ?
robert is adding these per failed jobs.
we track the whitelist as a git repo in gerrit:
http://gerrit.ovirt.org/gitweb?p=jenkins-whitelist.git;a=blob;f=jenkins-whitelist.txt
> If yes, why did the build abort for my latest patch ?
>
> _______________________________________________
> Infra mailing list
> Infra at ovirt.org
> http://lists.ovirt.org/mailman/listinfo/infra
More information about the Arch
mailing list