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/data_frame_analytics/outlier_detection_creation·ts - machine learning data frame analytics outlier detection creation iowa house prices edits the analytics job and displays it correctly in the job list #94854

Closed
kibanamachine opened this issue Mar 17, 2021 · 15 comments · Fixed by #91473
Labels
failed-test A test failure on a tracked branch, potentially flaky-test :ml won't fix

Comments

@kibanamachine
Copy link
Contributor

kibanamachine commented Mar 17, 2021

A test failed on a tracked branch

Error: Color stats for canvas element should be within tolerance. Expected: '[{"key":"#000000","value":91},{"key":"#6A717D","value":2},{"key":"#98A2B3","value":1},{"key":"#F5F7FA","value":2},{"key":"#D3DAE6","value":1}]' (got '[{"key":"#000000","value":91,"withinTolerance":true},{"key":"#F5F7FA","value":2,"withinTolerance":true},{"key":"#D3DAE6","value":1,"withinTolerance":true},{"key":"#69707D","value":1,"withinTolerance":false}]')
    at Assertion.assert (/dev/shm/workspace/parallel/12/kibana/node_modules/@kbn/expect/expect.js:100:11)
    at Assertion.eql (/dev/shm/workspace/parallel/12/kibana/node_modules/@kbn/expect/expect.js:244:8)
    at AnalyticsCanvasElement.assertCanvasElement (test/functional/services/ml/data_frame_analytics_canvas_element.ts:33:67)
    at runMicrotasks (<anonymous>)
    at processTicksAndRejections (internal/process/task_queues.js:93:5)
    at Context.<anonymous> (test/functional/apps/ml/data_frame_analytics/outlier_detection_creation.ts:260:11)
    at Object.apply (/dev/shm/workspace/parallel/12/kibana/node_modules/@kbn/test/src/functional_test_runner/lib/mocha/wrap_function.js:73:16) {
  actual: 'false',
  expected: 'true',
  showDiff: true
}

First failure: Jenkins Build

@kibanamachine kibanamachine added the failed-test A test failure on a tracked branch, potentially flaky-test label Mar 17, 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 added a commit that referenced this issue Mar 17, 2021
@spalger
Copy link
Contributor

spalger commented Mar 17, 2021

@walterra is working on updating this code, and these tests were passing fine in the v8 update PR, but I'm going to skip for now and let him unskip them in #91473

master/8.0: 3ec9a17

@elasticmachine
Copy link
Contributor

Pinging @elastic/ml-ui (:ml)

@kibanamachine
Copy link
Contributor Author

New failure: CI Build - 7.17

@kibanamachine
Copy link
Contributor Author

New failure: CI Build - 7.17

@spalger
Copy link
Contributor

spalger commented Mar 23, 2022

@walterra any idea why this might still be failing in 7.17?

@pheyos
Copy link
Member

pheyos commented Apr 27, 2022

It's a different problem this time. In the failure screenshot we can see unexpected error toasts that are blocking other UI components:
image

@pheyos
Copy link
Member

pheyos commented Apr 27, 2022

Looks like this failure didn't occur anymore in the last 4 weeks. Closing for now.

@kibanamachine
Copy link
Contributor Author

New failure: CI Build - 7.17

@tylersmalley
Copy link
Contributor

tylersmalley commented Sep 28, 2022

This was failing on consecutive runs on the 7.17 branch.

@kibanamachine
Copy link
Contributor Author

Skipped

7.17: e40cdc4

@peteharverson
Copy link
Contributor

Removing the blocker label as outlier jobs can be created successfully in manual testing.

@peteharverson
Copy link
Contributor

These tests were fixed with some improvements for 8.x but the fixes cannot easily be backported to 7.17. Having discussed with @pheyos , we have decided it is not worth spending considerable time to fix on 7.17 so will keep them skipped on 7.17 and close as won't fix.

@peteharverson peteharverson closed this as not planned Won't fix, can't repro, duplicate, stale Aug 22, 2023
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 won't fix
Projects
None yet
Development

Successfully merging a pull request may close this issue.

6 participants