[APM] Attempt to fix flaky test in service_group_count.spec.ts #204543
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
iblancof
added
release_note:skip
|
Pinging @elastic/obs-ux-infra_services-team (Team:obs-ux-infra_services) |
Flaky Test Runner Stats🎉 All tests passed! - kibana-flaky-test-suite-runner#7607[✅] x-pack/test/api_integration/deployment_agnostic/configs/serverless/oblt.apm.serverless.config.ts: 50/50 tests passed. |
…ostic-APM-API-Integration-Tests-x-pack-test-api_integration-deployment_agnostic-apis-observability-apm-service_groups-service_group_count-service_group_count-spec-ts
Bluefinger
approved these changes
Dec 30, 2024
…ostic-APM-API-Integration-Tests-x-pack-test-api_integration-deployment_agnostic-apis-observability-apm-service_groups-service_group_count-service_group_count-spec-ts
jennypavlova
approved these changes
Jan 2, 2025
…ostic-APM-API-Integration-Tests-x-pack-test-api_integration-deployment_agnostic-apis-observability-apm-service_groups-service_group_count-service_group_count-spec-ts
💛 Build succeeded, but was flaky
Failed CI StepsTest Failures
Metrics [docs]
History
cc @iblancof |
|
Starting backport for target branches: 8.x |
iblancof
deleted the
201267-Stateful-Observability-Deployment-agnostic-APM-API-Integration-Tests-x-pack-test-api_integration-deployment_agnostic-apis-observability-apm-service_groups-service_group_count-service_group_count-spec-ts
branch
kibanamachine
pushed a commit
to kibanamachine/kibana
that referenced
this pull request
Jan 7, 2025
…ic#204543) ## Summary Fixes elastic#201267 Before migrating the API tests to be deployment-agnostic, we had already seen some flaky results for this test (elastic#197912). After completing the migration, the error occurred again. This PR aims to fix the potential issue by ensuring that all existing alerts are cleared before creating the alerts used in the test case. Co-authored-by: jennypavlova <[email protected]> (cherry picked from commit 128739d)
💚 All backports created successfully
Note: Successful backport PRs will be merged automatically after passing CI. Questions ?Please refer to the Backport tool documentation |
kibanamachine
added a commit
that referenced
this pull request
Jan 7, 2025
…204543) (#205691) # Backport This will backport the following commits from `main` to `8.x`: - [[APM] Attempt to fix flaky test in service_group_count.spec.ts (#204543)](#204543) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Irene Blanco","email":"[email protected]"},"sourceCommit":{"committedDate":"2025-01-07T09:54:39Z","message":"[APM] Attempt to fix flaky test in service_group_count.spec.ts (#204543)\n\n## Summary\r\n\r\nFixes https://github.com/elastic/kibana/issues/201267\r\n\r\nBefore migrating the API tests to be deployment-agnostic, we had already\r\nseen some flaky results for this test\r\n(#197912). After completing the\r\nmigration, the error occurred again.\r\n\r\nThis PR aims to fix the potential issue by ensuring that all existing\r\nalerts are cleared before creating the alerts used in the test case.\r\n\r\nCo-authored-by: jennypavlova <[email protected]>","sha":"128739dc46f79457fb1848b4ef63c318cd1bb3f1","branchLabelMapping":{"^v9.0.0$":"main","^v8.18.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","v9.0.0","backport:prev-minor","Team:obs-ux-infra_services","v8.18.0"],"title":"[APM] Attempt to fix flaky test in service_group_count.spec.ts","number":204543,"url":"https://github.com/elastic/kibana/pull/204543","mergeCommit":{"message":"[APM] Attempt to fix flaky test in service_group_count.spec.ts (#204543)\n\n## Summary\r\n\r\nFixes https://github.com/elastic/kibana/issues/201267\r\n\r\nBefore migrating the API tests to be deployment-agnostic, we had already\r\nseen some flaky results for this test\r\n(#197912). After completing the\r\nmigration, the error occurred again.\r\n\r\nThis PR aims to fix the potential issue by ensuring that all existing\r\nalerts are cleared before creating the alerts used in the test case.\r\n\r\nCo-authored-by: jennypavlova <[email protected]>","sha":"128739dc46f79457fb1848b4ef63c318cd1bb3f1"}},"sourceBranch":"main","suggestedTargetBranches":["8.x"],"targetPullRequestStates":[{"branch":"main","label":"v9.0.0","branchLabelMappingKey":"^v9.0.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/204543","number":204543,"mergeCommit":{"message":"[APM] Attempt to fix flaky test in service_group_count.spec.ts (#204543)\n\n## Summary\r\n\r\nFixes https://github.com/elastic/kibana/issues/201267\r\n\r\nBefore migrating the API tests to be deployment-agnostic, we had already\r\nseen some flaky results for this test\r\n(#197912). After completing the\r\nmigration, the error occurred again.\r\n\r\nThis PR aims to fix the potential issue by ensuring that all existing\r\nalerts are cleared before creating the alerts used in the test case.\r\n\r\nCo-authored-by: jennypavlova <[email protected]>","sha":"128739dc46f79457fb1848b4ef63c318cd1bb3f1"}},{"branch":"8.x","label":"v8.18.0","branchLabelMappingKey":"^v8.18.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Irene Blanco <[email protected]>
kowalczyk-krzysztof
pushed a commit
to kowalczyk-krzysztof/kibana
that referenced
this pull request
Jan 7, 2025
…ic#204543) ## Summary Fixes elastic#201267 Before migrating the API tests to be deployment-agnostic, we had already seen some flaky results for this test (elastic#197912). After completing the migration, the error occurred again. This PR aims to fix the potential issue by ensuring that all existing alerts are cleared before creating the alerts used in the test case. Co-authored-by: jennypavlova <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
Fixes #201267
Before migrating the API tests to be deployment-agnostic, we had already seen some flaky results for this test (#197912). After completing the migration, the error occurred again.
This PR aims to fix the potential issue by ensuring that all existing alerts are cleared before creating the alerts used in the test case.