search

opentracing-contrib / java-specialagent

Automatic instrumentation for 3rd-party libraries in Java applications with OpenTracing.
Apache License 2.0
185 stars 46 forks source link

Circle CI: Thrift ITest prematurely exiting with "CircleCI received exit code 0" #555

Closed safris closed 4 years ago

safris commented 4 years ago 
-------> Intercept [ThriftProtocolAgentRule@pool-1-thread-1]: public org.apache.thrift.protocol.TMessage org.apache.thrift.protocol.TBinaryProtocol.readMessageBegin() throws org.apache.thrift.TException
-------> Intercept [ThreadAgentRule@pool-1-thread-1]: public void java.lang.Thread.run()
-------> Intercept [ThreadAgentRule@pool-1-thread-1]: public void java.lang.Thread.run()
-------> Intercept [ThreadAgentRule@Thread-1]: public void java.lang.Thread.run()
-------> Intercept [ThreadAgentRule@Thread-1]: public void java.lang.Thread.run()
Unknown instrumentable state for thread: DestroyJavaVM
-------> Intercept [ThreadAgentRule@DestroyJavaVM]: public synchronized void java.lang.Thread.start()
-------> Intercept [ThreadAgentRule@Thread-0]: public void io.opentracing.contrib.specialagent.SpecialAgentUtil$ShutdownHook.run()
-------> Intercept [ThreadAgentRule@Thread-0]: public void io.opentracing.contrib.specialagent.SpecialAgentUtil$ShutdownHook.run()
-------> Intercept [ThreadAgentRule@Thread-0]: public void io.opentracing.contrib.specialagent.SpecialAgentUtil$ShutdownHook.run()
[INFO] ------------------------------------------------------------------------
[INFO] Reactor Summary for SpecialAgent Tests for Apache Thrift 1.7.2-SNAPSHOT:
[INFO] 
[INFO] SpecialAgent Tests for Apache Thrift ............... SUCCESS [  0.002 s]
[INFO] SpecialAgent Test for Apache Thrift 0.10.0 ......... SUCCESS [  5.326 s]
[INFO] SpecialAgent Test for Apache Thrift 0.12.0 ......... SUCCESS [  2.728 s]
[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESS
[INFO] ------------------------------------------------------------------------
[INFO] Total time:  9.810 s
[INFO] Finished at: 2020-04-23T00:29:25Z
[INFO] ------------------------------------------------------------------------
andrewhsu commented 4 years ago

perhaps memory?

andrewhsu commented 4 years ago

Curious to know how often this happens? Is it consistent with a particular or class of tests?

safris commented 4 years ago

It happens every time. However, with my latest changes, it should not be an issue. I have separated all tests into individual containers. The reason the last build failed was due to another issue.

safris commented 4 years ago

This has been resolved by having each test run in its own container.