You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We occasionally see the following test failures indicating that the Java agent threw an exception when it called the ClassFileTransformer.transform method. The tests eventually pass but it's unclear why this error is occurring in the first place. We should investigate further.
com.newrelic.agent.attributes.AgentAttributeSenderTest > testCustomAttributesInTransaction FAILED
com.newrelic.agent.tracers.SkipTracerException at AgentAttributeSenderTest.java:56
*** java.lang.instrument ASSERTION FAILED ***: "!errorOutstanding" with message transform method call failed at JPLISAgent.c line: 844
*** java.lang.instrument ASSERTION FAILED ***: "!errorOutstanding" with message transform method call failed at JPLISAgent.c line: 844
*** java.lang.instrument ASSERTION FAILED ***: "!errorOutstanding" with message transform method call failed at JPLISAgent.c line: 844
*** java.lang.instrument ASSERTION FAILED ***: "!errorOutstanding" with message transform method call failed at JPLISAgent.c line: 844
*** java.lang.instrument ASSERTION FAILED ***: "!errorOutstanding" with message transform method call failed at JPLISAgent.c line: 844
*** java.lang.instrument ASSERTION FAILED ***: "!errorOutstanding" with message transform method call failed at JPLISAgent.c line: 844
com.newrelic.agent.service.async.AsyncTransactionServiceTest > testAsyncTransactionServiceTimeout FAILED
java.lang.AssertionError at AsyncTransactionServiceTest.java:62
The reference to the JPLISAgent means that a Java agent (not necessarily the NR Java agent) threw an exception when it called the transform method.
One theory is that the unit test flickers are due to our use of mockito-inline for mocking and it’s underlying use of a Byte Buddy Java agent. We should try to migrate away from this library for testing and see if the test flickers resolve.
The text was updated successfully, but these errors were encountered:
We occasionally see the following test failures indicating that the Java agent threw an exception when it called the ClassFileTransformer.transform method. The tests eventually pass but it's unclear why this error is occurring in the first place. We should investigate further.
The reference to the
JPLISAgent
means that a Java agent (not necessarily the NR Java agent) threw an exception when it called the transform method.One theory is that the unit test flickers are due to our use of mockito-inline for mocking and it’s underlying use of a Byte Buddy Java agent. We should try to migrate away from this library for testing and see if the test flickers resolve.
The text was updated successfully, but these errors were encountered: