Failing test: API Integration Tests.test/api_integration/apis/telemetry/telemetry_local·js - apis Telemetry /api/telemetry/v2/clusters/_stats should pull local stats and validate data types

[kibanamachine]

A test failed on a tracked branch

Error: expected 0 to be above 0
    at Assertion.assert (packages/kbn-expect/expect.js:100:11)
    at Assertion.greaterThan.Assertion.above (packages/kbn-expect/expect.js:317:8)
    at Function.greaterThan (packages/kbn-expect/expect.js:531:15)
    at Context.it (test/api_integration/apis/telemetry/telemetry_local.js:93:61)

First failure: Jenkins Build

[elasticmachine]

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

[elasticmachine]

Pinging @elastic/kibana-telemetry (Team:KibanaTelemetry)

[afharo]

After looking at the logs, it looks as if ES had some storage problem/delays during the execution of this test: The failed assertion is

kibana/test/api_integration/apis/telemetry/telemetry_local.js

Line 93 in 45ddd65

expect(stats.stack_stats.data[0].size_in_bytes).to.be.greaterThan(0);

The assertion is related to the index "filebeat-telemetry_tests_logs" created in the before step.

If preferred, we could replace .to.be.greaterThan(0); and use .to.be.a('number'); instead so this won't happen again. But these changes were merged and backported 1+ month ago (#70557) and it's the first and only time it happened.

What do you think @dmlemeshko?

[dmlemeshko]

@afharo I think test adjustment is a better option, but only if it is still valid after a change.
Is it a valid case when size is zero bytes?

[afharo]

Is it a valid case when size is zero bytes?

To be fair, we are only creating the index (not storing any document in it), so the size is expected to be minimal (208 bytes in my Mac). It seems weird to be 0 (AFAIK, the index should take a bit of space), but I guess it's fine to simply check it's a number. I'll create a tentative PR with the change 👍

[elasticmachine]

Pinging @elastic/kibana-core (Team:Core)