-
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
Sometimes reporting pdf optimize fails after upgrade #108963
Comments
Pinging @elastic/kibana-app-services (Team:AppServices) |
Pinging @elastic/kibana-reporting-services (Team:Reporting Services) |
It is possible this is related to Logs:
|
This sample of logs shows that a report was requested to be generated, but isn't getting executed. Task Manager be losing the task, or possibly marking the task as failed for some reason.
It looks like the report execution got stuck for over a minute after logging |
Duplicate of #106873 |
When running automated upgrade testing, I have some inconsistent results with generating a PDF optimized report on the built-in flights sample data, since it does not happen too often, it has been hard to reproduce outside the CI runs. Need to find a way to capture more debug information in the CI runs.
So far seen on upgrade paths:
The test environment is:
Do these seem acceptable for reliable results?
https://internal-ci.elastic.co/view/Stack%20Tests/job/elastic+estf-cloud-upgrade-tests/lastCompletedBuild/JOB=upgradeTest2,TASK=kibana_upgrade_tests,node=ess-testing/testReport/
The text was updated successfully, but these errors were encountered: