-
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
[CI] Failure in BWC on debian 8 tests with _cat/nodes
. Error: Values less than -1 bytes are not supported
#54415
Comments
Pinging @elastic/es-core-features (:Core/Features/CAT APIs) |
Here are some nifty server logs: |
Related to PR: #54259 |
@gwbrown I think we may need a way to be more lenient for BWC when receiving values from other nodes, as otherwise users may run into this problem with mixed version clusters, what do you think? |
Oh nevermind! sorry @gwbrown, I read this as relating to the |
Ha, I made the same mistake at first, then started wondering if I'd done some work on preventing negative byte values and just forgotten. Happy to help if you want assistance, of course! |
Another failure today: Seems to be specific 7.x and debian08 |
It also appears that the affected tests are Now that we have an error trace on the response, there's a stack trace in the failing response for the ML test that we didn't have when this ticket was filed:
It appears that this error happens when
The first failure was on March 25th, not long after we cut the 7.7 branch. There have been consistent failures in the twice-daily bwc run for debian 8. Chart: gradle enterprise |
_cat/nodes
. Error: Values less than -1 bytes are not supported_cat/nodes
. Error: Values less than -1 bytes are not supported
Recent failures for today on Log: https://elasticsearch-ci.elastic.co/job/elastic+elasticsearch+7.x+multijob-unix-compatibility/os=debian-8&&immutable/667/console Failing tests: The same error message: |
Another failure: Jenkins, Build scan |
Another instance of the the MlConfigIndexMappingsFullClusterRestartIT.testMlConfigIndexMappingsAfterMigration failure on 7.x:
|
It happened again today on 7.x: https://gradle-enterprise.elastic.co/s/negka76witrbo This test is failing twice a day for some time now so I'm going to mute it (#55389). I'm also assigning this issue to @jakelandis so that he can assign it to someone from the core/feature team. |
Failed again: https://gradle-enterprise.elastic.co/s/hsoc4hi5sf5p6 (7.x, debian)
Error message is |
Still happening: https://gradle-enterprise.elastic.co/s/pzl2mgclmc2zq |
Still happening: https://gradle-enterprise.elastic.co/s/wyh6iqz76h54u |
Another one: https://gradle-enterprise.elastic.co/s/j6vigxs56aes2/ I'm going to try and mute more tests for this. |
I couldn't see a way to mute this easily, and I also tried to work out how this could happen, but didn't get anywhere. Given that it's a problem on 7.x debian-8 only, I suspect this is actually an issue with the OS Management Bean on Java 8, and we should just work around it by detecting that We could try and work out why, but I suspect that will just end up finding that it's a JDK bug we can't do anything about |
I spent some time on this yesterday and came to a similar conclusion regarding detecting |
https://gradle-enterprise.elastic.co/s/cno7wedfdoqfg https://gradle-enterprise.elastic.co/s/viy6zvnenjkn4 Same failure, but on 7.7. Would be good to have the fix backported into 7.7 when possible. |
More today: https://gradle-enterprise.elastic.co/s/fnqczt5dpd7r6 (7.x, testing vs 7.7.1) |
I will backport the fix for these into 7.7 and 7.8 shortly. |
Closing this as the fix has been backported to 7.7 and 7.8 in addition to 7.x and master. |
In our case it seemed to be the swap, so switching it off with |
Multiple BWC tests fail in similar ways.
Values less than -1 bytes are not supported: -44383772672b
This occurs in BWC tests with 7.7.
Some failures:
https://gradle-enterprise.elastic.co/s/rpa3bpzgm7bkg
https://gradle-enterprise.elastic.co/s/or7qqkbuuazto
Here is one of the many stack traces:
Full stack trace
The text was updated successfully, but these errors were encountered: