Fix flaky core_app integration tests

[afharo]

Summary

• Starting off by unskipping them

Resolves #81072

Checklist

Delete any items that are not applicable to this PR.

• Any text added follows EUI's writing guidelines, uses sentence case text and includes i18n support
• Documentation was added for features that require explanation or tutorials
• Unit or functional tests were updated or added to match the most common scenarios
• Any UI touched in this PR is usable by keyboard only (learn more about keyboard accessibility)
• Any UI touched in this PR does not create any new axe failures (run axe in browser: FF, Chrome)
• If a plugin configuration key changed, check if it needs to be allowlisted in the cloud and added to the docker list
• This renders correctly on smaller devices using a responsive layout. (You can test this in your browser)
• This was checked for cross-browser compatibility

For maintainers

• This was checked for breaking API changes and was labeled appropriately

[afharo]

@elasticmachine merge upstream

Second run to see if it fails. After 3 successful runs, I'll merge.

[Bamieh]

@elasticmachine merge upstream

[Bamieh]

approving to unblock in case it gets 3 successive passes.

[pgayvallet]

Second run to see if it fails. After 3 successful runs, I'll merge.

Imho 3 green runs is far from being good enough to unskip a flaky suite (I mean, it's flaky, not red, 3 runs will likely succeed if the flakiness rate is < 10%, which is most likely the case here)

I usually fork the branch, edit the CI group tests to have only this specific test running, then use the flaky runner on 200+ iterations.

EDIT: this is not a FTR test. Well in that case, I would edit the IT file to have the test run 200 times, and then revert the commit if/when green.

[afharo]

Good call @pgayvallet! I've added a loop to run the suite 200 times. It forced me to move some of the vars and setup steps inside the describe context. Probably that was the cause of the flaky tests.

[afharo]

The tests passed 200 times in a row after the fixes mentioned in my previous comment: search src/core/server/core_app/integration_tests/default_route_provider_config.test.ts in the logs of the CI job to see them.

I'll go ahead and revert the 200 loop.

[kibanamachine]

💚 Build Succeeded

• continuous-integration/kibana-ci/pull-request
• Commit: 406bd78
• Storybooks Preview

Metrics [docs]

✅ unchanged

History

• 💚 Build #108304 succeeded bb7471c
• 💛 Build #108275 was flaky 5058a3d
• 💚 Build #108196 succeeded 948a5d9
• 💚 Build #108046 succeeded ca9050d

To update your PR or re-run it, just comment with:
@elasticmachine merge upstream

[kibanamachine]

💚 Backport successful

✅ 7.x / #92190

Successful backport PRs will be merged automatically after passing CI.