-
Notifications
You must be signed in to change notification settings - Fork 3.1k
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
Flakey Test: ITElasticsearchHealthCheck.oneHealthy #3197
Comments
I added info to the assertion on fail. there are similar flakes recently in actual ES tests, with an AbortedStreamException also. I didn't notice these until 0.99.9 or 1.0.0 I forget... either these will go away magically or we will have to perhaps use tracing inside the IT to print a trace when there was an exception and/or use the thx for hints @trustin |
Will apply the things as master build is erring
|
hmm even after changing to use system property, there's no causal chain here:
https://travis-ci.org/github/openzipkin/zipkin/builds/728217084 |
@minwoox ps if you have time, our elasticsearch tests fail on almost every PR since something around 0.99 It bounces between a couple tests on AbortedStreamException. If you have any cycles or know someone to help with this, it would be nice to have green builds again |
@adriancole I have looked through the code, but I couldn't find any clue. 😅 |
when setting this finally got more details.. <plugin>
<artifactId>maven-surefire-plugin</artifactId>
<version>${maven-failsafe-plugin.version}</version>
<configuration>
<!-- Ensures root cause ends up in the console -->
<trimStackTrace>false</trimStackTrace>
</configuration>
</plugin>
|
Oops, the response is sent before the request is fully sent. 😅 |
The `HttpResponse` was sent before the request are fully sent. So the request was aborted after getting the response. We should change to send the response after the request is fully received. - close openzipkin#3197
This will also fix the flaky test in ITElasticsearchHealthCheck hopefully. - close openzipkin#3197
This will also fix the flaky test in ITElasticsearchHealthCheck hopefully. - close #3197
Motivation: `AbortedStreamException.get()` returns the singleton or new instance depending on the `Flags.verboseExceptionSampler()`'s decision. However, if there's a problem in certain circumstances, it is very hard to find the cause with the singleton. Especially, this one. openzipkin/zipkin#3197 (comment) Modification: - Changed to created `AbortedStreamException` instances whenvere `get()` is called. Result: - You now get the stack trace of `AbortedStreamExcepetion` everytime.
The `HttpResponse` was sent before the request are fully sent. So the request was aborted after getting the response. We should change to send the response after the request is fully received. - close #3197 Signed-off-by: Adrian Cole <adrian@tetrate.io>
The text was updated successfully, but these errors were encountered: