Failing test: Chrome UI Functional Tests.test/functional/apps/visualize/_area_chart·js - visualize app area charts axis scaling scales when enabled count agg

[kibanamachine]

A test failed on a tracked branch

{ Error: expected [ [ '2015-09-20 00:00', '6' ],
  [ '2015-09-20 01:00', '9' ],
  [ '2015-09-20 02:00', '22' ],
  [ '2015-09-20 03:00', '31' ],
  [ '2015-09-20 04:00', '52' ],
  [ '2015-09-20 05:00', '119' ],
  [ '2015-09-20 06:00', '181' ],
  [ '2015-09-20 07:00', '218' ],
  [ '2015-09-20 08:00', '341' ],
  [ '2015-09-20 09:00', '440' ],
  [ '2015-09-20 10:00', '480' ],
  [ '2015-09-20 11:00', '517' ],
  [ '2015-09-20 12:00', '522' ],
  [ '2015-09-20 13:00', '446' ],
  [ '2015-09-20 14:00', '403' ],
  [ '2015-09-20 15:00', '321' ],
  [ '2015-09-20 16:00', '258' ],
  [ '2015-09-20 17:00', '172' ],
  [ '2015-09-20 18:00', '95' ],
  [ '2015-09-20 19:00', '55' ] ] to sort of equal [ [ '2015-09-20 00:00', '0.002' ],
  [ '2015-09-20 01:00', '0.003' ],
  [ '2015-09-20 02:00', '0.006' ],
  [ '2015-09-20 03:00', '0.009' ],
  [ '2015-09-20 04:00', '0.014' ],
  [ '2015-09-20 05:00', '0.033' ],
  [ '2015-09-20 06:00', '0.05' ],
  [ '2015-09-20 07:00', '0.061' ],
  [ '2015-09-20 08:00', '0.095' ],
  [ '2015-09-20 09:00', '0.122' ],
  [ '2015-09-20 10:00', '0.133' ],
  [ '2015-09-20 11:00', '0.144' ],
  [ '2015-09-20 12:00', '0.145' ],
  [ '2015-09-20 13:00', '0.124' ],
  [ '2015-09-20 14:00', '0.112' ],
  [ '2015-09-20 15:00', '0.089' ],
  [ '2015-09-20 16:00', '0.072' ],
  [ '2015-09-20 17:00', '0.048' ],
  [ '2015-09-20 18:00', '0.026' ],
  [ '2015-09-20 19:00', '0.015' ] ]
    at Assertion.assert (packages/kbn-expect/expect.js:100:11)
    at Assertion.eql (packages/kbn-expect/expect.js:244:8)
    at Inspector.eql [as expectTableData] (test/functional/services/inspector.ts:95:23)
    at process._tickCallback (internal/process/next_tick.js:68:7)
  actual:
   '[\n  [\n    "2015-09-20 00:00"\n    "6"\n  ]\n  [\n    "2015-09-20 01:00"\n    "9"\n  ]\n  [\n    "2015-09-20 02:00"\n    "22"\n  ]\n  [\n    "2015-09-20 03:00"\n    "31"\n  ]\n  [\n    "2015-09-20 04:00"\n    "52"\n  ]\n  [\n    "2015-09-20 05:00"\n    "119"\n  ]\n  [\n    "2015-09-20 06:00"\n    "181"\n  ]\n  [\n    "2015-09-20 07:00"\n    "218"\n  ]\n  [\n    "2015-09-20 08:00"\n    "341"\n  ]\n  [\n    "2015-09-20 09:00"\n    "440"\n  ]\n  [\n    "2015-09-20 10:00"\n    "480"\n  ]\n  [\n    "2015-09-20 11:00"\n    "517"\n  ]\n  [\n    "2015-09-20 12:00"\n    "522"\n  ]\n  [\n    "2015-09-20 13:00"\n    "446"\n  ]\n  [\n    "2015-09-20 14:00"\n    "403"\n  ]\n  [\n    "2015-09-20 15:00"\n    "321"\n  ]\n  [\n    "2015-09-20 16:00"\n    "258"\n  ]\n  [\n    "2015-09-20 17:00"\n    "172"\n  ]\n  [\n    "2015-09-20 18:00"\n    "95"\n  ]\n  [\n    "2015-09-20 19:00"\n    "55"\n  ]\n]',
  expected:
   '[\n  [\n    "2015-09-20 00:00"\n    "0.002"\n  ]\n  [\n    "2015-09-20 01:00"\n    "0.003"\n  ]\n  [\n    "2015-09-20 02:00"\n    "0.006"\n  ]\n  [\n    "2015-09-20 03:00"\n    "0.009"\n  ]\n  [\n    "2015-09-20 04:00"\n    "0.014"\n  ]\n  [\n    "2015-09-20 05:00"\n    "0.033"\n  ]\n  [\n    "2015-09-20 06:00"\n    "0.05"\n  ]\n  [\n    "2015-09-20 07:00"\n    "0.061"\n  ]\n  [\n    "2015-09-20 08:00"\n    "0.095"\n  ]\n  [\n    "2015-09-20 09:00"\n    "0.122"\n  ]\n  [\n    "2015-09-20 10:00"\n    "0.133"\n  ]\n  [\n    "2015-09-20 11:00"\n    "0.144"\n  ]\n  [\n    "2015-09-20 12:00"\n    "0.145"\n  ]\n  [\n    "2015-09-20 13:00"\n    "0.124"\n  ]\n  [\n    "2015-09-20 14:00"\n    "0.112"\n  ]\n  [\n    "2015-09-20 15:00"\n    "0.089"\n  ]\n  [\n    "2015-09-20 16:00"\n    "0.072"\n  ]\n  [\n    "2015-09-20 17:00"\n    "0.048"\n  ]\n  [\n    "2015-09-20 18:00"\n    "0.026"\n  ]\n  [\n    "2015-09-20 19:00"\n    "0.015"\n  ]\n]',
  showDiff: true }

First failure: Jenkins Build

[elasticmachine]

Pinging @elastic/kibana-test-triage (failed-test)

[kibanamachine]

New failure: Jenkins Build

[flash1293]

@ppisljar Could be interpreter related - this is shown in the screenshot

A whole bunch of test failures in visualizations popped up recently. Was there anything interpreter related merged lately that could cause those?

[elasticmachine]

Pinging @elastic/kibana-app-arch (Team:AppArch)

[kibanamachine]

New failure: Jenkins Build

[kibanamachine]

New failure: Jenkins Build

[pheyos]

Similar to #50290 - skipped for 7.5 in 8d15794

[kibanamachine]

New failure: Jenkins Build

[lukeelmers]

@flash1293 I'm looking at CI status and am struggling to find where this might have come up. One notable change to visualizations merged in #46910, but this was not backported to 7.5 so it seems unlikely it would be related. There's also an update to expressions in #48748, but that was awhile ago and I feel like we would've seen failures earlier.

In looking at the commit history on 7.5, I'm not seeing any suspicious commits around the time these failures started.

I ran this test a bunch of time under different conditions, including throttled network speed, and I still can't reproduce locally.

One thing I can extrapolate from the error message is that, in the past, we've seen errors like this when the visConfig string that's passed to an expression function ends up undefined and thus cannot be JSON.parsed (causing "Unexpected token u" error message). However, this should've been resolved for esaggs in this PR from 7.3: #32459

I'm afraid I'm at a loss on this at the moment, but I've also been out the past few weeks so perhaps @ppisljar will have some better ideas.

[flash1293]

Thanks for checking @lukeelmers . @ppisljar do you think it’s save to lift the blocker status from the issue for 7.5?

[ppisljar]

i think we should, as we are unable to reproduce this locally it might be just a flaky test which shouldn't be a blocker.

[flash1293]

This test hasn't failed since the general problems from the beginning of November have been fixed - looks like this was just related to CI instability. I'm hesitant to close the issue because the failure hints at a real problem with the interpreter infrastructure - the behavior shown in the screenshots should not be possible at all no matter what the Kibana server is doing. I will remove my assignment for now as this looks like an app arch problem. FYI @ppisljar

[tylersmalley]

Skipped in b0941df

[vadimkibana]

Thank you for contributing to this issue, however, we are closing this issue due to inactivity as part of a backlog grooming effort. If you believe this feature/bug should still be considered, please reopen with a comment.