Both are classified as non-critical (as per the test case) - but Luis can
answer better. First one is a create JVM plot fail (so should not be
critical) but has a message that will need to be reviewed (including
whether that particular test should be just rerun):
ConnectionError: ConnectionError(('Connection aborted.', error(111,
'Connection refused'))) caused by: ProtocolError(('Connection aborted.',
error(111, 'Connection refused')))
The second looks harmless I think - as it is just missing the word RESULT
but does show the results in flows/sec.
'10:16:57.487 8 switches: flows/sec: 85854 92914 81796 0 82911 84662 0
89093 total = 43.102496 per ms ' does not contain 'RESULT'
On Tue, Jul 26, 2016 at 9:52 AM, An Ho <an...@huawei.com> wrote:
> Hi OPENFLOWPLUGIN Team,
>
> There are some distribution test failures in Beryllium SR3 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 and delay of Beryllium SR3.
>
>
> https://jenkins.opendaylight.org/releng/job/openflowplugin-csit-1node-scalability-lithium-redesign-only-beryllium/966/
>
> https://jenkins.opendaylight.org/releng/job/openflowplugin-csit-1node-cbench-performance-only-beryllium/1616/
>
> Best Regards,
> An Ho
>
> [1]
> https://docs.google.com/spreadsheets/d/1hci5TMUPyB6PX8Al-fwfVqvs5SQVa2wZLja_7rKWN6o/edit#gid=1820514274
> [2]
> https://wiki.opendaylight.org/view/Simultaneous_Release:Beryllium_Release_Plan#Beryllium_SR3_Download
>
>
_______________________________________________
openflowplugin-dev mailing list
openflowplugin-dev@lists.opendaylight.org
https://lists.opendaylight.org/mailman/listinfo/openflowplugin-dev
