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: Chrome X-Pack UI Functional Tests.x-pack/test/functional/apps/dashboard/group3/reporting/screenshots·ts - dashboard Reporting Dashboard Reporting Screenshots Sample data from Kibana 7.6 PNG file matches the baseline image #142484

Closed
kibanamachine opened this issue Oct 3, 2022 · 15 comments · Fixed by #163966
Closed

Failing test: Chrome X-Pack UI Functional Tests.x-pack/test/functional/apps/dashboard/group3/reporting/screenshots·ts - dashboard Reporting Dashboard Reporting Screenshots Sample data from Kibana 7.6 PNG file matches the baseline image #142484

kibanamachine opened this issue Oct 3, 2022 · 15 comments · Fixed by #163966
Labels
(Deprecated) Feature:Reporting Use Reporting:Screenshot, Reporting:CSV, or Reporting:Framework instead failed-test A test failure on a tracked branch, potentially flaky-test Team:SharedUX Team label for AppEx-SharedUX (formerly Global Experience)

Comments

@kibanamachine
Copy link
Contributor

kibanamachine commented Oct 3, 2022 •
edited
Loading

A test failed on a tracked branch

Error: expected 0.11965814144852517 to be below 0.09
    at Assertion.assert (node_modules/@kbn/expect/expect.js:100:11)
    at Assertion.lessThan.Assertion.below (node_modules/@kbn/expect/expect.js:336:8)
    at Function.lessThan (node_modules/@kbn/expect/expect.js:531:15)
    at Context.<anonymous> (x-pack/test/functional/apps/dashboard/group3/reporting/screenshots.ts:316:35)
    at Object.apply (node_modules/@kbn/test/target_node/src/functional_test_runner/lib/mocha/wrap_function.js:87:16)

First failure: CI Build - main
@kibanamachine kibanamachine added the failed-test A test failure on a tracked branch, potentially flaky-test label Oct 3, 2022
@botelastic botelastic bot added the needs-team Issues missing a team label label Oct 3, 2022
@elasticmachine
Copy link
Contributor

Pinging @elastic/kibana-reporting-services (Team:Reporting Services)

@botelastic botelastic bot removed the needs-team Issues missing a team label label Oct 3, 2022
@petrklapka petrklapka added (Deprecated) Feature:Reporting Use Reporting:Screenshot, Reporting:CSV, or Reporting:Framework instead Team:SharedUX Team label for AppEx-SharedUX (formerly Global Experience) and removed Team:Reporting Services labels Oct 24, 2022
@tsullivan
Copy link
Member

Closing, as this seems to have been a one-time issue.

@kibanamachine kibanamachine reopened this Mar 29, 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 - main

@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

@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 Mar 30, 2023

/skip

@kibanamachine
Copy link
Contributor Author

Skipped

main: 036fe0e

kibanamachine added a commit that referenced this issue Mar 30, 2023
@kibanamachine
skip failing test suite (#142484)
036fe0e
@tsullivan
Copy link
Member

I'm looking at this today, and I find that it's the downloads a PDF file: large dashboard that is responsible for the failures. The report is generated, but the results usually bad (blank areas in the PNG, empty data in charts).

There appears to be a dimensional limit to Dashboards that can be safely captured. I think we shouldn't be that surprised, since there are probably millions of DOM elements on this screen.

@tsullivan
Copy link
Member

the results usually bad (blank areas in the PNG, empty data in charts).

Artifact of #138812

@tsullivan tsullivan mentioned this issue Aug 15, 2023
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
(Deprecated) Feature:Reporting Use Reporting:Screenshot, Reporting:CSV, or Reporting:Framework instead failed-test A test failure on a tracked branch, potentially flaky-test Team:SharedUX Team label for AppEx-SharedUX (formerly Global Experience)
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

[Dashboard/Reporting/Test] delete unusable large screenshot tests tsullivan/kibana
6 participants
@tsullivan @jbudz @mistic @elasticmachine @kibanamachine @petrklapka