-
Notifications
You must be signed in to change notification settings - Fork 25k
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
OsProbeTests.testOsStats and memory-related YAML test failures on Debian 8 #66629
Comments
Pinging @elastic/es-core-features (Team:Core/Features) |
The failures in https://gradle-enterprise.elastic.co/s/2efkk2gimu5nm seem possibly related with memory misreported too. |
Want to highlight that there is info in two other places on the cause of this: I would be inclined to suggest that we add a check for 0 in OsProbe and then on debian 8 go and find the right size in /proc/meminfo. |
Thanks, @henningandersen. I'll look into that. |
These two:
failed for different tests. But I think the underlying cause is the same, i.e. memory reporting issue on Debian OS. The error message is:
The failed tests are (list them here so its sear:
|
heya @danhermann, I wonder if this failure from today is related, I would say so at first glance: https://gradle-enterprise.elastic.co/s/e2hir35m4taug/console-log?task=:server:test . |
Other associated failures from what appears to be the same root cause of misreported memory by the OS, all on Debian 8 runners:
ClientYamlTestSuiteIT test {p0=cluster.stats/10_basic/cluster stats test}
ClientYamlTestSuiteIT test {p0=cluster.stats/10_basic/get cluster stats returns cluster_uuid at the top level}
DocsClientYamlTestSuiteIT test {yaml=reference/ml/anomaly-detection/apis/get-ml-info/line_41}
Build scan: https://gradle-enterprise.elastic.co/s/z3bger2wnj62m
Repro line:
./gradlew ':server:test' --tests "org.elasticsearch.monitor.os.OsProbeTests.testOsStats" -Dtests.seed=A4A541649A2C4A2C -Dtests.security.manager=true -Dtests.locale=es-PY -Dtests.timezone=Asia/Anadyr -Druntime.java=8
Reproduces locally?: No (on MacOS, don't have a local Debian box)
Applicable branches:
7.x
,7.11
,7.10
,6.8
Failure history: build stats, first recent failure at
2020-12-17T04:22:14.082Z
on7.11
Failure excerpt:
The text was updated successfully, but these errors were encountered: