-
Notifications
You must be signed in to change notification settings - Fork 24.9k
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
Failure of :modules:transport-netty4:test on master #48330
Comments
Pinging @elastic/es-core-infra (:Core/Infra/Core) |
@przemekwitek I think we should mute the test on windows with something like |
Ok, I'll prepare a fix shortly. |
Another failure on 7.x: Build | 20191022105837-FAD56C29 |
Another instance: Build | 20191022105802-5CDA2F31 |
Another instance: Build | 20191022105811-393EEB9F |
This may relate to a bug from #47384, which only happened with a Java 8 runtime (which is why it failed on 7.x but not master). In that case, we could be more specific in what we muted. For example, in
See the specific issue's description in this comment: #47384 (comment) EDIT: I'm not sure this is the same issue, after a closer look, but it seems related. EDIT 2: I'm quite wrong, apologies for the noise. This affects the work I've been doing, not the other way around. |
I think this has to do with dirty state from a prior test. Netty holds a static allocator which if touched will allocate memory. In this test we are asserting the allocator is empty. This assertion was mainly a sanity check and I think was not well thought out on my part (requires all related test to cooperate). I opened #48356 to remove this assertion. |
Build | 20191022054831-A81DC5D0
Log | https://elasticsearch-ci.elastic.co/job/elastic+elasticsearch+master+multijob-windows-compatibility/os=windows-2012-r2/215/console
Build Scans | https://gradle-enterprise.elastic.co/s/hpnzc7hnzftce
Reproduce line:
Does not reproduce locally.
Excerpt from logs:
The text was updated successfully, but these errors were encountered: