-
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
visualize app point series custom labels and axis titles should preserve saved axis titles after a vis is saved and reopened #27905
Comments
Pinging @elastic/kibana-app |
Failing on master and estf somewhat regularly looks like: Standard Output:
|
Screenshot: Html: |
I haven't been able to reproduce this failure when running tests locally, but I do have some suspicions about what's causing it:
I noticed that usually after we save a vis, we typically call So I opened #28272 to add that change and run CI a few times to see if it helps. So far that test has had no failures, but without being able to reliably reproduce, I'm sort of flying blind and I'm not 100% confident that we can officially mark this as resolved. More info in the PR. |
It looks like this might be what Tim was referring to in this issue that I closed yesterday: #19750 . "Fails to navigate". This is what I think is going on. When you save a new visualization the url actually changes. It looks like a soft reload, not a hard reload, but I wonder if in that routing the link won't work if you click it at a certain time. Maybe if we changed
to use I'd suggest doing what dashboard does too, and add the "expect" part. This will at least be a better error message, so we actually see that the real problem is that the navigation failed to occur.
Even dashboard isn't using the
That check to see if the user is on the landing page waits up to 5 seconds to finally return false, so it's like adding in a 5 second sleep. This probably ensure the dashboard breadcrumb link is clickable by the time we get there. So @lukeelmers - your solution to wait for the toast to go away would probably solve it, but in a very subtle way. I think we should try to put the fix inside either |
Thanks for the advice @stacey-gammon - Waiting for the toast to go away felt like an icky "fix" to me too. The I went ahead and pushed an update to the PR based on your suggestions... I'll re-run CI a couple times to see how it looks. Still not able to reproduce locally, but either way this feels as if it is moving in a better direction! |
This test is still failing over last seven days on 6.6 and 6.x branches. |
The PR that's in progress for this stalled last week after a couple of failed attempts -- will revisit again this week to see if I can sort anything out. |
This test is fixed in #31446. Waiting for it to merge. |
Error: retry.try timeout: Error: retry.try timeout: [POST http://localhost:9515/session/7182a7141b2e9ea17c9929de24492679/element / {"using":"partial link text","value":"Visualization Point Series Test"}] no such element: Unable to locate element: {"method":"partial link text","selector":"Visualization Point Series Test"}
(Session info: headless chrome=71.0.3578.98)
(Driver info: chromedriver=2.42.591071 (0b695ff80972cc1a65a5cd643186d2ae582cd4ac),platform=Linux 4.15.0-1026-gcp x86_64)
at Server._post (test/functional/services/remote/verbose_remote_logging.js:34:21)
at runRequest (node_modules/leadfoot/Session.js:92:40)
at node_modules/leadfoot/Session.js:113:39
at new Promise (node_modules/dojo/_debug/Promise.ts:411:4)
at Session._post (node_modules/leadfoot/Session.js:67:10)
at Session.find (node_modules/leadfoot/Session.js:1328:15)
at Command. (node_modules/leadfoot/Command.js:42:36)
at node_modules/dojo/_debug/Promise.ts:393:16
at run (node_modules/dojo/_debug/Promise.ts:237:8)
at node_modules/dojo/_debug/nextTick.ts:44:4
at process._tickCallback (internal/process/next_tick.js:61:11)
at Command.find (node_modules/leadfoot/Command.js:23:10)
at Command.prototype.(anonymous function) [as findByPartialLinkText] (node_modules/leadfoot/lib/strategies.js:29:16)
at _ensureElementWithTimeout (test/functional/services/find.js:203:36)
at retry.try (test/functional/services/find.js:76:33)
at runAttempt (test/common/services/retry/retry_for_success.js:39:21)
at retryForSuccess (test/common/services/retry/retry_for_success.js:67:37)
at lastError (test/common/services/retry/retry_for_success.js:29:9)
at retryForSuccess (test/common/services/retry/retry_for_success.js:63:13)
at lastError (test/common/services/retry/retry_for_success.js:29:9)
at retryForSuccess (test/common/services/retry/retry_for_success.js:63:13)
Branches: 6.5, 6.6, 6.x, master
The text was updated successfully, but these errors were encountered: