elastic / kibana

Your window into the Elastic Stack
https://www.elastic.co/products/kibana
Other
19.62k stars 8.22k forks source link

Failing test: Chrome X-Pack UI Functional Tests - ML anomaly_detection_result_views.x-pack/test/functional/apps/ml/anomaly_detection_result_views/anomaly_explorer·ts - machine learning - anomaly detection anomaly explorer with farequote based multi metric job renders swim lanes correctly on the time bounds change #192703

Closed kibanamachine closed 1 month ago

kibanamachine commented 1 month ago

A test failed on a tracked branch

Error: Expected swim lane x labels to be 2012-06-19,2012-11-16,2013-04-15,2013-09-12,2014-02-09,2014-07-09,2014-12-06,2015-05-05,2015-10-02, got 2016-02-07 00:00,2016-02-07 20:00,2016-02-08 16:00,2016-02-09 12:00,2016-02-10 08:00,2016-02-11 04:00
    at Assertion.assert (expect.js:100:11)
    at Assertion.eql (expect.js:244:8)
    at Object.assertAxisLabels (swim_lane.ts:91:31)
    at processTicksAndRejections (node:internal/process/task_queues:95:5)
    at Context.<anonymous> (anomaly_explorer.ts:425:11)
    at Object.apply (wrap_function.js:73:16) {
  actual: '[\n' +
    '  "2016-02-07 00:00"\n' +
    '  "2016-02-07 20:00"\n' +
    '  "2016-02-08 16:00"\n' +
    '  "2016-02-09 12:00"\n' +
    '  "2016-02-10 08:00"\n' +
    '  "2016-02-11 04:00"\n' +
    ']',
  expected: '[\n' +
    '  "2012-06-19"\n' +
    '  "2012-11-16"\n' +
    '  "2013-04-15"\n' +
    '  "2013-09-12"\n' +
    '  "2014-02-09"\n' +
    '  "2014-07-09"\n' +
    '  "2014-12-06"\n' +
    '  "2015-05-05"\n' +
    '  "2015-10-02"\n' +
    ']',
  showDiff: true
}

First failure: kibana-elasticsearch-snapshot-verify - 8.15

elasticmachine commented 1 month ago

Pinging @elastic/ml-ui (:ml)

peteharverson commented 1 month ago

This test was automatically retried and passed, so didn't block the es promotion. Removing failed-es-promotion label.

Test failure was in an Anomaly Explorer test, where the time range is widened, and then the swim lane axis labels are checked to validate if they match the new expanded time range.

Will monitor over the next couple of weeks to see whether it fails again with this same error.

peteharverson commented 1 month ago

Closing, no failure since original failure 4 weeks ago.