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.

Sign up for GitHub

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

Jump to bottom

[CI] DataStreamsClientYamlTestSuiteIT class failing #123416

Closed
elasticsearchmachine opened this issue Feb 25, 2025 · 2 comments
Closed

[CI] DataStreamsClientYamlTestSuiteIT class failing #123416

elasticsearchmachine opened this issue Feb 25, 2025 · 2 comments
Labels
:Data Management/Data streams Data streams and their lifecycles low-risk An open issue or test failure that is a low risk to future releases Team:Data Management Meta label for data/management team >test-failure Triaged test failures from CI

Comments

@elasticsearchmachine
Copy link
Collaborator

elasticsearchmachine commented Feb 25, 2025 •
edited
Loading

Build Scans:

Reproduction Line:

undefined

Applicable branches:
main

Reproduces locally?:
N/A

Failure History:
See dashboard

Failure Message:

undefined

Issue Reasons:

  • [main] 5 consecutive failures in step windows-2022_checkrestcompat_platform-support-windows
  • [main] 10 failures in class org.elasticsearch.datastreams.DataStreamsClientYamlTestSuiteIT (1.2% fail rate in 853 executions)
  • [main] 5 failures in step windows-2022_checkrestcompat_platform-support-windows (62.5% fail rate in 8 executions)
  • [main] 2 failures in step part-1 (1.1% fail rate in 186 executions)
  • [main] 3 failures in step rest-compatibility (1.4% fail rate in 218 executions)
  • [main] 5 failures in pipeline elasticsearch-periodic-platform-support (55.6% fail rate in 9 executions)
  • [main] 3 failures in pipeline elasticsearch-pull-request (1.4% fail rate in 222 executions)

Note:
This issue was created using new test triage automation. Please report issues or feedback to es-delivery.
@elasticsearchmachine elasticsearchmachine added :Data Management/Data streams Data streams and their lifecycles >test-failure Triaged test failures from CI Team:Data Management Meta label for data/management team needs:risk Requires assignment of a risk label (low, medium, blocker) labels Feb 25, 2025
@elasticsearchmachine
Copy link
Collaborator Author

Pinging @elastic/es-data-management (Team:Data Management)

@nielsbauman nielsbauman added low-risk An open issue or test failure that is a low risk to future releases and removed needs:risk Requires assignment of a risk label (low, medium, blocker) labels Feb 26, 2025
@nielsbauman
Copy link
Contributor

nielsbauman commented Feb 26, 2025 •
edited
Loading

The first two build scans are related to entitlements (I see Not entitled: component [x-pack-ml], module [org.elasticsearch.ml] in the logs) and I know Core Infra is already working on these specific failures. The other failures are all PR builds with many failures and they're caused by the PRs themselves. The full stack trace related to the entitlements is:

[2025-02-26T13:15:35,939][ERROR][o.e.b.Elasticsearch      ] [test-cluster-1] fatal exception while booting Elasticsearch org.elasticsearch.entitlement.runtime.api.NotEntitledException: Not entitled: component [x-pack-ml], module [org.elasticsearch.ml], class [class org.elasticsearch.xpack.ml.utils.NamedPipeHelper$PrivilegedInputPipeOpener], entitlement [file], operation [read], path [\\.\pipe\controller_log_10928]	
	at org.elasticsearch.entitlement@9.1.0-SNAPSHOT/org.elasticsearch.entitlement.runtime.policy.PolicyManager.notEntitled(PolicyManager.java:452)	
	at org.elasticsearch.entitlement@9.1.0-SNAPSHOT/org.elasticsearch.entitlement.runtime.policy.PolicyManager.checkFileRead(PolicyManager.java:288)	
	at org.elasticsearch.entitlement@9.1.0-SNAPSHOT/org.elasticsearch.entitlement.runtime.policy.PolicyManager.checkFileRead(PolicyManager.java:277)	
	at org.elasticsearch.entitlement@9.1.0-SNAPSHOT/org.elasticsearch.entitlement.runtime.api.ElasticsearchEntitlementChecker.check$java_io_FileInputStream$(ElasticsearchEntitlementChecker.java:1133)	
	at java.base/java.io.FileInputStream.<init>(FileInputStream.java)	
	at org.elasticsearch.ml@9.1.0-SNAPSHOT/org.elasticsearch.xpack.ml.utils.NamedPipeHelper$PrivilegedInputPipeOpener.run(NamedPipeHelper.java:288)	
	at org.elasticsearch.ml@9.1.0-SNAPSHOT/org.elasticsearch.xpack.ml.utils.NamedPipeHelper$PrivilegedInputPipeOpener.run(NamedPipeHelper.java:277)	
	at java.base/java.security.AccessController.doPrivileged(AccessController.java:319)	
	at org.elasticsearch.ml@9.1.0-SNAPSHOT/org.elasticsearch.xpack.ml.utils.NamedPipeHelper.openNamedPipeInputStream(NamedPipeHelper.java:130)	
	at org.elasticsearch.ml@9.1.0-SNAPSHOT/org.elasticsearch.xpack.ml.utils.NamedPipeHelper.openNamedPipeInputStream(NamedPipeHelper.java:97)	
	at org.elasticsearch.ml@9.1.0-SNAPSHOT/org.elasticsearch.xpack.ml.process.ProcessPipes.connectLogStream(ProcessPipes.java:158)	
	at org.elasticsearch.ml@9.1.0-SNAPSHOT/org.elasticsearch.xpack.ml.process.NativeController.<init>(NativeController.java:85)	
	at org.elasticsearch.ml@9.1.0-SNAPSHOT/org.elasticsearch.xpack.ml.process.NativeController.makeNativeController(NativeController.java:66)	
	at org.elasticsearch.ml@9.1.0-SNAPSHOT/org.elasticsearch.xpack.ml.MachineLearning.createComponents(MachineLearning.java:1021)	
	at org.elasticsearch.server@9.1.0-SNAPSHOT/org.elasticsearch.node.NodeConstruction.lambda$construct$17(NodeConstruction.java:923)	
	at org.elasticsearch.server@9.1.0-SNAPSHOT/org.elasticsearch.plugins.PluginsService.lambda$flatMap$0(PluginsService.java:186)	
	at java.base/java.util.stream.ReferencePipeline$7$1FlatMap.accept(ReferencePipeline.java:289)	
	at java.base/java.util.stream.ReferencePipeline$3$1.accept(ReferencePipeline.java:215)	
	at java.base/java.util.AbstractList$RandomAccessSpliterator.forEachRemaining(AbstractList.java:722)	
	at java.base/java.util.stream.AbstractPipeline.copyInto(AbstractPipeline.java:570)	
	at java.base/java.util.stream.AbstractPipeline.wrapAndCopyInto(AbstractPipeline.java:560)	
	at java.base/java.util.stream.AbstractPipeline.evaluate(AbstractPipeline.java:636)	
	at java.base/java.util.stream.AbstractPipeline.evaluateToArrayNode(AbstractPipeline.java:291)	
	at java.base/java.util.stream.ReferencePipeline.toArray(ReferencePipeline.java:656)	
	at java.base/java.util.stream.ReferencePipeline.toArray(ReferencePipeline.java:662)	
	at java.base/java.util.stream.ReferencePipeline.toList(ReferencePipeline.java:667)	
	at org.elasticsearch.server@9.1.0-SNAPSHOT/org.elasticsearch.node.NodeConstruction.construct(NodeConstruction.java:945)	
	at org.elasticsearch.server@9.1.0-SNAPSHOT/org.elasticsearch.node.NodeConstruction.prepareConstruction(NodeConstruction.java:297)	
	at org.elasticsearch.server@9.1.0-SNAPSHOT/org.elasticsearch.node.Node.<init>(Node.java:185)	
	at org.elasticsearch.server@9.1.0-SNAPSHOT/org.elasticsearch.bootstrap.Elasticsearch$2.<init>(Elasticsearch.java:341)	
	at org.elasticsearch.server@9.1.0-SNAPSHOT/org.elasticsearch.bootstrap.Elasticsearch.initPhase3(Elasticsearch.java:341)	
	at org.elasticsearch.server@9.1.0-SNAPSHOT/org.elasticsearch.bootstrap.Elasticsearch.main(Elasticsearch.java:93)

@nielsbauman nielsbauman closed this as not planned Won't fix, can't repro, duplicate, stale Feb 26, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
:Data Management/Data streams Data streams and their lifecycles low-risk An open issue or test failure that is a low risk to future releases Team:Data Management Meta label for data/management team >test-failure Triaged test failures from CI
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@nielsbauman @elasticsearchmachine