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.

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: Chrome X-Pack UI Functional Tests - aiops.x-pack/test/functional/apps/aiops/change_point_detection·ts - aiops change point detection attaches change point charts to a case #200091

Closed
kibanamachine opened this issue Nov 13, 2024 · 9 comments · Fixed by #201612
Assignees
Labels
failed-test A test failure on a tracked branch, potentially flaky-test :ml

Comments

@kibanamachine
Copy link
Contributor

kibanamachine commented Nov 13, 2024

A test failed on a tracked branch

Error: retry.tryForTime reached timeout 5000 ms
TimeoutError: The element [data-test-subj="all-cases-modal"] was still present when it should have disappeared.
Wait timed out after 2509ms
    at /opt/buildkite-agent/builds/bk-agent-prod-gcp-1731527911154860780/elastic/kibana-on-merge/kibana/node_modules/selenium-webdriver/lib/webdriver.js:923:22
    at processTicksAndRejections (node:internal/process/task_queues:95:5)
    at onFailure (retry_for_success.ts:18:9)
    at retryForSuccess (retry_for_success.ts:85:7)
    at RetryService.tryForTime (retry.ts:38:12)
    at Object.assertCaseModalVisible (common.ts:102:7)
    at Object.createCaseFromModal (create.ts:134:7)
    at Object.attachChartsToCases (change_point_detection_page.ts:305:7)
    at Context.<anonymous> (change_point_detection.ts:132:7)
    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 13, 2024
@botelastic botelastic bot added the needs-team Issues missing a team label label Nov 13, 2024
@elasticmachine
Copy link
Contributor

Pinging @elastic/ml-ui (:ml)

@botelastic botelastic bot removed the needs-team Issues missing a team label label Nov 13, 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 - 8.x

@kibanamachine
Copy link
Contributor Author

New failure: kibana-on-merge - main

@kibanamachine
Copy link
Contributor Author

New failure: kibana-on-merge - main

@kibanamachine
Copy link
Contributor Author

New failure: kibana-on-merge - main

@mistic
Copy link
Member

mistic commented Nov 19, 2024

Skipped.

main: 597c280
8.x: cbe6d4a

mistic added a commit that referenced this issue Nov 19, 2024
@mistic mistic added the v8.17.0 label Nov 19, 2024
@darnautov darnautov self-assigned this Nov 20, 2024
@peteharverson
Copy link
Contributor

Removing the blocker label as the functionality is working fine in manual testing. @darnautov is looking into a fix for the functional test failure caused by the cases modal remaining on the screen.

paulinashakirova pushed a commit to paulinashakirova/kibana that referenced this issue Nov 26, 2024
darnautov added a commit that referenced this issue Nov 28, 2024
## Summary

Fixes #200091
Fixes #200836

- Splits change point detection functional tests into separate groups
for dashboard and cases integrations.


### 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
kibanamachine pushed a commit to kibanamachine/kibana that referenced this issue Nov 28, 2024
## Summary

Fixes elastic#200091
Fixes elastic#200836

- Splits change point detection functional tests into separate groups
for dashboard and cases integrations.

### 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

(cherry picked from commit 0419606)
kibanamachine pushed a commit to kibanamachine/kibana that referenced this issue Nov 28, 2024
## Summary

Fixes elastic#200091
Fixes elastic#200836

- Splits change point detection functional tests into separate groups
for dashboard and cases integrations.

### 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

(cherry picked from commit 0419606)
CAWilson94 pushed a commit to CAWilson94/kibana that referenced this issue Dec 12, 2024
CAWilson94 pushed a commit to CAWilson94/kibana that referenced this issue Dec 12, 2024
## Summary

Fixes elastic#200091
Fixes elastic#200836

- Splits change point detection functional tests into separate groups
for dashboard and cases integrations.


### 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
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 :ml
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants