-
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
[Reporting/Fn Tests] Unskip Screenshot Tests #78190
[Reporting/Fn Tests] Unskip Screenshot Tests #78190
Conversation
@@ -40,7 +40,7 @@ export default function ({ getService }: FtrProviderContext) { | |||
filter(({ statusCode }) => statusCode === 500), | |||
map(({ message }) => message), | |||
first(), | |||
timeout(15000) | |||
timeout(120000) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This change is not related to a test that is currently failing, but the value was still way too low and was on the cusp of being flaky.
One of the reasons being very low was acceptable in this test is that the use case it covers has bug which makes it fail early instead of going through the usual 3 attempts to complete a report.
@elasticmachine merge upstream |
@elasticmachine merge master |
@elasticmachine merge upstream |
@elasticmachine merge upstream |
@elasticmachine merge upstream |
💚 Build SucceededMetrics 📚
History
To update your PR or re-run it, just comment with: |
Pinging @elastic/kibana-app-arch (Team:AppArch) |
Co-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>
Looks like this PR has a backport PR but it still hasn't been merged. Please merge it ASAP to keep the branches relatively in sync. |
1 similar comment
Looks like this PR has a backport PR but it still hasn't been merged. Please merge it ASAP to keep the branches relatively in sync. |
Summary
Four of the Reporting functional tests had to be skipped in the code because they became flaky. This turned out to be due to the test code not waiting long enough for screenshot reports (PNG, PDF) to finish. They were waiting 15 seconds, which is way too low, considering that the default timeout for generating a report is 2 minutes.
Closes #76581
Closes #76551