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: Interpreter Functional Tests.test/interpreter_functional/test_suites/run_pipeline/index·ts - runPipeline "before all" hook in "runPipeline" #60194

Closed
kibanamachine opened this issue Mar 14, 2020 · 20 comments
Closed

Failing test: Interpreter Functional Tests.test/interpreter_functional/test_suites/run_pipeline/index·ts - runPipeline "before all" hook in "runPipeline" #60194

kibanamachine opened this issue Mar 14, 2020 · 20 comments
Labels
failed-test A test failure on a tracked branch, potentially flaky-test impact:critical This issue should be addressed immediately due to a critical level of impact on the product. Team:DataVis Team label for DataVis Team Team:Visualizations Visualization editors, elastic-charts and infrastructure

Comments

@kibanamachine
Copy link
Contributor

kibanamachine commented Mar 14, 2020 •
edited
Loading

A test failed on a tracked branch

Error: retry.tryForTime timeout: Error: retry.try timeout: TimeoutError: Waiting for element to be located By(css selector, [data-test-subj="kibanaChrome"])
Wait timed out after 60023ms
    at /dev/shm/workspace/kibana/node_modules/selenium-webdriver/lib/webdriver.js:841:17
    at process._tickCallback (internal/process/next_tick.js:68:7)
    at onFailure (test/common/services/retry/retry_for_success.ts:28:9)
    at retryForSuccess (test/common/services/retry/retry_for_success.ts:68:13)
    at onFailure (test/common/services/retry/retry_for_success.ts:28:9)
    at retryForSuccess (test/common/services/retry/retry_for_success.ts:68:13)

First failure: Jenkins Build
@kibanamachine kibanamachine added the failed-test A test failure on a tracked branch, potentially flaky-test label Mar 14, 2020
@elasticmachine
Copy link
Contributor

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

@kibanamachine
Copy link
Contributor Author

New failure: Jenkins Build

@spalger
Copy link
Contributor

spalger commented Mar 15, 2020

Failure cased by #60148 and fixed by #60202

@spalger spalger closed this as completed Mar 15, 2020
@kibanamachine kibanamachine reopened this Mar 18, 2022
@kibanamachine
Copy link
Contributor Author

New failure: CI Build - main

@botelastic botelastic bot added the needs-team Issues missing a team label label Mar 18, 2022
@elasticmachine
Copy link
Contributor

Pinging @elastic/kibana-app-services (Team:AppServicesSv)

@botelastic botelastic bot removed the needs-team Issues missing a team label label Mar 18, 2022
@spalger
Copy link
Contributor

spalger commented Mar 18, 2022

@flash1293 do you think this could be caused by #118855?

@flash1293
Copy link
Contributor

It doesn’t look related to me… I can take a look on Monday

@exalate-issue-sync exalate-issue-sync bot added the impact:needs-assessment Product and/or Engineering needs to evaluate the impact of the change. label Jul 28, 2022
@exalate-issue-sync exalate-issue-sync bot added impact:critical This issue should be addressed immediately due to a critical level of impact on the product. and removed impact:needs-assessment Product and/or Engineering needs to evaluate the impact of the change. labels Aug 10, 2022
@vadimkibana
Copy link
Contributor

Thank you for contributing to this issue, however, we are closing this issue due to inactivity as part of a backlog grooming effort. If you believe this feature/bug should still be considered, please reopen with a comment.

@vadimkibana vadimkibana closed this as not planned Won't fix, can't repro, duplicate, stale Aug 12, 2022
@kibanamachine kibanamachine reopened this May 12, 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 - 8.8

@kibanamachine
Copy link
Contributor Author

New failure: CI Build - 8.8

@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

@jbudz
Copy link
Member

jbudz commented Sep 20, 2023

/skip

@kibanamachine
Copy link
Contributor Author

Skipped

main: 99bccce

kibanamachine added a commit that referenced this issue Sep 20, 2023
@kibanamachine
skip failing test suite (#60194)
99bccce
@kibanamachine
Copy link
Contributor Author

New failure: CI Build - main

@kibanamachine
Copy link
Contributor Author

New failure: CI Build - main

gergoabraham pushed a commit to gergoabraham/kibana that referenced this issue Sep 21, 2023
@kibanamachine @gergoabraham
skip failing test suite (elastic#60194)
ff7b66b
@vadimkibana vadimkibana added Team:Visualizations Visualization editors, elastic-charts and infrastructure Team:DataVis Team label for DataVis Team and removed Team:AppServicesSv labels Jan 15, 2024
@elasticmachine
Copy link
Contributor

Pinging @elastic/kibana-visualizations (Team:Visualizations)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
failed-test A test failure on a tracked branch, potentially flaky-test impact:critical This issue should be addressed immediately due to a critical level of impact on the product. Team:DataVis Team label for DataVis Team Team:Visualizations Visualization editors, elastic-charts and infrastructure
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
7 participants
@spalger @flash1293 @jbudz @elasticmachine @stratoula @kibanamachine @vadimkibana