-
Notifications
You must be signed in to change notification settings - Fork 8.2k
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: APM API Integration tests (trial).x-pack/test/apm_api_integration/tests/index·ts - APM API tests correlations/failed_transactions.spec.ts trial 8.0.0 "before all" hook: runBefore in "8.0.0" #176544
Labels
failed-test
A test failure on a tracked branch, potentially flaky-test
Team:obs-ux-infra_services
Observability Infrastructure & Services User Experience Team
Comments
kibanamachine
added
the
failed-test
A test failure on a tracked branch, potentially flaky-test
label
Feb 8, 2024
kibanamachine
added
the
Team:obs-ux-infra_services
Observability Infrastructure & Services User Experience Team
label
Feb 8, 2024
Pinging @elastic/obs-ux-infra_services-team (Team:obs-ux-infra_services) |
New failure: CI Build - main |
Skipped. main: 8b4c655 |
CoenWarmer
pushed a commit
to CoenWarmer/kibana
that referenced
this issue
Feb 15, 2024
CoenWarmer
pushed a commit
to CoenWarmer/kibana
that referenced
this issue
Feb 15, 2024
awahab07
pushed a commit
to awahab07/kibana
that referenced
this issue
Feb 19, 2024
fkanout
pushed a commit
to fkanout/kibana
that referenced
this issue
Mar 4, 2024
3 tasks
walterra
added a commit
that referenced
this issue
Jul 3, 2024
…187444) ## Summary Fixes #176544. Fixes #187421. Fixes #176119. Fixes #176425. Fixes #175855. Fixes #175911. Fixes #176780. Follow up to #186182. Reenables and stabilizes APM correlations API integration tests. Review hint: View with the `w=1` flag to ignore whitespace changes: https://github.com/elastic/kibana/pull/187444/files?w=1 ### Checklist - [x] [Unit or functional tests](https://www.elastic.co/guide/en/kibana/master/development-tests.html) were updated or added to match the most common scenarios - [x] [Flaky Test Runner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was used on any tests changed - [x] This was checked for breaking API changes and was [labeled appropriately](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)
New failure: kibana-on-merge - 8.15 |
This looks again like the test is failing during setup not during the test itself. |
crespocarlos
added a commit
that referenced
this issue
Jul 24, 2024
fixes [#176425](#176425) fixes [#176544](#176544) ## Summary The problem happens intermittently, I've managed to reproduce it a few times though. I suspect that since the es_archive `8.0.0` does not have a type definition for the `label.served_from_cache` field, it leaves ES to determine what's the appropriate type, therefore causing ingestion to sometimes fail. The `apm_8.0.0` has a type definition for this field for `transaction` index https://github.com/elastic/kibana/blob/main/x-pack/test/apm_api_integration/common/fixtures/es_archiver/apm_8.0.0/mappings.json#L18824, so I followed the same configuration. Co-authored-by: Elastic Machine <[email protected]>
kibanamachine
pushed a commit
to kibanamachine/kibana
that referenced
this issue
Jul 24, 2024
fixes [elastic#176425](elastic#176425) fixes [elastic#176544](elastic#176544) ## Summary The problem happens intermittently, I've managed to reproduce it a few times though. I suspect that since the es_archive `8.0.0` does not have a type definition for the `label.served_from_cache` field, it leaves ES to determine what's the appropriate type, therefore causing ingestion to sometimes fail. The `apm_8.0.0` has a type definition for this field for `transaction` index https://github.com/elastic/kibana/blob/main/x-pack/test/apm_api_integration/common/fixtures/es_archiver/apm_8.0.0/mappings.json#L18824, so I followed the same configuration. Co-authored-by: Elastic Machine <[email protected]> (cherry picked from commit 850aa69)
kibanamachine
added a commit
that referenced
this issue
Jul 24, 2024
…189061) # Backport This will backport the following commits from `main` to `8.15`: - [[APM] Fix `labels.served_from_cache` type (#188836)](#188836) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Carlos Crespo","email":"[email protected]"},"sourceCommit":{"committedDate":"2024-07-24T12:08:52Z","message":"[APM] Fix `labels.served_from_cache` type (#188836)\n\nfixes [#176425](https://github.com/elastic/kibana/issues/176425)\r\nfixes [#176544](https://github.com/elastic/kibana/issues/176544)\r\n\r\n## Summary\r\n\r\nThe problem happens intermittently, I've managed to reproduce it a few\r\ntimes though. I suspect that since the es_archive `8.0.0` does not have\r\na type definition for the `label.served_from_cache` field, it leaves ES\r\nto determine what's the appropriate type, therefore causing ingestion to\r\nsometimes fail.\r\n\r\nThe `apm_8.0.0` has a type definition for this field for `transaction`\r\nindex\r\nhttps://github.com/elastic/kibana/blob/main/x-pack/test/apm_api_integration/common/fixtures/es_archiver/apm_8.0.0/mappings.json#L18824,\r\nso I followed the same configuration.\r\n\r\nCo-authored-by: Elastic Machine <[email protected]>","sha":"850aa6964898adbe4659a748b9b4ebc59e54366b","branchLabelMapping":{"^v8.16.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","backport:prev-minor","ci:project-deploy-observability","Team:obs-ux-infra_services","v8.16.0"],"title":"[APM] Fix `labels.served_from_cache` type","number":188836,"url":"https://github.com/elastic/kibana/pull/188836","mergeCommit":{"message":"[APM] Fix `labels.served_from_cache` type (#188836)\n\nfixes [#176425](https://github.com/elastic/kibana/issues/176425)\r\nfixes [#176544](https://github.com/elastic/kibana/issues/176544)\r\n\r\n## Summary\r\n\r\nThe problem happens intermittently, I've managed to reproduce it a few\r\ntimes though. I suspect that since the es_archive `8.0.0` does not have\r\na type definition for the `label.served_from_cache` field, it leaves ES\r\nto determine what's the appropriate type, therefore causing ingestion to\r\nsometimes fail.\r\n\r\nThe `apm_8.0.0` has a type definition for this field for `transaction`\r\nindex\r\nhttps://github.com/elastic/kibana/blob/main/x-pack/test/apm_api_integration/common/fixtures/es_archiver/apm_8.0.0/mappings.json#L18824,\r\nso I followed the same configuration.\r\n\r\nCo-authored-by: Elastic Machine <[email protected]>","sha":"850aa6964898adbe4659a748b9b4ebc59e54366b"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v8.16.0","branchLabelMappingKey":"^v8.16.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/188836","number":188836,"mergeCommit":{"message":"[APM] Fix `labels.served_from_cache` type (#188836)\n\nfixes [#176425](https://github.com/elastic/kibana/issues/176425)\r\nfixes [#176544](https://github.com/elastic/kibana/issues/176544)\r\n\r\n## Summary\r\n\r\nThe problem happens intermittently, I've managed to reproduce it a few\r\ntimes though. I suspect that since the es_archive `8.0.0` does not have\r\na type definition for the `label.served_from_cache` field, it leaves ES\r\nto determine what's the appropriate type, therefore causing ingestion to\r\nsometimes fail.\r\n\r\nThe `apm_8.0.0` has a type definition for this field for `transaction`\r\nindex\r\nhttps://github.com/elastic/kibana/blob/main/x-pack/test/apm_api_integration/common/fixtures/es_archiver/apm_8.0.0/mappings.json#L18824,\r\nso I followed the same configuration.\r\n\r\nCo-authored-by: Elastic Machine <[email protected]>","sha":"850aa6964898adbe4659a748b9b4ebc59e54366b"}}]}] BACKPORT--> Co-authored-by: Carlos Crespo <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
failed-test
A test failure on a tracked branch, potentially flaky-test
Team:obs-ux-infra_services
Observability Infrastructure & Services User Experience Team
A test failed on a tracked branch
First failure: CI Build - main
The text was updated successfully, but these errors were encountered: