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 Middleswarth @rmiddle (twitter/IRC)
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 ? If yes, why did the build abort for my latest patch ?
On 08/14/2012 12:52 PM, 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 ? If yes, why did the build abort for my latest patch ?
Pls see http://gerrit.ovirt.org/#/c/6856/ For patch1 it says build success, for patch 2, it says aborted.. why ?
----- Original Message -----
From: "Deepak C Shetty" <deepakcs@linux.vnet.ibm.com> To: "Deepak C Shetty" <deepakcs@linux.vnet.ibm.com> Cc: engine-devel@ovirt.org, "arch" <arch@ovirt.org>, "VDSM Project Development" <vdsm-devel@lists.fedorahosted.org>, "infra" <infra@ovirt.org> Sent: Tuesday, August 14, 2012 11:54:31 AM Subject: Re: [Engine-devel] [vdsm] Jenkins testing.
On 08/14/2012 12:52 PM, 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 ? If yes, why did the build abort for my latest patch ?
Pls see http://gerrit.ovirt.org/#/c/6856/ For patch1 it says build success, for patch 2, it says aborted.. why ?
it's because your email address wasn't in the jenkins-whitelist.txt file. this file includes emails address for users that jenkins will allow running test jobs on thier patches. this was introduced as a way for defending the jenkins from malicious users that might send harmful patches to jenkins. i've added you to the whitelist, you should be ok now. the list was generated automaticly from git log, so it still might missing known people, if anyone sees this aborted msg in the gerrit, please contact infra team so he can be added to the whitelist. Eyal.
_______________________________________________ Engine-devel mailing list Engine-devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/engine-devel
On Tue, Aug 14, 2012 at 06:20:11AM -0400, Eyal Edri wrote:
Deepak C Shetty wrote:
On 08/14/2012 12:52 PM, 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 ? If yes, why did the build abort for my latest patch ?
Pls see http://gerrit.ovirt.org/#/c/6856/ For patch1 it says build success, for patch 2, it says aborted.. why ?
it's because your email address wasn't in the jenkins-whitelist.txt file. this file includes emails address for users that jenkins will allow running test jobs on thier patches. this was introduced as a way for defending the jenkins from malicious users that might send harmful patches to jenkins.
i've added you to the whitelist, you should be ok now.
the list was generated automaticly from git log, so it still might missing known people, if anyone sees this aborted msg in the gerrit, please contact infra team so he can be added to the whitelist.
Note that the whitelist is in the jenkins-whitelist repo so see http://gerrit.ovirt.org/gitweb?p=jenkins-whitelist.git and http://gerrit.ovirt.org/#/q/project:jenkins-whitelist,n,z for more details.
On 08/14/2012 04:54 AM, Deepak C Shetty wrote:
On 08/14/2012 12:52 PM, 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 ? If yes, why did the build abort for my latest patch ?
Pls see http://gerrit.ovirt.org/#/c/6856/ For patch1 it says build success, for patch 2, it says aborted.. why ?
All the abort means as a protective measure we don't run the tests unless we know the committer. With that said you are now in the whitelist so it shouldn't be an issue in the feature. -- Thanks Robert Middleswarth @rmiddle (twitter/Freenode IRC) @RobertM (OFTC IRC)
On 08/22/2012 07:40 AM, Robert Middleswarth wrote:
On 08/14/2012 04:54 AM, Deepak C Shetty wrote:
On 08/14/2012 12:52 PM, 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 ? If yes, why did the build abort for my latest patch ?
Pls see http://gerrit.ovirt.org/#/c/6856/ For patch1 it says build success, for patch 2, it says aborted.. why ?
All the abort means as a protective measure we don't run the tests unless we know the committer. With that said you are now in the whitelist so it shouldn't be an issue in the feature.
Thanks for putting me in the whitelist. But it still doesn't clarify how patch 1 got build success and subsequent patch 2 had abort ?
On 08/22/2012 12:03 AM, Deepak C Shetty wrote:
On 08/22/2012 07:40 AM, Robert Middleswarth wrote:
On 08/14/2012 04:54 AM, Deepak C Shetty wrote:
On 08/14/2012 12:52 PM, 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 ? If yes, why did the build abort for my latest patch ?
Pls see http://gerrit.ovirt.org/#/c/6856/ For patch1 it says build success, for patch 2, it says aborted.. why ?
All the abort means as a protective measure we don't run the tests unless we know the committer. With that said you are now in the whitelist so it shouldn't be an issue in the feature.
Thanks for putting me in the whitelist. But it still doesn't clarify how patch 1 got build success and subsequent patch 2 had abort ?
Patch 1 happened in the small window well I was testing before the whitelist went live. Patch 2 happened after the whitelist went live. Since you are now in the whitelist all new patches for you will run. -- Thanks Robert Middleswarth @rmiddle (twitter/Freenode IRC) @RobertM (OFTC IRC)
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-whit...
If yes, why did the build abort for my latest patch ?
_______________________________________________ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra
Great job! I know it required a great effort and time to make this work so kudos for making it happen. Eyal. ----- Original Message -----
From: "Robert Middleswarth" <robert@middleswarth.net> To: "infra" <infra@ovirt.org>, engine-devel@ovirt.org, "VDSM Project Development" <vdsm-devel@lists.fedorahosted.org>, "arch" <arch@ovirt.org> Sent: Tuesday, August 14, 2012 8:43:06 AM Subject: Jenkins testing.
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 Middleswarth @rmiddle (twitter/IRC)
_______________________________________________ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra
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.
participants (6)
-
Dan Kenigsberg -
Deepak C Shetty -
Ewoud Kohl van Wijngaarden -
Eyal Edri -
Itamar Heim -
Robert Middleswarth