quarkus: CI failure in TracingTest#testContextPropagationInFaultTolerance

@pavolloffay @kenfinnigan we have CI failing from time to time due to the test added here.

The failure is the following:

2019-04-23 11:38:25,393 INFO  [io.quarkus] (main) Quarkus stopped in 0.033s
[ERROR] Tests run: 4, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 6.981 s <<< FAILURE! - in io.quarkus.smallrye.opentracing.deployment.TracingTest
[ERROR] testContextPropagationInFaultTolerance  Time elapsed: 0.971 s  <<< FAILURE!
org.opentest4j.AssertionFailedError: expected: <5> but was: <4>
	at org.junit.jupiter.api.AssertionUtils.fail(AssertionUtils.java:55)
	at org.junit.jupiter.api.AssertEquals.failNotEqual(AssertEquals.java:195)
	at org.junit.jupiter.api.AssertEquals.assertEquals(AssertEquals.java:152)
	at org.junit.jupiter.api.AssertEquals.assertEquals(AssertEquals.java:147)
	at org.junit.jupiter.api.Assertions.assertEquals(Assertions.java:510)
	at io.quarkus.smallrye.opentracing.deployment.TracingTest.testContextPropagationInFaultTolerance(TracingTest.java:105)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

It happens once in a while. I saw it twice, once on a Linux build and once on a Windows build.

Could you take a look at that issue and, hopefully, fix it before tomorrow’s release?

About this issue

  • Original URL
  • State: closed
  • Created 5 years ago
  • Comments: 21 (21 by maintainers)

Commits related to this issue

Most upvoted comments

The test has been disabled for now; I think the right path forward would be to fix the problem, update the component, and then re-enable the test.