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/lens/group3/lens_reporting·ts - lens app - group 3 lens reporting PDF report should enable curl reporting if the visualization is saved #154957

Closed
kibanamachine opened this issue Apr 13, 2023 · 5 comments
Closed

Failing test: Chrome X-Pack UI Functional Tests.x-pack/test/functional/apps/lens/group3/lens_reporting·ts - lens app - group 3 lens reporting PDF report should enable curl reporting if the visualization is saved #154957

kibanamachine opened this issue Apr 13, 2023 · 5 comments
Assignees
@dej611
Labels
failed-test A test failure on a tracked branch, potentially flaky-test Feature:Lens Team:Visualizations Visualization editors, elastic-charts and infrastructure

Comments

@kibanamachine
Copy link
Contributor

kibanamachine commented Apr 13, 2023 •
edited
Loading

A test failed on a tracked branch

Error: retry.try timeout: Error: retry.try timeout: TimeoutError: Waiting for element to be located By(css selector, [data-test-subj="savedObjectTitle"])
Wait timed out after 10047ms
    at /var/lib/buildkite-agent/builds/kb-n2-4-spot-60b619efde311840/elastic/kibana-on-merge/kibana/node_modules/selenium-webdriver/lib/webdriver.js:929:17
    at runMicrotasks (<anonymous>)
    at processTicksAndRejections (node:internal/process/task_queues:96:5)
    at onFailure (retry_for_success.ts:17:9)
    at retryForSuccess (retry_for_success.ts:59:13)
    at RetryService.try (retry.ts:31:12)
    at Proxy.clickByCssSelector (find.ts:407:5)
    at TestSubjects.click (test_subjects.ts:164:5)
    at test_subjects.ts:264:7
    at runAttempt (retry_for_success.ts:29:15)
    at retryForSuccess (retry_for_success.ts:68:21)
    at RetryService.try (retry.ts:31:12)
    at TestSubjects.setValue (test_subjects.ts:261:12)
    at TimeToVisualizePageObject.setSaveModalValues (time_to_visualize_page.ts:54:5)
    at Object.save (lens_page.ts:704:7)
    at Context.<anonymous> (lens_reporting.ts:115:11)
    at Object.apply (wrap_function.js:73:16)
    at onFailure (retry_for_success.ts:17:9)
    at retryForSuccess (retry_for_success.ts:59:13)
    at RetryService.try (retry.ts:31:12)
    at TestSubjects.setValue (test_subjects.ts:261:12)
    at TimeToVisualizePageObject.setSaveModalValues (time_to_visualize_page.ts:54:5)
    at Object.save (lens_page.ts:704:7)
    at Context.<anonymous> (lens_reporting.ts:115:11)
    at Object.apply (wrap_function.js:73:16)

First failure: CI Build - main
@kibanamachine kibanamachine added the failed-test A test failure on a tracked branch, potentially flaky-test label Apr 13, 2023
@botelastic botelastic bot added the needs-team Issues missing a team label label Apr 13, 2023
@jbudz jbudz added the Team:SharedUX Team label for AppEx-SharedUX (formerly Global Experience) label Apr 13, 2023
@elasticmachine
Copy link
Contributor

Pinging @elastic/appex-sharedux (Team:SharedUX)

@botelastic botelastic bot removed the needs-team Issues missing a team label label Apr 13, 2023
@kibanamachine
Copy link
Contributor Author

New failure: CI Build - main

@petrklapka petrklapka added Team:Visualizations Visualization editors, elastic-charts and infrastructure Feature:Lens labels Apr 17, 2023
@elasticmachine
Copy link
Contributor

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

@petrklapka petrklapka removed the Team:SharedUX Team label for AppEx-SharedUX (formerly Global Experience) label Apr 17, 2023
@Dosant
Copy link
Contributor

Dosant commented Apr 17, 2023

I think this might be a flaky test from #153429 ? @elastic/kibana-visualizations I suggest you take a look at this first and then if there're issues found within reporting we'll try to help

@kibanamachine
Copy link
Contributor Author

New failure: CI Build - main

@dej611 dej611 mentioned this issue Apr 18, 2023
Merged
9 tasks
dej611 added a commit that referenced this issue Apr 18, 2023
@dej611
[Lens] Reenable reporting functional tests (#155118)
0ce4f2d 
## Summary

Fixes #155047, #154958, #154957, #154956, #154955, #154954

Flaky runner with 50 runs:
https://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/2146

### Checklist

Delete any items that are not applicable to this PR.

- [ ] Any text added follows [EUI's writing
guidelines](https://elastic.github.io/eui/#/guidelines/writing), uses
sentence case text and includes [i18n
support](https://github.com/elastic/kibana/blob/main/packages/kbn-i18n/README.md)
- [ ]
[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)
was added for features that require explanation or tutorials
- [ ] [Unit or functional
tests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)
were updated or added to match the most common scenarios
- [ ] Any UI touched in this PR is usable by keyboard only (learn more
about [keyboard accessibility](https://webaim.org/techniques/keyboard/))
- [ ] Any UI touched in this PR does not create any new axe failures
(run axe in browser:
[FF](https://addons.mozilla.org/en-US/firefox/addon/axe-devtools/),
[Chrome](https://chrome.google.com/webstore/detail/axe-web-accessibility-tes/lhdoppojpmngadmnindnejefpokejbdd?hl=en-US))
- [ ] If a plugin configuration key changed, check if it needs to be
allowlisted in the cloud and added to the [docker
list](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker)
- [ ] This renders correctly on smaller devices using a responsive
layout. (You can test this [in your
browser](https://www.browserstack.com/guide/responsive-testing-on-local-server))
- [ ] This was checked for [cross-browser
compatibility](https://www.elastic.co/support/matrix#matrix_browsers)


### Risk Matrix

Delete this section if it is not applicable to this PR.

Before closing this PR, invite QA, stakeholders, and other developers to
identify risks that should be tested prior to the change/feature
release.

When forming the risk matrix, consider some of the following examples
and how they may potentially impact the change:

| Risk | Probability | Severity | Mitigation/Notes |

|---------------------------|-------------|----------|-------------------------|
| Multiple Spaces&mdash;unexpected behavior in non-default Kibana Space.
| Low | High | Integration tests will verify that all features are still
supported in non-default Kibana Space and when user switches between
spaces. |
| Multiple nodes&mdash;Elasticsearch polling might have race conditions
when multiple Kibana nodes are polling for the same tasks. | High | Low
| Tasks are idempotent, so executing them multiple times will not result
in logical error, but will degrade performance. To test for this case we
add plenty of unit tests around this logic and document manual testing
procedure. |
| Code should gracefully handle cases when feature X or plugin Y are
disabled. | Medium | High | Unit tests will verify that any feature flag
or plugin combination still results in our service operational. |
| [See more potential risk
examples](https://github.com/elastic/kibana/blob/main/RISK_MATRIX.mdx) |


### For maintainers

- [ ] This was checked for breaking API changes and was [labeled
appropriately](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)
@dej611 dej611 closed this as completed Apr 18, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@dej611 dej611

Labels
failed-test A test failure on a tracked branch, potentially flaky-test Feature:Lens Team:Visualizations Visualization editors, elastic-charts and infrastructure
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
6 participants
@dej611 @jbudz @Dosant @elasticmachine @kibanamachine @petrklapka