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: Chrome X-Pack UI Plugin Functional Tests.x-pack/test/plugin_functional/test_suites/resolver - Resolver test app when the user is interacting with the node with ID: secondChild when the user hovers over the primary button when the user has clicked the primary button (which selects the node.) should render as expected #87425

Open
kibanamachine opened this issue Jan 6, 2021 · 15 comments
Open

Failing test: Chrome X-Pack UI Plugin Functional Tests.x-pack/test/plugin_functional/test_suites/resolver - Resolver test app when the user is interacting with the node with ID: secondChild when the user hovers over the primary button when the user has clicked the primary button (which selects the node.) should render as expected #87425

kibanamachine opened this issue Jan 6, 2021 · 15 comments
Labels
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:Threat Hunting:Investigations Security Solution Investigations Team Team:Threat Hunting Security Solution Threat Hunting Team v8.6.0

Comments

@kibanamachine
Copy link
Contributor

kibanamachine commented Jan 6, 2021 •
edited
Loading

A test failed on a tracked branch

Error: expected 0.09689814814814815 to be below 0.09
    at Assertion.assert (/dev/shm/workspace/parallel/4/kibana/packages/kbn-expect/expect.js:100:11)
    at Assertion.lessThan.Assertion.below (/dev/shm/workspace/parallel/4/kibana/packages/kbn-expect/expect.js:336:8)
    at Function.lessThan (/dev/shm/workspace/parallel/4/kibana/packages/kbn-expect/expect.js:531:15)
    at Context.<anonymous> (test/plugin_functional/test_suites/resolver/index.ts:119:23)
    at Object.apply (/dev/shm/workspace/parallel/4/kibana/packages/kbn-test/src/functional_test_runner/lib/mocha/wrap_function.js:84:16)

First failure: Jenkins Build
@kibanamachine kibanamachine added the failed-test A test failure on a tracked branch, potentially flaky-test label Jan 6, 2021
@kibanamachine
Copy link
Contributor Author

New failure: Jenkins Build

@kibanamachine
Copy link
Contributor Author

New failure: Jenkins Build

1 similar comment
@kibanamachine
Copy link
Contributor Author

New failure: Jenkins Build

@spalger spalger added the Team: SecuritySolution Security Solutions Team working on SIEM, Endpoint, Timeline, Resolver, etc. label Jan 6, 2021
@spalger
Copy link
Contributor

spalger commented Jan 6, 2021

This test failed 34 times all of the sudden starting late in the day yesterday across master and PRs.

image

It didn't keep that failure rate up though so I'm assuming this was fixed by someone on the @elastic/elastic-security-solution team who didn't know about this issue. Can someone please confirm?

@kibanamachine
Copy link
Contributor Author

New failure: Jenkins Build

spalger added a commit that referenced this issue Jan 6, 2021
@spalger
skip flaky suite (#87425)
316346a
spalger added a commit that referenced this issue Jan 6, 2021
@spalger
skip flaky suite (#87425)
8f3f278 
(cherry picked from commit 316346a)
@spalger
Copy link
Contributor

spalger commented Jan 6, 2021 •
edited
Loading

Alright, looks like I was wrong. Skipping in master and 7.x. I suspect that bb3659c is having some unexpected effects.

master: 316346a
7.x: 8f3f278

cc @michaelolo24

@michaelolo24
Copy link
Contributor

michaelolo24 commented Jan 6, 2021 •
edited
Loading

Taking a look, thanks @spalger!

@kibanamachine
Copy link
Contributor Author

New failure: Jenkins Build

1 similar comment
@kibanamachine
Copy link
Contributor Author

New failure: Jenkins Build

@michaelolo24
Copy link
Contributor

michaelolo24 commented Jan 6, 2021 •
edited
Loading

Running the flaky test runner right now to test. Figure these are coming from there Actually, take that back the test runner wouldn't trigger these failures. Anyways I made some updates and hopefully once my flaky test runner run is complete we should be good to go

@kibanamachine
Copy link
Contributor Author

New failure: Jenkins Build

@MadameSheema MadameSheema added the Team:Threat Hunting Security Solution Threat Hunting Team label Jan 15, 2021
@kibanamachine kibanamachine reopened this Nov 8, 2022
@kibanamachine
Copy link
Contributor Author

New failure: CI Build - main

@kibanamachine
Copy link
Contributor Author

New failure: CI Build - main

@jbudz
Copy link
Member

jbudz commented Nov 8, 2022

/skip

jbudz added a commit that referenced this issue Nov 9, 2022
@jbudz
skip flaky suite. #87425, #133907, #144820, #144861
c0f9eac
@jbudz
Copy link
Member

jbudz commented Nov 9, 2022

Skipped

main: c0f9eac

@MadameSheema MadameSheema added the Team:Threat Hunting:Investigations Security Solution Investigations Team label Nov 9, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
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:Threat Hunting:Investigations Security Solution Investigations Team Team:Threat Hunting Security Solution Threat Hunting Team v8.6.0
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
6 participants
@spalger @jbudz @michaelolo24 @PhilippeOberti @MadameSheema @kibanamachine