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: Serverless Observability Functional Tests.x-pack/test_serverless/functional/test_suites/observability/observability_logs_explorer/data_source_selector·ts - serverless observability UI Observability Logs Explorer DataSourceSelector with installed integrations and uncategorized data streams when open on the integrations tab should sort the integrations list by the clicked sorting option #182017

Closed
kibanamachine opened this issue Apr 29, 2024 · 6 comments · Fixed by #196516
Closed

Failing test: Serverless Observability Functional Tests.x-pack/test_serverless/functional/test_suites/observability/observability_logs_explorer/data_source_selector·ts - serverless observability UI Observability Logs Explorer DataSourceSelector with installed integrations and uncategorized data streams when open on the integrations tab should sort the integrations list by the clicked sorting option #182017

kibanamachine opened this issue Apr 29, 2024 · 6 comments · Fixed by #196516
Assignees
@awahab07
Labels
failed-test A test failure on a tracked branch, potentially flaky-test Team:obs-ux-logs Observability Logs User Experience Team

Comments

@kibanamachine
Copy link
Contributor

kibanamachine commented Apr 29, 2024 •
edited
Loading

A test failed on a tracked branch

Error: retry.try reached timeout 120000 ms
Error: expected [ 'System', 'AWS', 'Apache HTTP Server' ] to sort of equal [ 'Apache HTTP Server', 'AWS', 'System' ]
    at Assertion.assert (expect.js:100:11)
    at Assertion.eql (expect.js:244:8)
    at data_source_selector.ts:241:37
    at processTicksAndRejections (node:internal/process/task_queues:95:5)
    at runAttempt (retry_for_success.ts:29:15)
    at retryForSuccess (retry_for_success.ts:98:21)
    at RetryService.try (retry.ts:51:12)
    at Context.<anonymous> (data_source_selector.ts:239:11)
    at Object.apply (wrap_function.js:73:16)
    at onFailure (retry_for_success.ts:17:9)
    at retryForSuccess (retry_for_success.ts:84:7)
    at RetryService.try (retry.ts:51:12)
    at Context.<anonymous> (data_source_selector.ts:239:11)
    at Object.apply (wrap_function.js:73:16)

First failure: CI Build - main
@kibanamachine kibanamachine added the failed-test A test failure on a tracked branch, potentially flaky-test label Apr 29, 2024
@botelastic botelastic bot added the needs-team Issues missing a team label label Apr 29, 2024
@kibanamachine kibanamachine added the Team:obs-ux-logs Observability Logs User Experience Team label Apr 29, 2024
@elasticmachine
Copy link
Contributor

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

@botelastic botelastic bot removed the needs-team Issues missing a team label label Apr 29, 2024
@awahab07 awahab07 self-assigned this Jul 21, 2024
This was referenced Jul 21, 2024
Merged
Closed
@awahab07
Copy link
Contributor

awahab07 commented Jul 22, 2024 •
edited
Loading

There's only one instance of this failure and there are no subsequent occurrences. Also could not reproduce it in flaky test runs.

@kibanamachine kibanamachine reopened this Sep 26, 2024
@kibanamachine
Copy link
Contributor Author

New failure: kibana-on-merge - main

@awahab07
Copy link
Contributor

The second failure seems like the assertion settlement issue as the screenshot shows the correct sort order (contrary to the first failure where the order is indeed incorrect). Will keep an eye on if it happens again and how often does it happen.

First failureSecond failure

Image

Image

@yngrdyn
Copy link
Contributor

yngrdyn commented Sep 30, 2024

One thing I noticed between the two screenshots is the sort is different, maybe they are being correctly sorted according to the selected one. Maybe it is just flaky?

@kibanamachine
Copy link
Contributor Author

New failure: kibana-on-merge - main

@awahab07 awahab07 mentioned this issue Oct 16, 2024
Merged
kibanamachine pushed a commit to kibanamachine/kibana that referenced this issue Oct 22, 2024
@awahab07
Make sort integration test resilient to network delays. (elastic#196516)
1807990 
Fixes elastic#182017

## Summary

The PR tries to address the flakiness from the test.

Co-authored-by: Elastic Machine <[email protected]>
(cherry picked from commit cbf7982)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@awahab07 awahab07

Labels
failed-test A test failure on a tracked branch, potentially flaky-test Team:obs-ux-logs Observability Logs User Experience Team
Projects
None yet
Milestone
No milestone
4 participants
@yngrdyn @awahab07 @elasticmachine @kibanamachine