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: Firefox XPack UI Functional Tests.x-pack/test/functional/apps/status_page/status_page·ts - Status page Status Page allows user to navigate without authentication #50448

Closed
Tracked by #41983
kibanamachine opened this issue Nov 13, 2019 · 21 comments · Fixed by #100146
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 13, 2019

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. (/dev/shm/workspace/kibana/x-pack/test/functional/apps/status_page/status_page.ts)]

First failure: Jenkins Build

@kibanamachine kibanamachine added the failed-test A test failure on a tracked branch, potentially flaky-test label Nov 13, 2019
@elasticmachine
Copy link
Contributor

Pinging @elastic/kibana-test-triage (failed-test)

@tylersmalley
Copy link
Contributor

Closing issues I believe we're caused by Chromedriver update which was reverted in #50324

@kibanamachine
Copy link
Contributor Author

New failure: Jenkins Build

@kibanamachine
Copy link
Contributor Author

New failure: Jenkins Build

@kibanamachine
Copy link
Contributor Author

New failure: Jenkins Build

@spalger spalger added the Team:Core Core services & architecture: plugins, logging, config, saved objects, http, ES client, i18n, etc label May 21, 2020
@elasticmachine
Copy link
Contributor

Pinging @elastic/kibana-platform (Team:Platform)

@pgayvallet
Copy link
Contributor

@joshdover is this related to / part of #41983?

@joshdover
Copy link
Contributor

Yeah we should make sure this flakiness is fixed as part of that issue. I will update the ticket.

@kibanamachine
Copy link
Contributor Author

New failure: Jenkins Build

@kibanamachine
Copy link
Contributor Author

New failure: Jenkins Build

@mistic mistic closed this as completed Feb 8, 2021
@kibanamachine
Copy link
Contributor Author

New failure: Jenkins Build

@kibanamachine kibanamachine reopened this Feb 8, 2021
@kibanamachine
Copy link
Contributor Author

New failure: Jenkins Build

@joshdover
Copy link
Contributor

@mistic I'm guessing we'll need to take another look at this one?

@joshdover joshdover self-assigned this Feb 8, 2021
@mistic
Copy link
Member

mistic commented Feb 8, 2021

@joshdover that will be a good idea! I will skip it if it fails one more time 😃

@kibanamachine
Copy link
Contributor Author

New failure: Jenkins Build

@kibanamachine
Copy link
Contributor Author

New failure: Jenkins Build

@kibanamachine
Copy link
Contributor Author

New failure: Jenkins Build

mistic added a commit that referenced this issue Feb 9, 2021
mistic added a commit that referenced this issue Feb 9, 2021
@mistic
Copy link
Member

mistic commented Feb 9, 2021

The test keep failing and looks flaky. Skipping for now.

master/8.0: b78f9f9
7.x/7.12: c11a3ac

@kibanamachine
Copy link
Contributor Author

New failure: Jenkins Build

@joshdover
Copy link
Contributor

30+ days without any failures, closing.

@kibanamachine
Copy link
Contributor Author

New failure: CI Build - main

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:Core Core services & architecture: plugins, logging, config, saved objects, http, ES client, i18n, etc
Projects
None yet
Development

Successfully merging a pull request may close this issue.

8 participants