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: 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 - Stateful Observability - Deployment-agnostic APM API integration tests APM service_groups Service group counts with alerts returns the correct number of alerts #201267

Closed
kibanamachine opened this issue Nov 21, 2024 · 1 comment · Fixed by #204543
Closed

Failing test: 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 - Stateful Observability - Deployment-agnostic APM API integration tests APM service_groups Service group counts with alerts returns the correct number of alerts #201267

kibanamachine opened this issue Nov 21, 2024 · 1 comment · Fixed by #204543
Assignees
@iblancof
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

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:111:65)
    at processTicksAndRejections (node:internal/process/task_queues:95:5)
    at Object.apply (wrap_function.js:74:16)

First failure: kibana-on-merge - main
@kibanamachine kibanamachine added the failed-test A test failure on a tracked branch, potentially flaky-test label Nov 21, 2024
@botelastic botelastic bot added the needs-team Issues missing a team label label Nov 21, 2024
@kibanamachine kibanamachine added the Team:obs-ux-infra_services Observability Infrastructure & Services User Experience Team label Nov 21, 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 Nov 21, 2024
@crespocarlos crespocarlos mentioned this issue Nov 27, 2024
Closed
@iblancof iblancof self-assigned this Dec 16, 2024
@iblancof iblancof mentioned this issue Dec 17, 2024
Merged
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)
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]>
CAWilson94 pushed a commit to CAWilson94/kibana that referenced this issue Jan 13, 2025
@iblancof @jennypavlova @CAWilson94
[APM] Attempt to fix flaky test in service_group_count.spec.ts (elast…
7d99f99 
…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

@iblancof iblancof

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

Successfully merging a pull request may close this issue.

[APM] Attempt to fix flaky test in service_group_count.spec.ts iblancof/kibana
4 participants
@crespocarlos @elasticmachine @kibanamachine @iblancof