-
Notifications
You must be signed in to change notification settings - Fork 344
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
Test failing -- TestElasticSearchSuite/TestSparkDependenciesES #1113
Comments
I'm looking into this. intel so far: It boils down to a combination of Thesis: if we delete the indices created in |
I've been able to reproduce this, and you can see repeated stack traces in the log for the test-spark-deps-spark-dependencies cron job here: https://gist.github.com/kevinearls/400f6d2920fbd16629078a8fcd7c0a7d @jpkrohling unfortunately I probably won't have much time to look at this today. It might also be better to have @pavolloffay take a look if he's free. @moolen Thanks for the tip, although I'm afraid if we just change test order or clean up it may be covering up another problem. This was passing until recently. |
I dug a little and found this in elasticsearch:
This seems to be caused by returning |
fixes jaegertracing/jaeger-operator#1113 Signed-off-by: Moritz Johner <[email protected]>
what about |
fixes jaegertracing/jaeger-operator#1113 Signed-off-by: Moritz Johner <[email protected]>
fixes jaegertracing/jaeger-operator#1113 Signed-off-by: Moritz Johner <[email protected]>
fixes jaegertracing/jaeger-operator#1113 Signed-off-by: Moritz Johner <[email protected]>
fixes jaegertracing/jaeger-operator#1113 Signed-off-by: Moritz Johner <[email protected]>
fixes jaegertracing/jaeger-operator#1113 Signed-off-by: Moritz Johner <[email protected]>
fixes jaegertracing/jaeger-operator#1113 Signed-off-by: Moritz Johner <[email protected]>
The test
TestElasticSearchSuite/TestSparkDependenciesES
as part ofes-otel
is currently failing, affecting #1111, #1110 and #1105. Themaster
branch is currently also failing after #1102 was merged, but I don't think that PR is the cause, as the failures on the mentioned PRs were happening before that got merged.cc @kevinearls
The text was updated successfully, but these errors were encountered: