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.x-pack/test/functional/apps/observability_logs_explorer/data_source_selector·ts - Observability Logs Explorer DataSourceSelector with installed integrations and uncategorized data streams when open on the integrations tab should display a list of installed integrations #188676

Closed
kibanamachine opened this issue Jul 18, 2024 · 5 comments
Assignees
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 Jul 18, 2024

A test failed on a tracked branch

Error: expected 2 to equal 3
    at Assertion.assert (expect.js:100:11)
    at Assertion.apply (expect.js:227:8)
    at Assertion.be (expect.js:69:22)
    at Context.<anonymous> (data_source_selector.ts:213:42)
    at processTicksAndRejections (node:internal/process/task_queues:95:5)
    at Object.apply (wrap_function.js:73:16)

First failure: kibana-on-merge - main

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

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

@awahab07
Copy link
Contributor

@elastic/fleet, @elastic/appex-qa, FYI, we get these failure because the AWS integration installations fails. It'd be ideal to diagnose this, or have a way to deterministically install packages.

The following sort of errors are spotted in buildkite test run logs:

...
[00:01:45]           │ proc [kibana] [2024-07-18T15:46:57.373+00:00][ERROR][plugins.fleet] '502 Bad Gateway' error response from package registry at https://epr.elastic.co/epr/aws/aws-1.51.0.zip...
...

We install three integrations apache, aws and system here which the tests require. Once in a while, aws integration installation fails.

@kibanamachine
Copy link
Contributor Author

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

@awahab07
Copy link
Contributor

awahab07 commented Jan 6, 2025

Looks like a transient fleet package installation failure. Will be keeping an eye for new failures.

@awahab07
Copy link
Contributor

Closing as there are no new failures.

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 Team:obs-ux-logs Observability Logs User Experience Team
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants