Kibana: Failing test: Jest Integration Tests.src/core/server/metrics/integration_tests - ServerMetricsCollector collect connection count

[kibanamachine]

A test failed on a tracked branch

Error: connect ECONNRESET 127.0.0.1:45435
    at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1107:14)

First failure: Jenkins Build

[elasticmachine]

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

[kibanamachine]

New failure: Jenkins Build

[elasticmachine]

Pinging @elastic/stack-monitoring (Team:Monitoring)

[elasticmachine]

Pinging @elastic/kibana-platform (Team:Platform)

[chrisronline]

Adding platform team, as they technically own this

[pgayvallet]

Is this occurring on a regular basis or is there only 2 failures in the last month?

[spalger]

It's not really regular, we've only had two failures in PRs, and only very recently:

[pgayvallet]

This is probably caused by the only delay I couldn't replace with observable awaiting in the test.

https://github.com/elastic/kibana/blob/1f8da9dd7726596fd80658d48cbdf2b89e7c7855/src/core/server/metrics/integration_tests/server_collector.test.ts#L199-L200

Having a full stack trace would help to see where exactly it failed in the test and confirm that. but the two CI build failures are no longer accessible.

Will have to wait until next failure I guess?

[spalger]

Hmm, looking into it more closely I see the two PR failures were both in https://kibana-ci.elastic.co/job/elastic+kibana+pipeline-pull-request/39554/, which is seeing all ServerMetricsCollector tests fail because of the node.js version upgrade. In that case I think this might not have actually failed, even in PRs in the last 60 days so I'm going to close it.

[kibanamachine]

New failure: Jenkins Build

[kibanamachine]

New failure: Jenkins Build

[spalger]

Backporting fix to 7.8 https://github.com/elastic/kibana/pull/66643

[pgayvallet]

closing because of 7.8 backport