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

Failing test: X-Pack Endpoint Functional Tests.x-pack/test/security_solution_endpoint/apps/endpoint/policy_details·ts - endpoint When on the Endpoint Policy Details Page and the save button is clicked should have cleared the advanced section when the user deletes the value #92567

Closed
kibanamachine opened this issue Feb 24, 2021 · 39 comments
Assignees
Labels
failed-test A test failure on a tracked branch, potentially flaky-test Team:Defend Workflows “EDR Workflows” sub-team of Security Solution Team: SecuritySolution Security Solutions Team working on SIEM, Endpoint, Timeline, Resolver, etc. Team:SIEM

Comments

@kibanamachine
Copy link
Contributor

kibanamachine commented Feb 24, 2021

A test failed on a tracked branch

ElementClickInterceptedError: element click intercepted: Element <button class="euiButton euiButton--primary euiButton--fill" type="button" data-test-subj="policyDetailsSaveButton">...</button> is not clickable at point (1521, 972). Other element would receive the click: <div class="euiToast euiToast--success euiGlobalToastListItem euiGlobalToastListItem-isDismissed" id="0">...</div>
  (Session info: headless chrome=88.0.4324.182)
    at Object.throwDecodedError (/dev/shm/workspace/kibana/node_modules/selenium-webdriver/lib/error.js:550:15)
    at parseHttpResponse (/dev/shm/workspace/kibana/node_modules/selenium-webdriver/lib/http.js:565:13)
    at Executor.execute (/dev/shm/workspace/kibana/node_modules/selenium-webdriver/lib/http.js:491:26)
    at runMicrotasks (<anonymous>)
    at processTicksAndRejections (internal/process/task_queues.js:93:5)
    at Task.exec (/dev/shm/workspace/parallel/16/kibana/test/functional/services/remote/prevent_parallel_calls.ts:29:22) {
  remoteStacktrace: '#0 0x55bc50007199 <unknown>\n'
}

First failure: Jenkins Build

@kibanamachine kibanamachine added the failed-test A test failure on a tracked branch, potentially flaky-test label Feb 24, 2021
@kibanamachine
Copy link
Contributor Author

New failure: Jenkins Build

@kibanamachine
Copy link
Contributor Author

New failure: Jenkins Build

@kibanamachine
Copy link
Contributor Author

New failure: Jenkins Build

@kibanamachine
Copy link
Contributor Author

New failure: Jenkins Build

@brianseeders
Copy link
Contributor

brianseeders commented Feb 24, 2021

Skipped

master: d941763
7.x/7.13: 84b5b68

@elasticmachine
Copy link
Contributor

Pinging @elastic/siem (Team:SIEM)

@brianseeders
Copy link
Contributor

@elastic/security-solution

@kibanamachine
Copy link
Contributor Author

New failure: Jenkins Build

@kevinlog
Copy link
Contributor

@parkiino I think this test failure has to do with the new sticky bar for policy. Judging from error, we need to wait until the toaster is gone in the UI before clicking save again. Can you check?

@kibanamachine
Copy link
Contributor Author

New failure: Jenkins Build

@kibanamachine
Copy link
Contributor Author

New failure: Jenkins Build

@spalger
Copy link
Contributor

spalger commented Feb 24, 2021

Starting to see failures on 7.x too, so skipping there

spalger pushed a commit that referenced this issue Feb 24, 2021
(cherry picked from commit d941763)
@paul-tavares
Copy link
Contributor

@parkiino (@kevinlog ) instead of waiting for the toast to be "gone", just check for it (if not yet) and close it. Then wait for it to disappear (actually close out). then we can click save again.

@paul-tavares
Copy link
Contributor

Also - strange that this did not fail in CI during PR review. I'm guessing a timing issue

@parkiino
Copy link
Contributor

@paul-tavares i think it did actually fail during one of the builds, Kevin pointed it out once, but since it passed on the other builds I thought maybe it was a mistake. I'll probably do what you suggested though Paul and just close it out if it does exists.

@parkiino
Copy link
Contributor

parkiino commented Mar 1, 2021

#92919

@kibanamachine
Copy link
Contributor Author

New failure: Jenkins Build

@MindyRS MindyRS added the Team: SecuritySolution Security Solutions Team working on SIEM, Endpoint, Timeline, Resolver, etc. label Sep 22, 2021
@kibanamachine
Copy link
Contributor Author

New failure: CI Build - main

@kibanamachine
Copy link
Contributor Author

New failure: CI Build - 8.0

mistic added a commit that referenced this issue Nov 29, 2021
mistic added a commit that referenced this issue Nov 29, 2021
@kibanamachine
Copy link
Contributor Author

New failure: CI Build - 8.1

mistic added a commit that referenced this issue Feb 28, 2022
mistic added a commit that referenced this issue Feb 28, 2022
@mistic
Copy link
Member

mistic commented Feb 28, 2022

Skipped.

main: 865c351
8.1: e910bcd

@kevinlog
Copy link
Contributor

PR: #126458

lucasfcosta pushed a commit to lucasfcosta/kibana that referenced this issue Mar 2, 2022
@kevinlog
Copy link
Contributor

with the PR added above, I haven't seen this test fail for a few weeks. Going to close.

@kibanamachine
Copy link
Contributor Author

New failure: CI Build - main

mistic added a commit that referenced this issue Aug 29, 2022
@mistic
Copy link
Member

mistic commented Aug 29, 2022

Skipped.

main: f1c0985

@kevinlog
Copy link
Contributor

closing with this PR: #139660

Mpdreamz pushed a commit to Mpdreamz/kibana that referenced this issue Sep 6, 2022
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 Team:Defend Workflows “EDR Workflows” sub-team of Security Solution Team: SecuritySolution Security Solutions Team working on SIEM, Endpoint, Timeline, Resolver, etc. Team:SIEM
Projects
None yet
Development

No branches or pull requests

9 participants