Skip to content
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] XPackRestIT test {p0=ml/start_data_frame_analytics/Test start classification analysis when the dependent variable cardinality is too low} failing #126299

Open
elasticsearchmachine opened this issue Apr 4, 2025 · 3 comments
Labels
:ml Machine learning needs:risk Requires assignment of a risk label (low, medium, blocker) Team:ML Meta label for the ML team >test-failure Triaged test failures from CI

Comments

@elasticsearchmachine
Copy link
Collaborator

Build Scans:

Reproduction Line:

./gradlew ":x-pack:plugin:yamlRestTest" --tests "org.elasticsearch.xpack.test.rest.XPackRestIT.test {p0=ml/start_data_frame_analytics/Test start classification analysis when the dependent variable cardinality is too low}" -Dtests.seed=2AF51D1F410095EF -Dtests.jvm.argline="-Des.entitlements.enabled=true" -Dtests.locale=es-AR -Dtests.timezone=Europe/Rome -Druntime.java=24

Applicable branches:
main

Reproduces locally?:
N/A

Failure History:
See dashboard

Failure Message:

java.lang.AssertionError: Failure at [ml/start_data_frame_analytics:213]: the error message was expected to match the provided regex but didn't
Expected: Field \[keyword_field\] must have at least \[2\] distinct values but there were \[1\]
     but: was "{root_cause=[{type=no_shard_available_action_exception, reason=null, stack_trace=org.elasticsearch.action.NoShardAvailableActionException\n}], type=exception, reason=all shards failed, caused_by={type=search_phase_execution_exception, reason=all shards failed, phase=query, grouped=true, failed_shards=[{shard=0, index=.ml-stats-000001, node=null, reason={type=no_shard_available_action_exception, reason=null, stack_trace=org.elasticsearch.action.NoShardAvailableActionException\n}}], stack_trace=Failed to execute phase [query], all shards failed; shardFailures {[_na_][.ml-stats-000001][0]: org.elasticsearch.action.NoShardAvailableActionException\n}\n\tat [email protected]/org.elasticsearch.action.search.AbstractSearc
[truncated]

Issue Reasons:

  • [main] 3 failures in test test {p0=ml/start_data_frame_analytics/Test start classification analysis when the dependent variable cardinality is too low} (0.5% fail rate in 658 executions)
  • [main] 2 failures in step part-3 (1.2% fail rate in 169 executions)
  • [main] 2 failures in pipeline elasticsearch-pull-request (1.0% fail rate in 192 executions)

Note:
This issue was created using new test triage automation. Please report issues or feedback to es-delivery.

@elasticsearchmachine elasticsearchmachine added :Search Relevance/Ranking Scoring, rescoring, rank evaluation. >test-failure Triaged test failures from CI labels Apr 4, 2025
elasticsearchmachine added a commit that referenced this issue Apr 4, 2025
…data_frame_analytics/Test start classification analysis when the dependent variable cardinality is too low} #126299
@elasticsearchmachine
Copy link
Collaborator Author

This has been muted on branch main

Mute Reasons:

  • [main] 3 failures in test test {p0=ml/start_data_frame_analytics/Test start classification analysis when the dependent variable cardinality is too low} (0.5% fail rate in 658 executions)
  • [main] 2 failures in step part-3 (1.2% fail rate in 169 executions)
  • [main] 2 failures in pipeline elasticsearch-pull-request (1.0% fail rate in 192 executions)

Build Scans:

@elasticsearchmachine elasticsearchmachine added needs:risk Requires assignment of a risk label (low, medium, blocker) Team:Search Relevance Meta label for the Search Relevance team in Elasticsearch labels Apr 4, 2025
@elasticsearchmachine
Copy link
Collaborator Author

Pinging @elastic/es-search-relevance (Team:Search Relevance)

@benwtrent benwtrent added :ml Machine learning and removed :Search Relevance/Ranking Scoring, rescoring, rank evaluation. labels Apr 4, 2025
@elasticsearchmachine elasticsearchmachine added Team:ML Meta label for the ML team and removed Team:Search Relevance Meta label for the Search Relevance team in Elasticsearch labels Apr 4, 2025
@elasticsearchmachine
Copy link
Collaborator Author

Pinging @elastic/ml-core (Team:ML)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
:ml Machine learning needs:risk Requires assignment of a risk label (low, medium, blocker) Team:ML Meta label for the ML team >test-failure Triaged test failures from CI
Projects
None yet
Development

No branches or pull requests

2 participants