https://jira.opendaylight.org This file is an XML representation of an issue en-us 8.20.10 820010 22-06-2022 https://jira.opendaylight.org/browse/SFC-193 sfc <p>NullPointerException randomly raised during unit test execution for sfc-openflow-utils. Caracteristic stack: </p> <p>20:58:48 java.lang.NullPointerException<br/> 20:58:48 at junitparams.internal.ParameterisedTestMethodRunner.findChildForParams(ParameterisedTestMethodRunner.java:66)<br/> 20:58:48 at junitparams.internal.ParameterisedTestMethodRunner.runTestMethod(ParameterisedTestMethodRunner.java:40)<br/> 20:58:48 at junitparams.internal.ParameterisedTestClassRunner.runParameterisedTest(ParameterisedTestClassRunner.java:143)<br/> 20:58:48 at junitparams.JUnitParamsRunner.runChild(JUnitParamsRunner.java:393)</p> <p>Operating System: All<br/> Platform: All</p> SFC-193

Random NPE on SfcOpenflowUtilsTest unit test execution

Bug Verified Cannot Reproduce Diego Granados Diego Granados Thu, 4 May 2017 07:08:21 +0000 Tue, 29 May 2018 18:21:14 +0000 Tue, 29 May 2018 18:21:08 +0000 unspecified Carbon General 0 0 <p>Error is triggered when the randomly generated input for test shouldThrowExceptionForCreateSetAction contains certain characters in the unicode private or unassigned ranges. </p> <p>That input is generated randomly in method createActionSetDlBadParams; when using a test input generator, junit class ParameterisedTestMethod runner is used. In that class, a combination of test input + method name is stored (as String) in Description objects; the problem is that Description uses a regular expression for later separating test input / method name candidates which fails when test input contains certain unicode chars. </p> <p>The expression used for extracting test input (first matched group is taken as test input): </p> <p>private static final Pattern METHOD_AND_CLASS_NAME_PATTERN = Pattern<br/> .compile("(.<b>)\\((.</b>)<br class="atl-forced-newline" />)");</p> <p>Problem is that this pattern fails when certain unicode chars in the private / unassigned range are present. Sanitizing test input to remove those chars solves the problem.</p> <p>This test case is no longer failing.</p> Development External issue ID 8367 External issue URL Rank 0|i02fmn: