[APM] Revert skip for flaky Tests

[achyutjhunjhunwala]

Summary

Closes

• Failing test: APM API Integration tests (basic).x-pack/test/apm_api_integration/tests/service_overview/instance_details·ts - APM API tests basic apm_8.0.0 Instance details when data is loaded fetch instance details return the correct data #120056
• Failing test: Chrome X-Pack UI Functional Tests.x-pack/test/functional/apps/apm/feature_controls/apm_security·ts - APM specs feature controls security no apm privileges "before all" hook for "doesn't show APM navlink" #122001
• Failing test: Chrome X-Pack UI Functional Tests.x-pack/test/functional/apps/apm/correlations/latency_correlations·ts - APM specs correlations latency correlations space with no features disabled navigates to the 'opbeans-go' service overview page #127431
• Failing test: Chrome X-Pack UI Functional Tests.x-pack/test/functional/apps/apm/correlations/failed_transaction_correlations·ts - APM specs correlations failed transactions correlations space with no features disabled navigates to the 'opbeans-go' service overview page #127416

Flakiness Testing

Changes in the PR were tested with the flaky test runner, running 50 times for all 5 configs for APM

1. 4 config (Trial, Basic, Cloud and Rules) present inside apm_api_integration folder and
2. 1 config present inside functional/apps/apm

https://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/2499

[apmmachine]

🤖 GitHub comments

Expand to view the GitHub comments

Just comment with:

• /oblt-deploy : Deploy a Kibana instance using the Observability test environments.
• run elasticsearch-ci/docs : Re-trigger the docs validation. (use unformatted text in the comment!)

[kibana-ci]

💚 Build Succeeded

• Buildkite Build
• Commit: c56e91e

Metrics [docs]

Unknown metric groups

ESLint disabled line counts

id	before	after	diff
enterpriseSearch	14	16	+2
securitySolution	413	417	+4
total			+6

Total ESLint disabled count

id	before	after	diff
enterpriseSearch	15	17	+2
securitySolution	492	496	+4
total			+6

History

• 💔 Build #138344 failed 6232a0a
• 💔 Build #138215 failed b0e9db0
• 💔 Build #138107 failed ade0c33
• 💔 Build #138067 failed 95d664e
• 💔 Build #138009 failed 8ca7a50

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

[yngrdyn]

LGTM 🥇
For the functional tests maybe we need to create a ticket if there is no one already. I think it'd help with visibility of the tech debt rather than having it in the dev documentation.

TODO: We could try moving this tests to the new e2e tests located at x-pack/plugins/apm/ftr_e2e.

[elasticmachine]

Pinging @elastic/apm-ui (Team:APM)

[achyutjhunjhunwala]

LGTM 🥇 For the functional tests maybe we need to create a ticket if there is no one already. I think it'd help with visibility of the tech debt rather than having it in the dev documentation.

TODO: We could try moving this tests to the new e2e tests located at x-pack/plugins/apm/ftr_e2e.

@yngrdyn #160701

[sorenlouv]

@achyutjhunjhunwala did you intentionally remove these?

[achyutjhunjhunwala]

Yes, as this was adding no value but more flakiness.