Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Kibana Overview] Fix failing test #139112

Merged
merged 9 commits into from
Sep 8, 2022

Conversation

majagrubic
Copy link
Contributor

@majagrubic majagrubic commented Aug 18, 2022

Summary

Fixes: #137741

On Cloud, there is "Enterprise Search" solution as well, which messes up the order of the solutions, so checking for the exact order is not an option.

Checklist

Delete any items that are not applicable to this PR.

For maintainers

@majagrubic majagrubic requested a review from a team August 18, 2022 19:55
@majagrubic majagrubic added v8.4.0 release_note:skip Skip the PR/issue when compiling release notes labels Aug 18, 2022
@majagrubic majagrubic marked this pull request as ready for review August 19, 2022 04:46
});

it('click on Observability card leads to Observability', async () => {
// skipped as on Cloud it's a different setup than locally
xit('click on Observability card leads to Observability', async () => {
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why do we keep those skipped tests if we can't run them on CI?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

So we know we need to tackle them at one point in time, which may not be right away.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I see. Should we create an issue for it then and add the link in this comment?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Cool thanks. Sorry I meant in the comment of the code base 😊 So we know it is being tracked

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hope it's ok now

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yeah perfect thanks. It is just to be consistent with how the operation team flags skipped tests when there are too many failure in CI.

@majagrubic
Copy link
Contributor Author

@elasticmachine merge upstream

@majagrubic majagrubic requested a review from sebelga August 24, 2022 14:07
@majagrubic majagrubic requested a review from a team August 25, 2022 17:59
Copy link
Contributor

@rshen91 rshen91 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM nice comments for tracking failing test issues

Copy link
Contributor

@sebelga sebelga left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM 👍 Thanks for fixing the tests

@liza-mae
Copy link
Contributor

Thanks @majagrubic for putting in this fix, can we update the PR and merge as soon as possible to main and 8.4.

@liza-mae
Copy link
Contributor

liza-mae commented Sep 7, 2022

@elasticmachine merge upstream

@kibana-ci
Copy link
Collaborator

💚 Build Succeeded

Metrics [docs]

✅ unchanged

History

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

@liza-mae
Copy link
Contributor

liza-mae commented Sep 7, 2022

@majagrubic this looks ready, should we merge?

@majagrubic majagrubic merged commit 1929395 into elastic:main Sep 8, 2022
@kibanamachine
Copy link
Contributor

💔 All backports failed

Status Branch Result
8.4 An unhandled error occurred. Please see the logs for details

Manual backport

To create the backport manually run:

node scripts/backport --pr 139112

Questions ?

Please refer to the Backport tool documentation

@majagrubic
Copy link
Contributor Author

💚 All backports created successfully

Status Branch Result
8.4

Note: Successful backport PRs will be merged automatically after passing CI.

Questions ?

Please refer to the Backport tool documentation

majagrubic pushed a commit to majagrubic/kibana that referenced this pull request Sep 9, 2022
* [Kibana Overview] Fix failing test

* Remove comment

* Fix regexp

* Add a comment

Co-authored-by: Kibana Machine <[email protected]>
(cherry picked from commit 1929395)
majagrubic pushed a commit that referenced this pull request Sep 9, 2022
* [Kibana Overview] Fix failing test

* Remove comment

* Fix regexp

* Add a comment

Co-authored-by: Kibana Machine <[email protected]>
(cherry picked from commit 1929395)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
release_note:skip Skip the PR/issue when compiling release notes v8.4.0 v8.4.2 v8.5.0
Projects
None yet
6 participants