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 - Triggers Actions UI.x-pack/test/functional_with_es_ssl/apps/triggers_actions_ui/alerts_page·ts - Actions and Triggers app Stack alerts page Loads the page with limited privileges Shows only allowed feature filters #181795

Closed
kibanamachine opened this issue Apr 26, 2024 · 4 comments · Fixed by #183568
Closed

Failing test: Chrome X-Pack UI Functional Tests with ES SSL - Triggers Actions UI.x-pack/test/functional_with_es_ssl/apps/triggers_actions_ui/alerts_page·ts - Actions and Triggers app Stack alerts page Loads the page with limited privileges Shows only allowed feature filters #181795

kibanamachine opened this issue Apr 26, 2024 · 4 comments · Fixed by #183568
Assignees
@JiaweiWu
Labels
failed-test A test failure on a tracked branch, potentially flaky-test Feature:Alerting/RulesManagement Issues related to the Rules Management UX Feature:Alerting Team:ResponseOps Label for the ResponseOps team (formerly the Cases and Alerting teams)

Comments

@kibanamachine
Copy link
Contributor

kibanamachine commented Apr 26, 2024 •
edited

A test failed on a tracked branch

Error: expected [] to have a length of 2 but got 0
    at Assertion.assert (expect.js:100:11)
    at Assertion.length (expect.js:374:8)
    at Context.<anonymous> (alerts_page.ts:59:41)
    at processTicksAndRejections (node:internal/process/task_queues:95:5)
    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 26, 2024
@botelastic botelastic bot added the needs-team Issues missing a team label label Apr 26, 2024
@kibanamachine kibanamachine added the Team:ResponseOps Label for the ResponseOps team (formerly the Cases and Alerting teams) label Apr 26, 2024
@elasticmachine
Copy link
Contributor

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

@botelastic botelastic bot removed the needs-team Issues missing a team label label Apr 26, 2024
@kibanamachine
Copy link
Contributor Author

New failure: CI Build - 8.14

@cnasikas cnasikas added Feature:Alerting Feature:Alerting/RulesManagement Issues related to the Rules Management UX labels Apr 30, 2024
@kibanamachine
Copy link
Contributor Author

New failure: CI Build - 8.14

kibanamachine added a commit that referenced this issue May 2, 2024
@kibanamachine
skip failing test suite (#181795)
2b25bce
@kibanamachine
Copy link
Contributor Author

Skipped

main: 2b25bce
8.14: c8626b2

kibanamachine added a commit that referenced this issue May 2, 2024
@kibanamachine
skip failing test suite (#181795)
c8626b2
yuliacech pushed a commit to yuliacech/kibana that referenced this issue May 3, 2024
@kibanamachine @yuliacech
skip failing test suite (elastic#181795)
5c5f52c
@JiaweiWu JiaweiWu self-assigned this May 15, 2024
@cnasikas cnasikas removed the v8.14.0 label May 15, 2024
@JiaweiWu JiaweiWu mentioned this issue May 15, 2024
Merged
1 task
JiaweiWu added a commit that referenced this issue May 16, 2024
@JiaweiWu
[ResponseOps] Fix flaky global alerts page E2E tests (#183568)
be659de 
## Summary
Resolves: #181795

### 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
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@JiaweiWu JiaweiWu

Labels
failed-test A test failure on a tracked branch, potentially flaky-test Feature:Alerting/RulesManagement Issues related to the Rules Management UX Feature:Alerting Team:ResponseOps Label for the ResponseOps team (formerly the Cases and Alerting teams)
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

[ResponseOps] Fix flaky global alerts page E2E tests JiaweiWu/kibana
4 participants
@cnasikas @elasticmachine @kibanamachine @JiaweiWu