-
Notifications
You must be signed in to change notification settings - Fork 25.2k
[TEST] testTracerLog failing #40586
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
Comments
Pinging @elastic/es-distributed |
Muted on the various branches (see linked commits) |
Can you have a look @andrershov? |
@ywelsch I'm looking at it and not sure what is going on here.
But here we see just the following line before the exception:
Stacktrace is telling us that exception is happening when TS_B tries to log the following message (TransportService:908):
The unusual thing here is that we expect it to log |
I think it is just due to the concurrency. Expectations are being added throughout the test. But the network threads are asynchronous. So it is possible there is an attempt to add a new assertions while the network threads attempt to log. We might need to create the MockAppenders, add assertion and then add it as a logging appender. Probably a new appender for each different scenario. |
This just failed for https://elasticsearch-ci.elastic.co/job/elastic+elasticsearch+master+intake/3437/ A slightly different error message this time:
Reproduce line is:
|
Adding more of the log outcome in case it helps: https://gist.github.com/matriv/ab0a86f3251a291fcd9e7283964e6f73 |
In general can we have new issues for new failures? It makes it easier to track what is new and old, and gives a clean slate for new failures. I opened #41890. |
I've seen failures for both
org.elasticsearch.xpack.security.transport.nio.SimpleSecurityNioTransportTests
andorg.elasticsearch.transport.nio.SimpleMockNioTransportTests
, see e.g.https://elasticsearch-ci.elastic.co/job/elastic+elasticsearch+master+artifactory/63/console
and
https://elasticsearch-ci.elastic.co/job/elastic+elasticsearch+master+intake/2750/console
Output:
The text was updated successfully, but these errors were encountered: