On Tue, Aug 14, 2012 at 01:43:06AM -0400, 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.

Thanks Robert, for this great improvement.

However, it seems to me that the script is pulling the wrong git hash.
For example, my patch http://gerrit.ovirt.org/#/c/7097/ with git has
539ccfbf02f0ca9605149885ae6b3e6feb4f1976 reports of success. However the
console output
http://jenkins.ovirt.info/job/patch_vdsm_unit_tests/417/console
show that the git hash that was actually built was
8af050b205994746198e5fb257652cd2fb8bfbc1 (vdsm/master)

Something is fishy here, and I may be getting false positive results.

Regards,
Dan.
_______________________________________________
vdsm-devel mailing list
vdsm-devel@lists.fedorahosted.org
https://lists.fedorahosted.org/mailman/listinfo/vdsm-devel

Reply via email to