[Obs AI Assistant] remove flaky test

[neptunian]

This test can be flaky because the "save" button only appears if the there is change in one of the form values, but the change can be "reset" if the state takes a while to load in some edge case so the "save" button does not appear. Given I already added a test for making sure that the inputs are disabled when a user does not have access to Advanced Settings, this test is somewhat redundant in terms of security access and given its flaky nature, I would like to remove it. I could see having it in another test suite that tests general functionality of the settings page and a unit test for useEditableSettings.

Closes #190637

[obltmachine]

🤖 GitHub comments

Expand to view the GitHub comments

Just comment with:

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

[neptunian]

/ci

[kibanamachine]

Flaky Test Runner Stats

🎉 All tests passed! - kibana-flaky-test-suite-runner#6815

[✅] x-pack/test/observability_ai_assistant_functional/enterprise/config.ts: 25/25 tests passed.

see run history

[neptunian]

/ci

[neptunian]

/ci

[kibanamachine]

Flaky Test Runner Stats

🎉 All tests passed! - kibana-flaky-test-suite-runner#6822

[✅] x-pack/test/observability_ai_assistant_functional/enterprise/config.ts: 25/25 tests passed.

see run history

[kibana-ci]

💚 Build Succeeded

• Buildkite Build
• Commit: fe550c2
• Kibana Serverless Image: docker.elastic.co/kibana-ci/kibana-serverless:pr-191531-fe550c2db52c

Metrics [docs]

✅ unchanged

History

• 💚 Build #230395 succeeded fe550c2
• 💔 Build #230375 failed 350ba2c
• 💔 Build #230364 failed 2ff7826
• 💔 Build #230363 failed 2ff7826
• 💔 Build #230223 failed c440198

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