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: Chrome X-Pack UI Functional Tests with ES SSL - Cases - group 1.x-pack/test/functional_with_es_ssl/apps/cases/group1/view_case·ts - Cases - group 1 View case "after all" hook: afterTestSuite.trigger in "View case" #202378

Open
kibanamachine opened this issue Nov 30, 2024 · 2 comments
Open

Failing test: Chrome X-Pack UI Functional Tests with ES SSL - Cases - group 1.x-pack/test/functional_with_es_ssl/apps/cases/group1/view_case·ts - Cases - group 1 View case "after all" hook: afterTestSuite.trigger in "View case" #202378

kibanamachine opened this issue Nov 30, 2024 · 2 comments
Labels
failed-es-promotion failed-test A test failure on a tracked branch, potentially flaky-test Feature:Cases Cases feature Team:ResponseOps Label for the ResponseOps team (formerly the Cases and Alerting teams)

Comments

@kibanamachine
Copy link
Contributor

A test failed on a tracked branch

Error: Timeout of 360000ms exceeded. For async tests and hooks, ensure "done()" is called; if returning a Promise, ensure it resolves. (/opt/buildkite-agent/builds/bk-agent-prod-gcp-1732938107126395991/elastic/kibana-elasticsearch-snapshot-verify/kibana/x-pack/test/functional_with_es_ssl/apps/cases/group1/view_case.ts)
    at listOnTimeout (node:internal/timers:573:17)
    at processTimers (node:internal/timers:514:7) {
  code: 'ERR_MOCHA_TIMEOUT',
  timeout: 360000,
  file: '/opt/buildkite-agent/builds/bk-agent-prod-gcp-1732938107126395991/elastic/kibana-elasticsearch-snapshot-verify/kibana/x-pack/test/functional_with_es_ssl/apps/cases/group1/view_case.ts'
}

First failure: kibana-elasticsearch-snapshot-verify - 8.15
@kibanamachine kibanamachine added the failed-test A test failure on a tracked branch, potentially flaky-test label Nov 30, 2024
@botelastic botelastic bot added the needs-team Issues missing a team label label Nov 30, 2024
@kibanamachine kibanamachine added failed-es-promotion Team:ResponseOps Label for the ResponseOps team (formerly the Cases and Alerting teams) labels Nov 30, 2024
@elasticmachine
Copy link
Contributor

Pinging @elastic/response-ops (Team:ResponseOps)

@botelastic botelastic bot removed the needs-team Issues missing a team label label Nov 30, 2024
@cnasikas cnasikas added the Feature:Cases Cases feature label Dec 2, 2024
@elasticmachine
Copy link
Contributor

Pinging @elastic/response-ops-cases (Feature:Cases)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
failed-es-promotion failed-test A test failure on a tracked branch, potentially flaky-test Feature:Cases Cases feature Team:ResponseOps Label for the ResponseOps team (formerly the Cases and Alerting teams)
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@cnasikas @elasticmachine @kibanamachine