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/ml/anomaly_detection/anomaly_explorer·ts - machine learning anomaly detection anomaly explorer with farequote based multi metric job adds swim lane embeddable to a dashboard #118584

Closed
kibanamachine opened this issue Nov 15, 2021 · 11 comments · Fixed by #118658 or #122247
Assignees
Labels
failed-test A test failure on a tracked branch, potentially flaky-test :ml

Comments

@kibanamachine
Copy link
Contributor

kibanamachine commented Nov 15, 2021

A test failed on a tracked branch

TimeoutError: Waiting until element is enabled
Wait timed out after 10090ms
    at /opt/local-ssd/buildkite/builds/kb-n2-4-a8218bc47b67e6c0/elastic/kibana-hourly/kibana/node_modules/selenium-webdriver/lib/webdriver.js:895:17
    at runMicrotasks (<anonymous>)
    at processTicksAndRejections (node:internal/process/task_queues:96:5) {
  remoteStacktrace: ''
}

First failure: CI Build - main

@kibanamachine kibanamachine added the failed-test A test failure on a tracked branch, potentially flaky-test label Nov 15, 2021
@botelastic botelastic bot added the needs-team Issues missing a team label label Nov 15, 2021
@kibanamachine
Copy link
Contributor Author

New failure: CI Build - main

@elasticmachine
Copy link
Contributor

Pinging @elastic/ml-ui (:ml)

@botelastic botelastic bot removed the needs-team Issues missing a team label label Nov 15, 2021
@mistic
Copy link
Member

mistic commented Nov 15, 2021

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

main/8.1: 6bd5e48
8.0: d417d0a

@pheyos pheyos self-assigned this Nov 16, 2021
@pheyos
Copy link
Member

pheyos commented Nov 16, 2021

From the failure screenshot it seems the dashboard selection didn't work, looking into it.
image

jloleysens added a commit to jloleysens/kibana that referenced this issue Nov 16, 2021
…igrate-away-from-injected-css-js

* 'main' of github.com:elastic/kibana: (221 commits)
  [Reporting] Add log level to config (elastic#118319)
  [Metrics UI] Skip failing waffle chart color palette test (elastic#118527)
  [APM] chore: Unify naming of 'apm/scripts/**/*' with snake_case (elastic#118328)
  skip flaky suites (elastic#99581, elastic#118356, elastic#118474)
  [Alerting] Initial implementation of alerting task `cancel()` (elastic#114289)
  chore(NA): creates pkg_npm_types bazel rule (elastic#116465)
  skip flaky suite (elastic#116892)
  Bump chromedriver to 95.0.0 (elastic#116724)
  [Data visualizer] Improve design of expanded rows (elastic#118125)
  [APM] prefer ECS field names for HTTP and URL (elastic#118485)
  Update query_debugging_in_development_and_production.md (elastic#118491)
  [Uptime] adjust Elastic Synthetics integration functional tests (elastic#118163)
  [kbn/rule-data-utils] add submodules and require public use them (elastic#117963)
  [DOCS] Refresh APM correlation screenshots (elastic#116723) (elastic#118577)
  Handles ns to ms conversion for event loop delay metrics (elastic#118447)
  [Cases] Rename functional tests folder (elastic#118490)
  dummy commit
  skip flaky suite (elastic#118593)
  Improve workpad schema validation (elastic#97838)
  skip flaky suite (elastic#118584)
  ...

# Conflicts:
#	src/plugins/dashboard/public/application/embeddable/viewport/dashboard_viewport.tsx
@kibanamachine
Copy link
Contributor Author

New failure: CI Build - 8.0

mistic added a commit that referenced this issue Nov 16, 2021
@mistic mistic added the v8.0.0 label Nov 16, 2021
@kibanamachine
Copy link
Contributor Author

New failure: CI Build - 8.0

@kibanamachine
Copy link
Contributor Author

New failure: CI Build - 8.0

@kibanamachine
Copy link
Contributor Author

New failure: CI Build - main

@spalger
Copy link
Contributor

spalger commented Dec 28, 2021

@pheyos looks like there's a timeout that might need to be extended?

Error: retry.tryForTime timeout: Error: expected testSubject(mlDashboardSelectionTable loaded) to exist

image

Skipped
8.1/main: 6b7f3df
8.0: de7bb6d

spalger pushed a commit that referenced this issue Dec 28, 2021
spalger pushed a commit that referenced this issue Dec 28, 2021
(cherry picked from commit 6b7f3df)
@pheyos
Copy link
Member

pheyos commented Jan 4, 2022

In the test execution log I can see the following error:

debg browser[INFO] http://localhost:6101/49353/bundles/core/core.entry.js 7:118592 "Detected an unhandled Promise rejection.
Error: The field \"@timestamp\" associated with this object no longer exists in the data view. Please use another field."
warn browser[SEVERE] http://localhost:6101/49353/bundles/plugin/data/kibana/data.plugin.js 0:371378 Uncaught SavedFieldNotFound: The field "@timestamp" associated with this object…xists in the data view. Please use another field.

Not sure where this is coming from and I could reproduce locally so far. Will take a closer look.

@pheyos
Copy link
Member

pheyos commented Jan 4, 2022

It turned out that now we have a couple system dashboards installed by default and filtering the list sometimes seems to fail while the test assumes that after filtering there was only one ML Test dashboard. As a result, the test adds the swim lane visualization to all dashboards and opens the wrong one for validations (which sometimes brings up issues in case the corresponding source data / data view has been modified or removed in another test). I'll adjust the test to be more robust in this area.

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 :ml
Projects
None yet
5 participants