CAPWAP Beryllium SR4 Distribution Test Failures
|
an.ho@huawei.com
Hi CAPWAP Team,
There are some distribution test failures in Beryllium SR4 Build 20161017 related to your project. Could you or someone from your team please take a moment to mark these issues in the spreadsheet [1] as "OKAY" to release or "BLOCKING" and requires a respin of Beryllium SR4.
https://jenkins.opendaylight.org/releng/job/capwap-csit-1node-ac-only-beryllium/950/ https://jenkins.opendaylight.org/releng/job/capwap-csit-1node-ac-all-beryllium/1050/
Best Regards, An Ho
|
|
|
|
an.ho@huawei.com
Hi JamO,
Looking at these test failures, it seems the same as the issues from the previous Beryllium SR3. In fact, the tests have not passed since September. Based on my analysis, I believe the issues are known problem with the tests. I will update the spreadsheet as “OKAY” to release.
Abi Varghese and the CAPWAP Team, please feel free to raise a BLOCKER bug and let us know if you have any objections or concerns with this assessment.
Best Regards, An Ho
From: An Ho
Hi CAPWAP Team,
There are some distribution test failures in Beryllium SR4 Build 20161017 related to your project. Could you or someone from your team please take a moment to mark these issues in the spreadsheet [1] as "OKAY" to release or "BLOCKING" and requires a respin of Beryllium SR4.
https://jenkins.opendaylight.org/releng/job/capwap-csit-1node-ac-only-beryllium/950/ https://jenkins.opendaylight.org/releng/job/capwap-csit-1node-ac-all-beryllium/1050/
Best Regards, An Ho
|
|
|
|
Jamo Luhrsen <jluhrsen@...>
ok An.
toggle quoted messageShow quoted text
it does look like CAPWAP has broken CSIT. They are using a python library from robot and it's not giving any debug output. Nothing in the karaf.log either than I can tell. JamO
On 10/19/2016 09:40 AM, An Ho wrote:
Hi JamO,
|
|
|