-
Notifications
You must be signed in to change notification settings - Fork 25.2k
[CI] DocsClientYamlTestSuiteIT test {yaml=reference/cat/nodes/line_361} failing #124103
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
…=reference/cat/nodes/line_361} #124103
This has been muted on branch 9.0 Mute Reasons:
Build Scans: |
Pinging @elastic/es-delivery (Team:Delivery) |
This has been muted on branch 8.18 Mute Reasons:
Build Scans:
|
…=reference/cat/nodes/line_361} #124103
This has been muted on branch 8.x Mute Reasons:
Build Scans:
|
…=reference/cat/nodes/line_361} #124103
The .security index is created asynchronously on a cluster startup. This affects some of the docs YAML tests in a way that they need to account for the existence of the .security index or wait for the index to be created and green. This PR disables the feature for docs YAML tests. Disabling the feature in docs YAML tests will solve the flakiness without affecting the coverage. Resolves elastic#122343 Resolves elastic#121748 Resolves elastic#121611 Resolves elastic#121345 Resolves elastic#121338 Resolves elastic#121337 Resolves elastic#121288 Resolves elastic#121287 Resolves elastic#121867 Resolves elastic#122335 Resolves elastic#122681 Resolves elastic#121976 Resolves elastic#123094 Resolves elastic#123192 Resolves elastic#122983 Resolves elastic#124671 Resolves elastic#124103
Reopening this because the failure in the |
Pinging @elastic/es-core-infra (Team:Core/Infra) |
This never worked with OpenJDK on Windows, but we bundle the Oracle JDK (at least on Windows), and we use that for tests launched via gradle. This is the OpenJDK implementation:
Apparently, the Oracle JDK has a different (more complete, proprietary?) management bean for Windows. I think it's reasonable to adjust the test to allow -1. We wouldn't catch cases where the CPU load percentage is unexpectedly -1, but I don't think these CAT tests should be the ones asserting that. |
The .security index is created asynchronously on a cluster startup. This affects some of the docs YAML tests in a way that they need to account for the existence of the .security index or wait for the index to be created and green. This PR disables the feature for docs YAML tests. Disabling the feature in docs YAML tests will solve the flakiness without affecting the coverage. Resolves elastic#122343 Resolves elastic#121748 Resolves elastic#121611 Resolves elastic#121345 Resolves elastic#121338 Resolves elastic#121337 Resolves elastic#121288 Resolves elastic#121287 Resolves elastic#121867 Resolves elastic#122335 Resolves elastic#122681 Resolves elastic#121976 Resolves elastic#123094 Resolves elastic#123192 Resolves elastic#122983 Resolves elastic#124671 Resolves elastic#124103 (cherry picked from commit cac356a) # Conflicts: # muted-tests.yml
The .security index is created asynchronously on a cluster startup. This affects some of the docs YAML tests in a way that they need to account for the existence of the .security index or wait for the index to be created and green. This PR disables the feature for docs YAML tests. Disabling the feature in docs YAML tests will solve the flakiness without affecting the coverage. Resolves elastic#122343 Resolves elastic#121748 Resolves elastic#121611 Resolves elastic#121345 Resolves elastic#121338 Resolves elastic#121337 Resolves elastic#121288 Resolves elastic#121287 Resolves elastic#121867 Resolves elastic#122335 Resolves elastic#122681 Resolves elastic#121976 Resolves elastic#123094 Resolves elastic#123192 Resolves elastic#122983 Resolves elastic#124671 Resolves elastic#124103 (cherry picked from commit cac356a) # Conflicts: # muted-tests.yml
The .security index is created asynchronously on a cluster startup. This affects some of the docs YAML tests in a way that they need to account for the existence of the .security index or wait for the index to be created and green. This PR disables the feature for docs YAML tests. Disabling the feature in docs YAML tests will solve the flakiness without affecting the coverage. Resolves elastic#122343 Resolves elastic#121748 Resolves elastic#121611 Resolves elastic#121345 Resolves elastic#121338 Resolves elastic#121337 Resolves elastic#121288 Resolves elastic#121287 Resolves elastic#121867 Resolves elastic#122335 Resolves elastic#122681 Resolves elastic#121976 Resolves elastic#123094 Resolves elastic#123192 Resolves elastic#122983 Resolves elastic#124671 Resolves elastic#124103 (cherry picked from commit cac356a) # Conflicts: # muted-tests.yml
) The .security index is created asynchronously on a cluster startup. This affects some of the docs YAML tests in a way that they need to account for the existence of the .security index or wait for the index to be created and green. This PR disables the feature for docs YAML tests. Disabling the feature in docs YAML tests will solve the flakiness without affecting the coverage. Resolves #122343 Resolves #121748 Resolves #121611 Resolves #121345 Resolves #121338 Resolves #121337 Resolves #121288 Resolves #121287 Resolves #121867 Resolves #122335 Resolves #122681 Resolves #121976 Resolves #123094 Resolves #123192 Resolves #122983 Resolves #124671 Resolves #124103 (cherry picked from commit cac356a) # Conflicts: # muted-tests.yml
) The .security index is created asynchronously on a cluster startup. This affects some of the docs YAML tests in a way that they need to account for the existence of the .security index or wait for the index to be created and green. This PR disables the feature for docs YAML tests. Disabling the feature in docs YAML tests will solve the flakiness without affecting the coverage. Resolves #122343 Resolves #121748 Resolves #121611 Resolves #121345 Resolves #121338 Resolves #121337 Resolves #121288 Resolves #121287 Resolves #121867 Resolves #122335 Resolves #122681 Resolves #121976 Resolves #123094 Resolves #123192 Resolves #122983 Resolves #124671 Resolves #124103 (cherry picked from commit cac356a) # Conflicts: # muted-tests.yml
) The .security index is created asynchronously on a cluster startup. This affects some of the docs YAML tests in a way that they need to account for the existence of the .security index or wait for the index to be created and green. This PR disables the feature for docs YAML tests. Disabling the feature in docs YAML tests will solve the flakiness without affecting the coverage. Resolves #122343 Resolves #121748 Resolves #121611 Resolves #121345 Resolves #121338 Resolves #121337 Resolves #121288 Resolves #121287 Resolves #121867 Resolves #122335 Resolves #122681 Resolves #121976 Resolves #123094 Resolves #123192 Resolves #122983 Resolves #124671 Resolves #124103 (cherry picked from commit cac356a) # Conflicts: # muted-tests.yml
This is not reproducible anymore, as we are transitioning to the new doc system; as we discussed on Slack, the fix would be in the test: -1 is an acceptable value, and we already accept it in related cat API tests (see for example |
@ldematte should we add the -1 fix on the 8.x branches to prevent the bot from reopening this (and related) issues? |
The only branch that still have the old docs is 8.18. We can add the fix to that branch if we want. |
Uh oh!
There was an error while loading. Please reload this page.
Build Scans:
Reproduction Line:
Applicable branches:
8.x
Reproduces locally?:
N/A
Failure History:
See dashboard
Failure Message:
Issue Reasons:
Note:
This issue was created using new test triage automation. Please report issues or feedback to es-delivery.
The text was updated successfully, but these errors were encountered: