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.

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

dashboard app using current data dashboard query bar causes panels to reload when refresh is clicked #39212

Closed
liza-mae opened this issue Jun 18, 2019 · 11 comments
Assignees
Labels
failed-test A test failure on a tracked branch, potentially flaky-test Feature:Dashboard Dashboard related features Team:Visualizations Visualization editors, elastic-charts and infrastructure test_ui_functional test test-cloud test-failure-flaky

Comments

@liza-mae
Copy link
Contributor

✖ fail: "dashboard app using current data dashboard query bar causes panels to reload when refresh is clicked"
18:06:12 │ [GET http://localhost:9515/session/ff618cfe7fa170807f09ba6bb8cf2ad0/element/0.7831911331657162-11/displayed] stale element reference: element is not attached to the page document
18:06:12 │ (Session info: headless chrome=74.0.3729.131)
18:06:12 │ (Driver info: chromedriver=74.0.3729.6 (255758eccf3d244491b8a1317aa76e1ce10d57e9-refs/branch-heads/3729@{#29}),platform=Linux 4.16.13-200.fc27.x86_64 x86_64)
18:06:12 │ at Server._get (test/functional/services/remote/verbose_remote_logging.js:34:21)
18:06:12 │ at runRequest (node_modules/leadfoot/Session.js:92:40)
18:06:12 │ at getFinalValue (node_modules/dojo/_debug/Promise.ts:462:22)
18:06:12 │ at node_modules/dojo/_debug/Promise.ts:478:11
18:06:12 │ at node_modules/dojo/_debug/Promise.ts:393:16
18:06:12 │ at runCallbacks (node_modules/dojo/_debug/Promise.ts:11:12)
18:06:12 │ at node_modules/dojo/_debug/Promise.ts:317:5
18:06:12 │ at run (node_modules/dojo/_debug/Promise.ts:237:8)
18:06:12 │ at node_modules/dojo/_debug/nextTick.ts:44:4
18:06:12 │ at process._tickCallback (internal/process/next_tick.js:61:11)

Version: 6.8

@liza-mae liza-mae added test test_ui_functional Team:Visualizations Visualization editors, elastic-charts and infrastructure failed-test A test failure on a tracked branch, potentially flaky-test test-cloud labels Jun 18, 2019
@elasticmachine
Copy link
Contributor

Pinging @elastic/kibana-app

@elasticmachine
Copy link
Contributor

Pinging @elastic/kibana-test-triage

@liza-mae
Copy link
Contributor Author

✖ fail: "dashboard app using current data dashboard query bar causes panels to reload when refresh is clicked"
15:49:22 │ StaleElementReferenceError: stale element reference: element is not attached to the page document
15:49:22 │ (Session info: headless chrome=75.0.3770.142)
15:49:22 │ (Driver info: chromedriver=75.0.3770.90 (a6dcaf7e3ec6f70a194cc25e8149475c6590e025-refs/branch-heads/3770@{#1003}),platform=Linux 4.16.13-200.fc27.x86_64 x86_64)
15:49:22 │ at Object.checkLegacyResponse (node_modules/selenium-webdriver/lib/error.js:585:15)
15:49:22 │ at parseHttpResponse (node_modules/selenium-webdriver/lib/http.js:551:13)
15:49:22 │ at Executor.execute (node_modules/selenium-webdriver/lib/http.js:486:26)
15:49:22 │ at process._tickCallback (internal/process/next_tick.js:68:7)

Version: 7.3

@liza-mae
Copy link
Contributor Author

dashboard app using current data dashboard query bar causes panels to reload when refresh is clicked

@liza-mae
Copy link
Contributor Author

└- ✖ fail: "dashboard app using current data dashboard query bar causes panels to reload when refresh is clicked"
│ StaleElementReferenceError: stale element reference: element is not attached to the page document
│ (Session info: headless chrome=77.0.3865.90)
│ (Driver info: chromedriver=77.0.3865.40 (f484704e052e0b556f8030b65b953dce96503217-refs/branch-heads/3865@{#442}),platform=Linux 4.15.0-58-generic x86_64)
│ at Object.checkLegacyResponse (node_modules/selenium-webdriver/lib/error.js:585:15)
│ at parseHttpResponse (node_modules/selenium-webdriver/lib/http.js:551:13)
│ at Executor.execute (node_modules/selenium-webdriver/lib/http.js:486:26)
│ at process._tickCallback (internal/process/next_tick.js:68:7)

Version: 7.4

@majagrubic
Copy link
Contributor

By the message of it, it sounds like there was an attempt to interact with an element that's not in the DOM anymore, but it doesn't say which element.

@majagrubic
Copy link
Contributor

This is the test:

it('causes panels to reload when refresh is clicked', async () => {

From what I can tell, the test is interacting with 3 elements:

  1. query bar
  2. pie chart
  3. discover column headers

Interactions with both the query bar and pie chart have retry options:
Query bar:

await testSubjects.click('querySubmitButton');

(as part of the testSubjects)
Pie chart:
await retry.try(async () => {

@majagrubic
Copy link
Contributor

majagrubic commented Feb 24, 2020

discover table headers also has a retry, which I just confirmed locally:

debg Find.allByCssSelector('[data-test-subj="docTableHeaderField"]') with timeout=10000
debg --- retry.try error: stale element reference: element is not attached to the page document
debg TestSubjects.findAll(docTableHeaderField)
debg Find.allByCssSelector('[data-test-subj="docTableHeaderField"]') with timeout=10000

Looks like docTableHeaderField was not found in the first try, but was found in the subsequent try.

@majagrubic
Copy link
Contributor

But according to that screenshot, the test failed because pie chart was rendered with 4 slices, instead of not being rendered at all. This is the expected final state of the test:
dashboard app using current data dashboard query bar causes panels to reload when refresh is clicked

So I wonder if the error couldn't be found, retry took care of it and then it failed because pie chart wasn't given enough time to reload.

@majagrubic
Copy link
Contributor

We did a bunch of work in state management for the dashboard. So if there was a bug where pie chart wasn't rendered properly because of state not updating, it was likely fixed.

@timroes
Copy link
Contributor

timroes commented Feb 24, 2020

It seems this test was never skipped, and didn't fail on any available past runs in CI, so I'd close this, since as Maja pointed out, we've had a lot of changes since 7.4, that could have influenced that.

@timroes timroes closed this as completed Feb 24, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
failed-test A test failure on a tracked branch, potentially flaky-test Feature:Dashboard Dashboard related features Team:Visualizations Visualization editors, elastic-charts and infrastructure test_ui_functional test test-cloud test-failure-flaky
Projects
None yet
Development

No branches or pull requests

4 participants