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: X-Pack Endpoint Functional Tests.x-pack/test/security_solution_endpoint/apps/endpoint/resolver·ts - endpoint Endpoint Event Resolver Resolver Tree events Check Related Events for event.registry Node #85106

Closed
kibanamachine opened this issue Dec 6, 2020 · 5 comments
Closed

Failing test: X-Pack Endpoint Functional Tests.x-pack/test/security_solution_endpoint/apps/endpoint/resolver·ts - endpoint Endpoint Event Resolver Resolver Tree events Check Related Events for event.registry Node #85106

kibanamachine opened this issue Dec 6, 2020 · 5 comments
Labels
blocker failed-test A test failure on a tracked branch, potentially flaky-test skipped-test Team: SecuritySolution Security Solutions Team working on SIEM, Endpoint, Timeline, Resolver, etc. Team:SIEM Team:Threat Hunting Security Solution Threat Hunting Team v7.11.0 v8.0.0

Comments

@kibanamachine
Copy link
Contributor

kibanamachine commented Dec 6, 2020 •
edited
Loading

A test failed on a tracked branch

ElementNotInteractableError: element not interactable
  (Session info: headless chrome=87.0.4280.88)
    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/3/kibana/test/functional/services/remote/prevent_parallel_calls.ts:40:22) {
  remoteStacktrace: '#0 0x5569784e1e79 <unknown>\n'
}

First failure: Jenkins Build
@kibanamachine kibanamachine added the failed-test A test failure on a tracked branch, potentially flaky-test label Dec 6, 2020
@azasypkin azasypkin added Team: SecuritySolution Security Solutions Team working on SIEM, Endpoint, Timeline, Resolver, etc. Team:SIEM triage_needed labels Dec 7, 2020
@elasticmachine
Copy link
Contributor

Pinging @elastic/siem (Team:SIEM)

@kibanamachine
Copy link
Contributor Author

New failure: Jenkins Build

@mistic
Copy link
Member

mistic commented Dec 7, 2020

Skipped via #85085 (comment)

@MadameSheema MadameSheema added the Team:Threat Hunting Security Solution Threat Hunting Team label Jan 18, 2021
@MadameSheema
Copy link
Member

@jonathan-buttner @kqualters-elastic @michaelolo24 @XavierM these tests are skipped from December. Let's fix it or delete it.

@jonathan-buttner jonathan-buttner mentioned this issue Mar 10, 2021
Merged
@jonathan-buttner
Copy link
Contributor

Removed the tests

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
blocker failed-test A test failure on a tracked branch, potentially flaky-test skipped-test Team: SecuritySolution Security Solutions Team working on SIEM, Endpoint, Timeline, Resolver, etc. Team:SIEM Team:Threat Hunting Security Solution Threat Hunting Team v7.11.0 v8.0.0
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
6 participants
@azasypkin @mistic @elasticmachine @MadameSheema @kibanamachine @jonathan-buttner