Alright, this looks like a pccmock

Yeah, it's three test cases, all of them are PCEP-related. They are failing reliably, which seems to indicate a systemic problem. I'll try to see if I can debug/repro it tomorrow. We might punt to

It seems that we are still having Bgp and pcep issues but are they all critical ? Or can we fix them later so we can release phosphorus ?

Hi Robert: The jjb-merge job failed since a new branch is added and the CR changes a lots of job configs. This translates to updating all the job configs on Jenkins and requires more time to

it seems that the issue has been fixed by LF IT so are we good to pick up Phosphorus AR #216 integration #174 is showing some BGPCEP failed test

To explain: it is failing since Sep 21, hence Jenkins jobs do not reflect Gerrit branches mapping: - all -phosphorus jobs still refer to master branch - there are no -sulfur jobs Regards, Robert

It seems Jenkins/JJB integration is busted. I have filed https://jira.linuxfoundation.org/plugins/servlet/theme/portal/2/IT-22956 for that. Bye, Robert

It seems we have a few regressions in both BGP and PCEP. I suspect I know the culprit behind at least one of the failures, should have an updated bgpcep ready later today. Regards, Robert

Phosphorus AR#212 integration #169 has only one test case failed bgpcep https://jenkins.opendaylight.org/releng/job/bgpcep-csit-1node-userfeatures-all-phosphorus/167/ so looks to me like a good RC

I have retriggered the job, as the OVSDB/OFP test cases failed with: i.e. instance limits, again :( Bye, Robert

97467 is merged, so i guess i can pick AR #211, Integration #167. There are some CSIT failures

Yes, We need Luis or someone from the integration team to merge 97467, then we can pick up the subsequent AR build.

Thanks Anil. Robert, please correct me if I'm wrong, but we have to wait for [1] to be fixed before we can pick a RC [1] https://git.opendaylight.org/gerrit/c/integration/test/+/97467 Anil, i think

Hello all, Presently, all of our CI job logs are shipped and stored on AWS S3 bucket [1.] and on Nexus2 Log server [2.]. We have been shipping/storing logs on the AWS S3 bucket, since this was enabled

Hello all, The version bump is complete, the master branch is promoted to the next release (Sulfer) and the "stable/phosphorous" branch is created. The master branch is unlocked and is open for

Hello all, The master branch is locked for Phosphorus code freeze and branch cutting ("stable/phosphorus") and master branch will be promoted to next (Sulphur). Once the version bump and the release

Greetings, TransportPCE Silicon SR2 release is now complete. Thanks to everyone who has contributed to this release. Regards, Bala From: Daniel de la Rosa <ddelarosa0707@...> Date:

Hi Daniel You are right. No change was pushed for the download page update and there were another problem in the index. I just fixed these other remaining issues. Hope this helps BR Guillaume De :

Hello Guillaume and all I still don't see Silicon SR2 releases notes nor the downloads document being updated, anything else to be done? Thanks

Hello this new file was not referenced in the folder index, what explains the docs job failure with sphinx option "-W". Every warnings is treated by sphinx as a failure. This should be OK now. I just