Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix exception rendering failure in the parent process when the plugin test throws an exception without StackTrace #8885

Closed
emeroad opened this issue May 25, 2022 · 0 comments · Fixed by #8949

Comments

@emeroad
Copy link
Member

emeroad commented May 25, 2022

When an exception without stacktrace is thrown, the error handling of test fails

java.lang.IndexOutOfBoundsException: Index: 17, Size: 17
	at java.util.SubList.rangeCheck(AbstractList.java:755)
	at java.util.SubList.get(AbstractList.java:639)
	at com.navercorp.pinpoint.test.plugin.PinpointPluginTestStatement.toException(PinpointPluginTestStatement.java from InputFileObject:138)
	at com.navercorp.pinpoint.test.plugin.PinpointPluginTestStatement.toException(PinpointPluginTestStatement.java from InputFileObject:141)
	at com.navercorp.pinpoint.test.plugin.PinpointPluginTestStatement.toFailure(PinpointPluginTestStatement.java from InputFileObject:125)
	at com.navercorp.pinpoint.test.plugin.PinpointPluginTestStatement.evaluate(PinpointPluginTestStatement.java from InputFileObject:83)
	at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
	at org.junit.runners.Suite.runChild(Suite.java:128)
	at com.navercorp.pinpoint.test.plugin.PinpointPluginTestSuite.access$200(PinpointPluginTestSuite.java:55)
	at com.navercorp.pinpoint.test.plugin.PinpointPluginTestSuite$3.run(PinpointPluginTestSuite.java:340)
	at com.navercorp.pinpoint.test.plugin.PinpointPluginTestSuite$1.schedule(PinpointPluginTestSuite.java:75)
	at com.navercorp.pinpoint.test.plugin.PinpointPluginTestSuite.runChildren(PinpointPluginTestSuite.java:338)
	at com.navercorp.pinpoint.test.plugin.PinpointPluginTestSuite.access$300(PinpointPluginTestSuite.java:55)
	at com.navercorp.pinpoint.test.plugin.PinpointPluginTestSuite$4.evaluate(PinpointPluginTestSuite.java:353)
	at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
	at org.junit.runner.JUnitCore.run(JUnitCore.java:137)
	at com.intellij.junit4.JUnit4IdeaTestRunner.startRunnerWithArgs(JUnit4IdeaTestRunner.java:68)
	at com.intellij.rt.junit.IdeaTestRunner$Repeater.startRunnerWithArgs(IdeaTestRunner.java:33)
	at com.intellij.rt.junit.JUnitStarter.prepareStreamsAndStart(JUnitStarter.java:230)
	at com.intellij.rt.junit.JUnitStarter.main(JUnitStarter.java:58)
java.lang.RuntimeException: java.util.concurrent.ExecutionException: org.apache.kafka.common.errors.TimeoutException: Topic kafka-it-topic not present in metadata after 60000 ms.
	at com.salesforce.kafka.test.KafkaTestUtils.produceRecords(KafkaTestUtils.java:143)
	at com.salesforce.kafka.test.KafkaTestUtils.produceRecords(KafkaTestUtils.java:175)
	at com.navercorp.pinpoint.plugin.kafka.KafkaClient_2_7_x_IT.producerSendTest(KafkaClient_2_7_x_IT.java:60)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:498)
	at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:59)
	at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
	at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:56)
	at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
	at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
	at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
	at org.junit.runners.ParentRunner$3.evaluate(ParentRunner.java:306)
	at com.navercorp.pinpoint.test.plugin.ForkedPinpointPluginTestRunner$1.evaluate(ForkedPinpointPluginTestRunner.java:60)
	at org.junit.runners.BlockJUnit4ClassRunner$1.evaluate(BlockJUnit4ClassRunner.java:100)
	at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:366)
	at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:103)
	at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:63)
	at org.junit.runners.ParentRunner$4.run(ParentRunner.java:331)
	at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:79)
	at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:329)
	at org.junit.runners.ParentRunner.access$100(ParentRunner.java:66)
	at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:293)
	at org.junit.runners.ParentRunner$3.evaluate(ParentRunner.java:306)
	at org.junit.runners.ParentRunner.run(ParentRunner.java:413)
	at org.junit.runner.JUnitCore.run(JUnitCore.java:137)
	at com.navercorp.pinpoint.test.plugin.shared.SharedPinpointPluginTest$2.run(SharedPinpointPluginTest.java:272)
	at java.lang.Thread.run(Thread.java:748)
Caused by: java.util.concurrent.ExecutionException: org.apache.kafka.common.errors.TimeoutException: Topic kafka-it-topic not present in metadata after 60000 ms.
	at org.apache.kafka.clients.producer.KafkaProducer$FutureFailure.<init>(KafkaProducer.java:1317)
	at org.apache.kafka.clients.producer.KafkaProducer.doSend(KafkaProducer.java:986)
	at org.apache.kafka.clients.producer.KafkaProducer.send(KafkaProducer.java:886)
	at org.apache.kafka.clients.producer.KafkaProducer.send(KafkaProducer.java:774)
	at com.salesforce.kafka.test.KafkaTestUtils.produceRecords(KafkaTestUtils.java:125)
	... 28 more
Caused by: org.apache.kafka.common.errors.TimeoutException: Topic kafka-it-topic not present in metadata after 60000 ms.
@emeroad emeroad modified the milestones: 2.4.0, 2.5.0 May 25, 2022
emeroad added a commit to emeroad/pinpoint that referenced this issue Jun 21, 2022
emeroad added a commit to emeroad/pinpoint that referenced this issue Jun 21, 2022
@emeroad emeroad linked a pull request Jun 21, 2022 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant