-
Notifications
You must be signed in to change notification settings - Fork 8.3k
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
Failing test: Jest Integration Tests.src/core/server/integration_tests/saved_objects/migrations/group3 - incompatible_cluster_routing_allocation retries the INIT action with a descriptive message when cluster settings are incompatible #158318
Failing test: Jest Integration Tests.src/core/server/integration_tests/saved_objects/migrations/group3 - incompatible_cluster_routing_allocation retries the INIT action with a descriptive message when cluster settings are incompatible #158318
Comments
Pinging @elastic/kibana-core (Team:Core) |
New failure: CI Build - main |
New failure: CI Build - main |
This was caused by #157802, which is unrelated to the failed test. The issue can be safely closed. |
New failure: CI Build - main |
This time, caused by the same reason as #163273. Closing. |
…/jest_integration_node/jest-preset.js` to resolve the following error: ``` Jest Integration Tests src/core/server/integration_tests/saved_objects/migrations/group3 incompatible_cluster_routing_allocation retries the INIT action with a descriptive message when cluster settings are incompatible Failures in tracked branches: 4 elastic#158318 Buildkite Job https://buildkite.com/elastic/kibana-pull-request/builds/153873#018a3421-e8f1-48e5-afdf-43496e4d1b0d Jest encountered an unexpected token Jest failed to parse a file. This happens e.g. when your code or its dependencies use non-standard JavaScript syntax, or when Jest is not configured to support such syntax. Out of the box Jest supports Babel, which will be used to transform your files into valid JS based on your Babel configuration. By default "node_modules" folder is ignored by transformers. Here's what you can do: • If you are trying to use ECMAScript Modules, see https://jestjs.io/docs/ecmascript-modules for how to enable it. • If you are trying to use TypeScript, see https://jestjs.io/docs/getting-started#using-typescript • To have some of your "node_modules" files transformed, you can specify a custom "transformIgnorePatterns" in your config. • If you need a custom transformation specify a "transform" option in your config. • If you simply want to mock your non-JS modules (e.g. binary assets) you can stub them out with the "moduleNameMapper" config option. You'll find more details and examples of these config options in the docs: https://jestjs.io/docs/configuration For information about custom transformations, see: https://jestjs.io/docs/code-transformation Details: /var/lib/buildkite-agent/builds/kb-n2-4-spot-f55f234db461f53e/elastic/kibana-pull-request/kibana/node_modules/langsmith/dist/index.js:1 ({"Object.<anonymous>":function(module,exports,require,__dirname,__filename,jest){export { Client } from "./client.js"; ```
New failure: CI Build - main |
The error is
It seems unrelated again. |
New failure: CI Build - main |
New failure: CI Build - main |
New failure: CI Build - main |
New failure: kibana-elasticsearch-snapshot-verify - main |
New failure: kibana-elasticsearch-snapshot-verify - main |
Skipped main: d44f70f |
## Summary Bumping the data archives to 8.last (8.18 at the moment) so that ES 9.0 finds it compatible. Resolves elastic#158318. Resolves elastic#163254. Resolves elastic#163255. Resolves elastic#166190. Resolves elastic#166199. Resolves elastic#167676. (cherry picked from commit 523372f)
# Backport This will backport the following commits from `main` to `8.x`: - [Update data archives for SO integration tests (#204561)](#204561) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Alejandro Fernández Haro","email":"[email protected]"},"sourceCommit":{"committedDate":"2024-12-17T14:18:48Z","message":"Update data archives for SO integration tests (#204561)\n\n## Summary\n\nBumping the data archives to 8.last (8.18 at the moment) so that ES 9.0\nfinds it compatible.\n\nResolves #158318.\nResolves #163254.\nResolves #163255.\nResolves #166190.\nResolves #166199.\nResolves #167676.","sha":"523372fd6e3c04134f70c9fc05ead121b6922181","branchLabelMapping":{"^v9.0.0$":"main","^v8.18.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Team:Core","release_note:skip","v9.0.0","backport:prev-minor"],"title":"Update data archives for SO integration tests","number":204561,"url":"https://github.com/elastic/kibana/pull/204561","mergeCommit":{"message":"Update data archives for SO integration tests (#204561)\n\n## Summary\n\nBumping the data archives to 8.last (8.18 at the moment) so that ES 9.0\nfinds it compatible.\n\nResolves #158318.\nResolves #163254.\nResolves #163255.\nResolves #166190.\nResolves #166199.\nResolves #167676.","sha":"523372fd6e3c04134f70c9fc05ead121b6922181"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v9.0.0","branchLabelMappingKey":"^v9.0.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/204561","number":204561,"mergeCommit":{"message":"Update data archives for SO integration tests (#204561)\n\n## Summary\n\nBumping the data archives to 8.last (8.18 at the moment) so that ES 9.0\nfinds it compatible.\n\nResolves #158318.\nResolves #163254.\nResolves #163255.\nResolves #166190.\nResolves #166199.\nResolves #167676.","sha":"523372fd6e3c04134f70c9fc05ead121b6922181"}}]}] BACKPORT--> Co-authored-by: Alejandro Fernández Haro <[email protected]>
## Summary Bumping the data archives to 8.last (8.18 at the moment) so that ES 9.0 finds it compatible. Resolves elastic#158318. Resolves elastic#163254. Resolves elastic#163255. Resolves elastic#166190. Resolves elastic#166199. Resolves elastic#167676.
A test failed on a tracked branch
First failure: CI Build - main
The text was updated successfully, but these errors were encountered: