Hi Jamo,

After looking at the execution logs I agree with Diego, for some reason tests 
devoted to Carbon are being executed in Boron scope.

Maybe a Releng issue ...

BR,

Ursicio 

-----Original Message-----
From: [email protected] 
[mailto:[email protected]] On Behalf Of Diego Jesus 
Granados Lopez
Sent: martes, 28 de marzo de 2017 10:29
To: Jamo Luhrsen <[email protected]>; [email protected]
Cc: Colin Dixon <[email protected]>
Subject: Re: [sfc-dev] SFC Boron-SR3 test failure checkoff

Hi, 

I checked the failing job and most (not sure if all, but probably) of the 
failing tests shouldn't be executing in boron checks. E.g. there are 4 tests 
consistently failing that shouldn't be executing in Boron (Service Path 
validation: added by me) they were merged to carbon only one month ago. 

Any chance the Jenkins job is misconfigured and using master branch instead of 
boron-something for running that jobs? I looked at the job config and it 
contains a "GERRIT_BRANCH" parameter set to "stable/boron", but as I said if it 
was being used, tests added to carbon only shouldn't be being run

BR,
Diego

-----Original Message-----
From: [email protected] 
[mailto:[email protected]] On Behalf Of Jamo Luhrsen
Sent: lunes, 27 de marzo de 2017 22:57
To: [email protected]
Cc: Colin Dixon <[email protected]>
Subject: Re: [sfc-dev] SFC Boron-SR3 test failure checkoff

SFC,

I took a look at one of your failing jobs from the tracking sheet and it does 
have seemingly consistent failures now. But, the same job back in the SR2 
timeframe was passing 100%. Maybe there is a regression?

job from SR2-ish:

https://logs.opendaylight.org/releng/jenkins092/sfc-csit-3node-rest-basic-all-boron/212/archives/log.html.gz


Thanks,
JamO

> tl;dr
> Your project has test failures in the Boron-SR3 distribution tests. 
> Please look at them and mark them as OKAY in the spreadsheet if 
> they're not blocking or start a conversation with us _now_ if they are.
>
>
> Full details:
> The SFC project has at least one test failure in the distribution test 
> from the proposed Boron-SR3 release here:
> https://wiki.opendaylight.org/view/Simultaneous_Release:Boron_Release_
> Plan#Boron_SR3_Download
>
> To find the test failures, go to the distribution test report link at 
> the page above or directly here:
> https://jenkins.opendaylight.org/releng/view/distribution/job/integrat
> ion-distribution-test-boron/173/
>
> Then look for yellow or red balls after tests that start with your 
> project's short name and click on the number to go to the actual run 
> that produced the failures.
>
> Please check to see if the failures are a blocking issue for releasing
> Boron-SR3 and if so, start the discussion and if not, update the 
> spreadsheet here with OK in front of the issues:
> https://docs.google.com/spreadsheets/d/1zImtd764e-hOgJAxoJKl85fxHCPu2a
> gLfqsBtf13zQY/edit#gid=1776065453
>
> Ideally, also follow up here or on this thread:
> https://lists.opendaylight.org/pipermail/release/2017-March/009712.htm
> l
>
> Cheers,
> --Colin
_______________________________________________
sfc-dev mailing list
[email protected]
https://lists.opendaylight.org/mailman/listinfo/sfc-dev
_______________________________________________
sfc-dev mailing list
[email protected]
https://lists.opendaylight.org/mailman/listinfo/sfc-dev
_______________________________________________
sfc-dev mailing list
[email protected]
https://lists.opendaylight.org/mailman/listinfo/sfc-dev

Reply via email to