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: Chrome X-Pack UI Functional Tests.x-pack/test/functional/apps/discover/feature_controls/discover_security·ts - discover feature controls security global discover all privileges allow saving via the saved query management component popover with no query loaded #45348

Closed
kibanamachine opened this issue Sep 11, 2019 · 25 comments · Fixed by #57715 or #58218
Assignees
Labels
blocker failed-test A test failure on a tracked branch, potentially flaky-test skipped-test Team:Visualizations Visualization editors, elastic-charts and infrastructure

Comments

@kibanamachine
Copy link
Contributor

kibanamachine commented Sep 11, 2019

A test failed on a tracked branch


        Error: retry.try timeout: Error: expected testSubject(saveQueryForm) to exist
    at TestSubjects.existOrFail (/var/lib/jenkins/workspace/elastic+kibana+7.x/JOB/x-pack-ciGroup3/node/linux-immutable/kibana/test/functional/services/test_subjects.ts:55:15)
    at process._tickCallback (internal/process/next_tick.js:68:7)
    at lastError (/var/lib/jenkins/workspace/elastic+kibana+7.x/JOB/x-pack-ciGroup3/node/linux-immutable/kibana/test/common/services/retry/retry_for_success.ts:28:9)
    at onFailure (/var/lib/jenkins/workspace/elastic+kibana+7.x/JOB/x-pack-ciGroup3/node/linux-immutable/kibana/test/common/services/retry/retry_for_success.ts:68:13)
      

First failure: Jenkins Build

@kibanamachine kibanamachine added the failed-test A test failure on a tracked branch, potentially flaky-test label Sep 11, 2019
@elasticmachine
Copy link
Contributor

Pinging @elastic/kibana-test-triage

@spalger
Copy link
Contributor

spalger commented Sep 11, 2019

Related #44631

@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

@spalger spalger added the Team:Security Team focused on: Auth, Users, Roles, Spaces, Audit Logging, and more! label Jan 8, 2020
@elasticmachine
Copy link
Contributor

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

@kibanamachine
Copy link
Contributor Author

New failure: Jenkins Build

@azasypkin azasypkin added Team:Visualizations Visualization editors, elastic-charts and infrastructure and removed Team:Security Team focused on: Auth, Users, Roles, Spaces, Audit Logging, and more! labels Jan 9, 2020
@elasticmachine
Copy link
Contributor

Pinging @elastic/kibana-app (Team:KibanaApp)

@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

@kibanamachine
Copy link
Contributor Author

New failure: Jenkins Build

@kibanamachine
Copy link
Contributor Author

New failure: Jenkins Build

jbudz added a commit to jbudz/kibana that referenced this issue Feb 13, 2020
Several tests using the
savedQueryManagementComponent.saveNewQueryMissingOrFail method have been
failing with 'waiting for element'.  Temproary adding a skip for tests
using this method

Related elastic#50018
Related elastic#44631
Related elastic#45348
@jbudz jbudz mentioned this issue Feb 13, 2020
7 tasks
spalger pushed a commit that referenced this issue Feb 13, 2020
Several tests using the
savedQueryManagementComponent.saveNewQueryMissingOrFail method have been
failing with 'waiting for element'.  Temproary adding a skip for tests
using this method

Related #50018
Related #44631
Related #45348
@spalger
Copy link
Contributor

spalger commented Feb 13, 2020

Skipped:

master: 431a1e9
7.x/7.7: d97c88b

master: 8aa718d
7.x/7.7: 4841bfb

spalger pushed a commit that referenced this issue Feb 13, 2020
Several tests using the
savedQueryManagementComponent.saveNewQueryMissingOrFail method have been
failing with 'waiting for element'.  Temproary adding a skip for tests
using this method

Related #50018
Related #44631
Related #45348

(cherry picked from commit 431a1e9)
@spalger spalger removed the blocker label Feb 19, 2020
@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

@spalger
Copy link
Contributor

spalger commented Feb 20, 2020

Latest failure on 7.x: https://kibana-ci.elastic.co/job/elastic+kibana+7.x/3063/testReport/junit/Chrome%20X-Pack%20UI%20Functional%20Tests/x-pack_test_functional_apps_discover_feature_controls_discover_security%C2%B7ts/Kibana_Pipeline___kibana_xpack_agent___discover_feature_controls_security_global_discover_all_privileges_allow_saving_via_the_saved_query_management_component_popover_with_no_query_loaded/

[00:04:39]                   │ debg TestSubjects.exists(saveQueryForm)
[00:04:39]                   │ debg Find.existsByDisplayedByCssSelector('[data-test-subj="saveQueryForm"]') with timeout=120000
[00:04:42]                   │ debg --- retry.tryForTime error: [data-test-subj="saveQueryForm"] is not displayed
[00:04:45]                   │ debg --- retry.tryForTime failed again with the same message...
[00:04:48]                   │ debg --- retry.tryForTime failed again with the same message...
[00:04:51]                   │ debg --- retry.tryForTime failed again with the same message...
[00:04:54]                   │ debg --- retry.tryForTime failed again with the same message...
[00:04:57]                   │ debg --- retry.tryForTime failed again with the same message...
[00:05:00]                   │ debg --- retry.tryForTime failed again with the same message...
[00:05:03]                   │ debg --- retry.tryForTime failed again with the same message...
[00:05:06]                   │ debg --- retry.tryForTime failed again with the same message...
[00:05:09]                   │ debg --- retry.tryForTime failed again with the same message...
[00:05:12]                   │ debg --- retry.tryForTime failed again with the same message...
[00:05:15]                   │ debg --- retry.tryForTime failed again with the same message...
[00:05:18]                   │ debg --- retry.tryForTime failed again with the same message...
[00:05:21]                   │ debg --- retry.tryForTime failed again with the same message...
[00:05:24]                   │ debg --- retry.tryForTime failed again with the same message...
[00:05:27]                   │ debg --- retry.tryForTime failed again with the same message...
[00:05:30]                   │ debg --- retry.tryForTime failed again with the same message...
[00:05:33]                   │ debg --- retry.tryForTime failed again with the same message...
[00:05:37]                   │ debg --- retry.tryForTime failed again with the same message...
[00:05:40]                   │ debg --- retry.tryForTime failed again with the same message...
[00:05:43]                   │ debg --- retry.tryForTime failed again with the same message...
[00:05:46]                   │ debg --- retry.tryForTime failed again with the same message...
[00:05:49]                   │ debg --- retry.tryForTime failed again with the same message...
[00:05:52]                   │ debg --- retry.tryForTime failed again with the same message...
[00:05:55]                   │ debg --- retry.tryForTime failed again with the same message...
[00:05:58]                   │ debg --- retry.tryForTime failed again with the same message...
[00:06:01]                   │ debg --- retry.tryForTime failed again with the same message...
[00:06:04]                   │ debg --- retry.tryForTime failed again with the same message...
[00:06:07]                   │ debg --- retry.tryForTime failed again with the same message...
[00:06:10]                   │ debg --- retry.tryForTime failed again with the same message...
[00:06:13]                   │ debg --- retry.tryForTime failed again with the same message...
[00:06:16]                   │ debg --- retry.tryForTime failed again with the same message...
[00:06:19]                   │ debg --- retry.tryForTime failed again with the same message...
[00:06:22]                   │ debg --- retry.tryForTime failed again with the same message...
[00:06:25]                   │ debg --- retry.tryForTime failed again with the same message...
[00:06:28]                   │ debg --- retry.tryForTime failed again with the same message...
[00:06:31]                   │ debg --- retry.tryForTime failed again with the same message...
[00:06:34]                   │ debg --- retry.tryForTime failed again with the same message...
[00:06:37]                   │ debg --- retry.tryForTime failed again with the same message...
[00:06:40]                   │ debg --- retry.tryForTime failed again with the same message...
[00:06:41]                   │ debg --- retry.try error: expected testSubject(saveQueryForm) to exist

Seems to me the retry is in the wrong place based on this log.

spalger added a commit that referenced this issue Feb 20, 2020
spalger added a commit that referenced this issue Feb 20, 2020
(cherry picked from commit ba983f0)
@spalger
Copy link
Contributor

spalger commented Feb 20, 2020

skipped

master: ba983f0
7.x/7.7: 0176629

@kibanamachine
Copy link
Contributor Author

New failure: Jenkins Build

mbondyra added a commit to mbondyra/kibana that referenced this issue Feb 20, 2020
* master: (136 commits)
  [Visualize] Remove legacy appState in visualize (elastic#57330)
  Use static time for tsvb rollup test (elastic#57701)
  [SIEM] Fix ResizeObserver polyfill (elastic#58046)
  [SIEM][Detection Engine] Fixes return codes where some were rule_id instead of id
  skip flaky suite (elastic#56816)
  skip flaky suite (elastic#58059)
  skip flaky suite (elastic#45348)
  migrates notification server routes to NP (elastic#57906)
  Moved all of the show/hide toggles outside of ordered lists. (elastic#57163)
  [APM] NP Migration - Moves plugin server files out of legacy (elastic#57532)
  [Maps][Telemetry] Migrate Maps telemetry to NP (elastic#55055)
  Embeddable add panel examples (elastic#57319)
  Fix useRequest to support query change (elastic#57723)
  Allow custom paths in plugin generator (elastic#57766)
  [SIEM][Case] Merge header components (elastic#57816)
  [ML] New Platform server shim: update job audit messages routes (elastic#57925)
  [kbn/optimizer] emit success event from reducer when all bundles cached (elastic#57945)
  [APM] Don’t include UI filters when fetching a specific transaction (elastic#57934)
  Upgrade yargs (elastic#57720)
  skip flaky suite (elastic#57762) (elastic#57997) (elastic#57998)
  ...

# Conflicts:
#	src/plugins/advanced_settings/public/management_app/components/field/__snapshots__/field.test.tsx.snap
#	src/plugins/advanced_settings/public/management_app/components/field/field.tsx
#	x-pack/plugins/translations/translations/ja-JP.json
#	x-pack/plugins/translations/translations/zh-CN.json
@flash1293 flash1293 self-assigned this Feb 21, 2020
@kibanamachine kibanamachine reopened this Feb 26, 2020
@kibanamachine
Copy link
Contributor Author

New failure: Jenkins Build

@flash1293
Copy link
Contributor

Closing again, haven't merged the backport yet: #58581 (comment)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
blocker failed-test A test failure on a tracked branch, potentially flaky-test skipped-test Team:Visualizations Visualization editors, elastic-charts and infrastructure
Projects
None yet
5 participants