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

Failing test: APM API Integration tests (basic).x-pack/test/apm_api_integration/tests/service_groups/service_group_count/service_group_count·spec·ts - APM API tests service_groups/service_group_count/service_group_count.spec.ts basic no archive Service group counts with alerts returns the correct number of alerts #197912

Closed
kibanamachine opened this issue Oct 25, 2024 · 7 comments
Closed

Failing test: APM API Integration tests (basic).x-pack/test/apm_api_integration/tests/service_groups/service_group_count/service_group_count·spec·ts - APM API tests service_groups/service_group_count/service_group_count.spec.ts basic no archive Service group counts with alerts returns the correct number of alerts #197912

kibanamachine opened this issue Oct 25, 2024 · 7 comments
Assignees
@crespocarlos
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
Copy link
Contributor

kibanamachine commented Oct 25, 2024 •
edited
Loading

A test failed on a tracked branch

Error: expected { services: 2, alerts: 2 } to have a property 'alerts' of 1, but got 2
    at Assertion.assert (expect.js:100:11)
    at Assertion.property (expect.js:417:10)
    at Context.<anonymous> (service_group_count.spec.ts:101:65)
    at processTicksAndRejections (node:internal/process/task_queues:95:5)
    at Object.apply (wrap_function.js:74:16)

First failure: kibana-on-merge - 8.x
@kibanamachine kibanamachine added the failed-test A test failure on a tracked branch, potentially flaky-test label Oct 25, 2024
@botelastic botelastic bot added the needs-team Issues missing a team label label Oct 25, 2024
@kibanamachine kibanamachine added the Team:obs-ux-infra_services Observability Infrastructure & Services User Experience Team label Oct 25, 2024
@elasticmachine
Copy link
Contributor

Pinging @elastic/obs-ux-infra_services-team (Team:obs-ux-infra_services)

@botelastic botelastic bot removed the needs-team Issues missing a team label label Oct 25, 2024
@kibanamachine
Copy link
Contributor Author

New failure: kibana-on-merge - main

@kibanamachine
Copy link
Contributor Author

New failure: kibana-on-merge - 8.x

@kibanamachine
Copy link
Contributor Author

New failure: kibana-on-merge - main

@kibanamachine
Copy link
Contributor Author

New failure: kibana-on-merge - main

mistic added a commit that referenced this issue Nov 20, 2024
@mistic
skip flaky suite (#197912)
20749d0
mistic added a commit that referenced this issue Nov 20, 2024
@mistic
skip flaky suite (#197912)
ffe7f23
@mistic
Copy link
Member

mistic commented Nov 20, 2024

Skipped.

main: 20749d0
8.x: ffe7f23

paulinashakirova pushed a commit to paulinashakirova/kibana that referenced this issue Nov 26, 2024
@mistic @paulinashakirova
skip flaky suite (elastic#197912)
392aec5
@crespocarlos crespocarlos self-assigned this Nov 27, 2024
@crespocarlos
Copy link
Contributor

crespocarlos commented Nov 27, 2024 •
edited
Loading

This test is now part of the deployement-agnostic suite. I couldn't find recent errors caused by this test recently in https://buildkite.com/elastic/kibana-on-merge. I'll close out.. Closing this in favor of #201267

CAWilson94 pushed a commit to CAWilson94/kibana that referenced this issue Dec 12, 2024
@mistic @CAWilson94
skip flaky suite (elastic#197912)
5f5d4f4
@iblancof iblancof mentioned this issue Dec 17, 2024
Merged
iblancof added a commit that referenced this issue Jan 7, 2025
@iblancof @jennypavlova
[APM] Attempt to fix flaky test in service_group_count.spec.ts (#204543)
128739d 
## 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.

Co-authored-by: jennypavlova <[email protected]>
kibanamachine pushed a commit to kibanamachine/kibana that referenced this issue Jan 7, 2025
@iblancof
[APM] Attempt to fix flaky test in service_group_count.spec.ts (elast…
8ddfafd 
…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)
kibanamachine added a commit that referenced this issue Jan 7, 2025
@kibanamachine @iblancof
[8.x] [APM] Attempt to fix flaky test in service_group_count.spec.ts (#…
c43b65e 
…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 issue Jan 7, 2025
@iblancof @jennypavlova @kowalczyk-krzysztof
[APM] Attempt to fix flaky test in service_group_count.spec.ts (elast…
2f325e5 
…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
Assignees

@crespocarlos crespocarlos

Labels
failed-test A test failure on a tracked branch, potentially flaky-test Team:obs-ux-infra_services Observability Infrastructure & Services User Experience Team
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@crespocarlos @mistic @elasticmachine @kibanamachine