[test-failed]: Chrome X-Pack UI Functional Tests1.x-pack/test/functional/apps/dashboard/reporting/screenshots·ts.dashboard Reporting Screenshots "before all" hook: initialize tests in "Screenshots"

[liza-mae]

Version: 8.8.0-SNAPSHOT
Class: Chrome X-Pack UI Functional Tests1.x-pack/test/functional/apps/dashboard/reporting/screenshots·ts
Stack Trace:
Error: Request failed with status code 500
at createError (/home/liza/TESTING/kbn-7.8/node_modules/axios/lib/core/createError.js:16:15)
at settle (/home/liza/TESTING/kbn-7.8/node_modules/axios/lib/core/settle.js:17:12)
at IncomingMessage.handleStreamEnd (/home/liza/TESTING/kbn-7.8/node_modules/axios/lib/adapters/http.js:236:11)
at endReadableNT (_stream_readable.js:1145:12)
at process._tickCallback (internal/process/next_tick.js:63:19)
Platform: cloud
Build Num: 278

[elasticmachine]

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

[elasticmachine]

Pinging @elastic/kibana-reporting-services (Team:Reporting Services)

[liza-mae]

This test appears to be causing some cascading failures on cloud. I see this error in the UI:

{"statusCode":500,"error":"Internal Server Error","message":"Limit of total fields [1000] in index [.kibana_2] has been exceeded"}

[elasticmachine]

Pinging @elastic/kibana-operations (Team:Operations)

[liza-mae]

@tsullivan and I debugged this and found the root cause is es archiver, since we have seen es archiver failures happen before on major release in cloud, we would like the operations team to take a look. This is high priority as it is causing cascading failures. The test above reproduces the problem consistently. I will send logs via slack.

[liza-mae]

This turned out to be a real issue and relates to #69985 and some PRs that were merged recently seems to have fixed it.

This test is no longer throwing an internal server issue:
{"statusCode":500,"error":"Internal Server Error","message":"Limit of total fields [1000] in index [.kibana_2] has been exceeded"}

The tests still have some failures, new issues to be open. Closed as fixed.