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: Firefox XPack UI Functional Tests.x-pack/test/functional/apps/spaces/enter_space·ts - Spaces app Enter Space allows user to navigate to different spaces, respecting the configured default route #100570

Closed
kibanamachine opened this issue May 25, 2021 · 24 comments · Fixed by #117510, #118043 or #131835
Closed

Failing test: Firefox XPack UI Functional Tests.x-pack/test/functional/apps/spaces/enter_space·ts - Spaces app Enter Space allows user to navigate to different spaces, respecting the configured default route #100570

kibanamachine opened this issue May 25, 2021 · 24 comments · Fixed by #117510, #118043 or #131835
Assignees
@legrego
Labels
failed-test A test failure on a tracked branch, potentially flaky-test impact:medium Addressing this issue will have a medium level of impact on the quality/strength of our product. loe:small Small Level of Effort Team:Security Team focused on: Auth, Users, Roles, Spaces, Audit Logging, and more!

Comments

@kibanamachine
Copy link
Contributor

kibanamachine commented May 25, 2021 •
edited by elasticdog
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="space-avatar-default"])
Wait timed out after 10011ms
    at /dev/shm/workspace/parallel/18/kibana/node_modules/selenium-webdriver/lib/webdriver.js:842:17
    at runMicrotasks (<anonymous>)
    at processTicksAndRejections (internal/process/task_queues.js:93:5)
    at onFailure (/dev/shm/workspace/parallel/18/kibana/test/common/services/retry/retry_for_success.ts:17:9)
    at retryForSuccess (/dev/shm/workspace/parallel/18/kibana/test/common/services/retry/retry_for_success.ts:57:13)
    at Retry.try (/dev/shm/workspace/parallel/18/kibana/test/common/services/retry/retry.ts:32:14)
    at Proxy.clickByCssSelector (/dev/shm/workspace/parallel/18/kibana/test/functional/services/common/find.ts:420:7)
    at TestSubjects.click (/dev/shm/workspace/parallel/18/kibana/test/functional/services/common/test_subjects.ts:109:7)
    at /dev/shm/workspace/parallel/18/kibana/x-pack/test/functional/page_objects/space_selector_page.ts:193:9
    at runAttempt (/dev/shm/workspace/parallel/18/kibana/test/common/services/retry/retry_for_success.ts:27:15)
    at retryForSuccess (/dev/shm/workspace/parallel/18/kibana/test/common/services/retry/retry_for_success.ts:66:21)
    at Retry.try (/dev/shm/workspace/parallel/18/kibana/test/common/services/retry/retry.ts:32:14)
    at SpaceSelectorPage.clickSpaceAvatar (test/functional/page_objects/space_selector_page.ts:191:14)
    at Context.<anonymous> (test/functional/apps/spaces/enter_space.ts:56:7)
    at Object.apply (/dev/shm/workspace/parallel/18/kibana/node_modules/@kbn/test/src/functional_test_runner/lib/mocha/wrap_function.js:73:16)
    at onFailure (/dev/shm/workspace/parallel/18/kibana/test/common/services/retry/retry_for_success.ts:17:9)
    at retryForSuccess (/dev/shm/workspace/parallel/18/kibana/test/common/services/retry/retry_for_success.ts:57:13)
    at Retry.try (/dev/shm/workspace/parallel/18/kibana/test/common/services/retry/retry.ts:32:14)
    at SpaceSelectorPage.clickSpaceAvatar (test/functional/page_objects/space_selector_page.ts:191:14)
    at Context.<anonymous> (test/functional/apps/spaces/enter_space.ts:56:7)
    at Object.apply (/dev/shm/workspace/parallel/18/kibana/node_modules/@kbn/test/src/functional_test_runner/lib/mocha/wrap_function.js:73:16)

First failure: Jenkins Build
@kibanamachine kibanamachine added the failed-test A test failure on a tracked branch, potentially flaky-test label May 25, 2021
@botelastic botelastic bot added the needs-team Issues missing a team label label May 25, 2021
@legrego legrego self-assigned this May 26, 2021
@legrego legrego added the Team:Security Team focused on: Auth, Users, Roles, Spaces, Audit Logging, and more! label May 26, 2021
@elasticmachine
Copy link
Contributor

Pinging @elastic/kibana-security (Team:Security)

@botelastic botelastic bot removed the needs-team Issues missing a team label label May 26, 2021
@legrego legrego mentioned this issue May 26, 2021
Merged
@kibanamachine kibanamachine reopened this May 27, 2021
@kibanamachine
Copy link
Contributor Author

New failure: Jenkins Build

@jportner
Copy link
Contributor

Here are screenshots from the first and second failure:

first-failure
second-failure

They look basically the same, except the second one is using the Amsterdam theme.

Perhaps the fix was incomplete? I'm not sure what next steps would be, just leaving this here for whoever picks it up.

@kibanamachine
Copy link
Contributor Author

New failure: Jenkins Build

@kibanamachine
Copy link
Contributor Author

New failure: Jenkins Build

@legrego
Copy link
Member

legrego commented May 30, 2021

Thanks for the triage @jportner - I'm disappointed my fix didn't work. I ran the flaky test suite about 85 times without any failures, so I was fairly confident in the fix 😐

@kibanamachine
Copy link
Contributor Author

New failure: Jenkins Build

@kibanamachine
Copy link
Contributor Author

New failure: Jenkins Build

mistic added a commit that referenced this issue May 31, 2021
@mistic
skip flaky suite (#100570)
622bf0b
mistic added a commit that referenced this issue May 31, 2021
@mistic
skip flaky suite (#100570)
0434764
@mistic
Copy link
Member

mistic commented May 31, 2021 •
edited by spalger
Loading

The test keeps failing. I've skipped it for now.

master/8.0: 622bf0b
7.x/7.14: 0434764
7.13: 0434764

@kibanamachine
Copy link
Contributor Author

New failure: Jenkins Build

@spalger spalger added v7.14.0 and removed v8.0.0 labels Jun 30, 2021
@spalger
Copy link
Contributor

spalger commented Jun 30, 2021 •
edited
Loading

@elastic/kibana-security this issue was improperly labeled as an 8.0 blocker but is actually skipped in 7.14/7.x, and most recently failed in 7.13, so there is clearly something wrong here (though it's likely not a regression since it appears to happen in 7.13 as well).

Skipped in 7.13 as well 61ce62c

spalger pushed a commit that referenced this issue Jun 30, 2021
@mistic @spalger
skip flaky suite (#100570)
61ce62c 
(cherry picked from commit 0434764)
@jportner
Copy link
Contributor

Removing this as a blocker -- decision took place in a Slack conversation.

CC @legrego @bhavyarm

@jportner jportner removed the blocker label Jul 12, 2021
@kibanamachine
Copy link
Contributor Author

New failure: CI Build - main

@kibanamachine
Copy link
Contributor Author

New failure: CI Build - main

@thomheymann thomheymann mentioned this issue Nov 11, 2021
Merged
@kibanamachine
Copy link
Contributor Author

New failure: CI Build - main

mistic added a commit that referenced this issue Nov 11, 2021
@mistic
skip flaky suites (#100570)
589cf5b
@mistic
Copy link
Member

mistic commented Nov 11, 2021 •
edited
Loading

This test keeps failing and looks flaky. Skipping it for now.

main/8.1: 589cf5b

claudiopro pushed a commit to claudiopro/kibana that referenced this issue Nov 11, 2021
@mistic @claudiopro
skip flaky suites (elastic#100570)
4693f58
fkanout pushed a commit to fkanout/kibana that referenced this issue Nov 17, 2021
@brianseeders @fkanout
skip flaky suite (elastic#100570)
d1de7f9
fkanout pushed a commit to fkanout/kibana that referenced this issue Nov 17, 2021
@mistic @fkanout
skip flaky suites (elastic#100570)
91a1e97
@exalate-issue-sync exalate-issue-sync bot added impact:critical This issue should be addressed immediately due to a critical level of impact on the product. and removed impact:low Addressing this issue will have a low level of impact on the quality/strength of our product. labels Nov 23, 2021
dmlemeshko pushed a commit that referenced this issue Nov 29, 2021
@mistic @dmlemeshko
skip flaky suites (#100570)
279c97e
@jportner
Copy link
Contributor

jportner commented Dec 1, 2021

Not sure why that was closed... reopening

@jportner jportner reopened this Dec 1, 2021
@jportner jportner mentioned this issue Dec 6, 2021
Closed
roeehub pushed a commit to build-security/kibana that referenced this issue Dec 16, 2021
@brianseeders
skip flaky suite (elastic#100570)
b5266fa
roeehub pushed a commit to build-security/kibana that referenced this issue Dec 16, 2021
@mistic
skip flaky suites (elastic#100570)
73d0652
@exalate-issue-sync exalate-issue-sync bot added impact:medium Addressing this issue will have a medium level of impact on the quality/strength of our product. and removed impact:critical This issue should be addressed immediately due to a critical level of impact on the product. labels Feb 10, 2022
@legrego legrego assigned legrego and unassigned thomheymann May 9, 2022
@legrego legrego mentioned this issue May 10, 2022
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@legrego legrego

Labels
failed-test A test failure on a tracked branch, potentially flaky-test impact:medium Addressing this issue will have a medium level of impact on the quality/strength of our product. loe:small Small Level of Effort Team:Security Team focused on: Auth, Users, Roles, Spaces, Audit Logging, and more!
Projects
None yet
Milestone
No milestone
8 participants
@thomheymann @brianseeders @spalger @legrego @mistic @jportner @elasticmachine @kibanamachine