kofemann
commented
6 years ago this is correct as we test that gPlazma behaves correct if one of the plugings throws RuntimeException.
-kofemann /* caffeinated mutations of the core personality /
On Tue, Feb 27, 2018 at 2:23 PM, Jürgen Starek notifications@github.com wrote:
Recent Jenkins runs like https://ci.dcache.org/view/ dCache%204.0/job/dCache-v4.0/61/consoleFull yielded the following during gplazma testing:
ERROR o.d.g.strategies.PAMStyleStrategy - Bug in plugin: java.lang.RuntimeException: this is a bug at org.dcache.gplazma.strategies.AccountStrategyTests$Buggy.account(AccountStrategyTests.java:499) ~[test-classes/:na] at org.dcache.gplazma.strategies.DefaultAccountStrategy.lambda$account$0(DefaultAccountStrategy.java:65) [classes/:na] at org.dcache.gplazma.strategies.PAMStyleStrategy.callPlugins(PAMStyleStrategy.java:98) ~[classes/:na] at org.dcache.gplazma.strategies.DefaultAccountStrategy.account(DefaultAccountStrategy.java:57) [classes/:na] at org.dcache.gplazma.strategies.AccountStrategyTests.runAccountPhase(AccountStrategyTests.java:357) [test-classes/:na] at org.dcache.gplazma.strategies.AccountStrategyTests.shouldFailForRequisiteBuggyPlugin(AccountStrategyTests.java:337) [test-classes/:na] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[na:1.8.0_161] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) ~[na:1.8.0_161] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[na:1.8.0_161] at java.lang.reflect.Method.invoke(Method.java:498) ~[na:1.8.0_161] at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50) [junit-4.12.jar:4.12] at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12) [junit-4.12.jar:4.12] at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47) [junit-4.12.jar:4.12] at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17) [junit-4.12.jar:4.12] at org.junit.internal.runners.statements.ExpectException.evaluate(ExpectException.java:19) [junit-4.12.jar:4.12] at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26) [junit-4.12.jar:4.12] at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325) [junit-4.12.jar:4.12] at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78) [junit-4.12.jar:4.12] at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57) [junit-4.12.jar:4.12] at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290) [junit-4.12.jar:4.12] at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71) [junit-4.12.jar:4.12] at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288) [junit-4.12.jar:4.12] at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58) [junit-4.12.jar:4.12] at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268) [junit-4.12.jar:4.12] at org.junit.runners.ParentRunner.run(ParentRunner.java:363) [junit-4.12.jar:4.12] at org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:367) [surefire-junit4-2.19.1.jar:2.19.1] at org.apache.maven.surefire.junit4.JUnit4Provider.executeWithRerun(JUnit4Provider.java:274) [surefire-junit4-2.19.1.jar:2.19.1] at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:238) [surefire-junit4-2.19.1.jar:2.19.1] at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:161) [surefire-junit4-2.19.1.jar:2.19.1] at org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:290) [surefire-booter-2.19.1.jar:2.19.1] at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:242) [surefire-booter-2.19.1.jar:2.19.1] at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:121) [surefire-booter-2.19.1.jar:2.19.1]
This does not lead to the corresponding test suite showing failed tests. If the message is expected to occur, it should be masked from output.
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/dCache/dcache/issues/3871, or mute the thread https://github.com/notifications/unsubscribe-auth/AAjJ3XqMzxQKE7EMaoxiR1wVQ2hskCafks5tZAHtgaJpZM4SU7DY .
Recent Jenkins runs like https://ci.dcache.org/view/dCache%204.0/job/dCache-v4.0/61/consoleFull yielded the following during gplazma testing:
This does not lead to the corresponding test suite showing failed tests. If the message is expected to occur, it should be masked from output.