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: Analytics Integration Tests.test/analytics/tests/instrumented_events/from_the_server/core_overall_status_changed·ts - analytics instrumented events from the server core-overall_status_changed "before all" hook for "should emit the initial "degraded" event with the context set to initializing" #171164

Closed
kibanamachine opened this issue Nov 14, 2023 · 18 comments
Closed

Failing test: Analytics Integration Tests.test/analytics/tests/instrumented_events/from_the_server/core_overall_status_changed·ts - analytics instrumented events from the server core-overall_status_changed "before all" hook for "should emit the initial "degraded" event with the context set to initializing" #171164

kibanamachine opened this issue Nov 14, 2023 · 18 comments
Assignees
@gsoldevila
Labels
failed-test A test failure on a tracked branch, potentially flaky-test Team:Core Core services & architecture: plugins, logging, config, saved objects, http, ES client, i18n, etc

Comments

@kibanamachine
Copy link
Contributor

kibanamachine commented Nov 14, 2023 •
edited
Loading

A test failed on a tracked branch

Error: socket hang up
    at connResetException (node:internal/errors:720:14)
    at Socket.socketOnEnd (node:_http_client:525:23)
    at Socket.emit (node:events:529:35)
    at endReadableNT (node:internal/streams/readable:1368:12)
    at processTicksAndRejections (node:internal/process/task_queues:82:21) {
  code: 'ECONNRESET',
  response: undefined
}

First failure: CI Build - main
@kibanamachine kibanamachine added the failed-test A test failure on a tracked branch, potentially flaky-test label Nov 14, 2023
@botelastic botelastic bot added the needs-team Issues missing a team label label Nov 14, 2023
@kibanamachine kibanamachine added the Team:Core Core services & architecture: plugins, logging, config, saved objects, http, ES client, i18n, etc label Nov 14, 2023
@elasticmachine
Copy link
Contributor

Pinging @elastic/kibana-core (Team:Core)

@botelastic botelastic bot removed the needs-team Issues missing a team label label Nov 14, 2023
@kibanamachine
Copy link
Contributor Author

New failure: CI Build - main

@kibanamachine
Copy link
Contributor Author

New failure: CI Build - main

@kibanamachine
Copy link
Contributor Author

New failure: CI Build - main

@kibanamachine
Copy link
Contributor Author

New failure: CI Build - main

@kibanamachine
Copy link
Contributor Author

New failure: CI Build - main

@kibanamachine
Copy link
Contributor Author

New failure: CI Build - main

@kibanamachine
Copy link
Contributor Author

New failure: CI Build - main

@kibanamachine
Copy link
Contributor Author

New failure: CI Build - main

@kibanamachine
Copy link
Contributor Author

New failure: CI Build - main

@kibanamachine
Copy link
Contributor Author

New failure: CI Build - main

@kibanamachine
Copy link
Contributor Author

New failure: CI Build - main

@gsoldevila gsoldevila self-assigned this Nov 14, 2023
@gsoldevila
Copy link
Contributor

Seems a consequence of #171012
Investigating . . .

@delanni
Copy link
Contributor

delanni commented Nov 14, 2023

@gsoldevila - should we skip the test in the meantime?

@gsoldevila
Copy link
Contributor

Yes please, I have to confirm with the team whether the behavior that we check in the tests is the right one.

@delanni
Copy link
Contributor

delanni commented Nov 14, 2023

/skip

@kibanamachine
Copy link
Contributor Author

Skipped

main: 2b71ae1

kibanamachine added a commit that referenced this issue Nov 14, 2023
@kibanamachine
skip failing test suite (#171164)
2b71ae1
@kibanamachine
Copy link
Contributor Author

New failure: CI Build - main

@gsoldevila gsoldevila mentioned this issue Nov 14, 2023
Merged
gsoldevila added a commit that referenced this issue Nov 15, 2023
@gsoldevila
Upgrade tests to support the 1st event being the "available" (#171216)
feee02b 
## Summary

Address #171164

The tests were assuming that the first event emitted is always
`"degraded"`.
After merging #171012 this might
no longer be the case, aka the first event might already have an
`"available"` status and we might have no more events in that case.

This PR takes this enhancement into account and makes the test more
robust:
* Checking that an `"initializing"` event comes through first.
* Checking that we eventually get an `"available"` event.

---

Flaky Test Runner Pipeline - 100x 🟢 
https://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/3981
@logeekal logeekal mentioned this issue Nov 16, 2023
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@gsoldevila gsoldevila

Labels
failed-test A test failure on a tracked branch, potentially flaky-test Team:Core Core services & architecture: plugins, logging, config, saved objects, http, ES client, i18n, etc
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@delanni @elasticmachine @gsoldevila @kibanamachine