Yes, skipped simply means for that particular job, it's result is not counted towards the vote decision for Jenkins. So if you have a 5 jobs trigger off of a patch but 2 jobs are configured to be skipped that means only the last 3 jobs that were none skipped's results will be used to decide whether or not to +1 or -1.
Of course for ODL's merge jobs voting is over so there is no votes to count but we had to add the skip vote setting due to the issue explained in the commit message of patch 47075. Thanh On Wed, Oct 19, 2016 at 8:44 AM, Lori Jakab <lorand.jakab+...@gmail.com> wrote: > Thanks Alexis! > > -Lori > > > On Wed, Oct 19, 2016 at 3:18 PM, Alexis de Talhouët < > adetalho...@inocybe.com> wrote: > >> Lori, >> >> This seems to be related to this patch: https://git.opendayligh >> t.org/gerrit/#/c/47075/ >> Explanation is on the commit message. >> >> Thanks, >> Alexis >> >> On Oct 19, 2016, at 2:08 AM, Lori Jakab <lorand.jakab+...@gmail.com> >> wrote: >> >> Hi, >> >> I observed that lately all merge jobs outcomes have "(skipped)" added, >> for example "SUCCESS (skipped)" or "UNSTABLE (skipped)". What exactly is >> skipped? Is this something that we have to worry about? >> >> Thanks, >> -Lori >> >>
_______________________________________________ infrastructure mailing list infrastructure@lists.opendaylight.org https://lists.opendaylight.org/mailman/listinfo/infrastructure
