-
Notifications
You must be signed in to change notification settings - Fork 8.3k
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
[test-failed]: Chrome X-Pack UI Functional Tests1.x-pack/test/functional/apps/reporting_management/report_delete_pagination·ts - reporting management app Delete reports "before all" hook for "Confirm single report deletion works" #68847
Comments
Pinging @elastic/kibana-test-triage (failed-test) |
Pinging @elastic/kibana-reporting-services (Team:Reporting Services) |
Hi, I ran this test in the flaky test runner for Cloud SaaS, and found the following server logs. It looks like Elasticsearch becomes unresponsive. It's hard to tell how far into the test this succeeds, but it looks like not very far.
|
@tsullivan I believe the error you are seeing is different than the one I reported in this issue. { Error: Request Timeout after 30000ms |
The problem reported in this issue appears to be caused by the test order execution and is not specific to cloud, we should be able to reproduce via the test order. Attached is the screenshot. @tsullivan the other error you reported still needs to be investigated, but it is a separate issue. |
I see. In my testing, I referred to a single test suite that only includes this test and 1 other one. That explains why I didn't hit the problem of test order of execution. |
I ran this test in my local and on cloud 7.9 snapshot , runs fine in a loop. It must be the test order of execution as Tim rightly points out . |
We would need to change the order in the functional/config.js if we feel transform test needs to be run last. kibana/x-pack/test/functional/config.js Line 58 in 0e008e3
kibana/x-pack/test/functional/config.js Line 59 in 0e008e3
|
I figured out the problem. The transform tests just need to logout() in the after method in the index file. I have the fix implemented locally and I'll create a PR for it. |
Fix was not back ported to 7.8, can it be back ported to that branch? |
on it's way #70973 |
Version: 7.8.0
Class: Chrome X-Pack UI Functional Tests1.x-pack/test/functional/apps/reporting_management/report_delete_pagination·ts
Stack Trace:
{ TimeoutError: Waiting for element to be located By(css selector, [data-test-subj="kibanaChrome"])
Wait timed out after 102212ms
at /var/lib/jenkins/workspace/elastic+estf-cloud-kibana-tests/JOB/xpackGrp1/TASK/saas_run_kibana_tests/node/linux-immutable/ci/cloud/common/build/kibana/node_modules/selenium-webdriver/lib/webdriver.js:842:17
at process._tickCallback (internal/process/next_tick.js:68:7) name: 'TimeoutError', remoteStacktrace: '' }
Platform: cloud
Build Num: 324
The text was updated successfully, but these errors were encountered: