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

[Entity Analytics] Hopefully fix flaky tests 🤞 #177421

Merged
merged 10 commits into from
Mar 14, 2024

Conversation

hop-dev
Copy link
Contributor

@hop-dev hop-dev commented Feb 21, 2024

Summary

Closes #174860
Closes #174859

Hopefully fix some flaky tests for good.

Flaky test run 1 (50 ESS): https://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/5268

Flaky test run 2 (100 ESS 100 Serverless) https://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/5278

Flaky test run 3 100 again https://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/5436 ✅ (ran as a lot of time has passed)

componentType === 'RiskInformationButtonIcon'
? RiskInformationButtonIcon
: RiskInformationButtonEmpty;
describe('RiskInformationButtonEmpty', () => {
Copy link
Contributor Author

Choose a reason for hiding this comment

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

Updated these tests as I have removed the RiskInformationButtonIcon component

@@ -105,29 +106,6 @@ const getCriticalityLevelTableColumns = (): Array<
export const HOST_RISK_INFO_BUTTON_CLASS = 'HostRiskInformation__button';
export const USER_RISK_INFO_BUTTON_CLASS = 'UserRiskInformation__button';

export const RiskInformationButtonIcon = ({ riskEntity }: { riskEntity: RiskScoreEntity }) => {
Copy link
Contributor Author

Choose a reason for hiding this comment

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

I noticed this component isn't being used when grepping around so I have removed it

@@ -36,11 +36,17 @@ interface UserRiskEntity {
export type RiskEntity = HostRiskEntity | UserRiskEntity;

const RiskSummaryComponent: React.FC<RiskEntity> = ({ risk, riskEntity, originalRisk }) => {
const currentRiskScore =
let currentRiskScore =
Copy link
Contributor Author

Choose a reason for hiding this comment

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

this is hopefully the fix for enrichments.cy.ts

@hop-dev hop-dev changed the title [EA] Flaky test [Entity Analytics] Hopefully fix some flaky tests Feb 22, 2024
@hop-dev hop-dev changed the title [Entity Analytics] Hopefully fix some flaky tests [Entity Analytics] _Hopefully_ fix flaky tests 🤞 Feb 23, 2024
@hop-dev hop-dev changed the title [Entity Analytics] _Hopefully_ fix flaky tests 🤞 [Entity Analytics] Hopefully fix flaky tests 🤞 Feb 23, 2024
@@ -15,9 +15,22 @@ import {
RISK_DETAILS_NAV,
} from '../screens/hosts/host_risk';

export const navigateToHostRiskDetailTab = () => {
export const navigateToHostRiskDetailTab = (attempts = 3) => {
Copy link
Contributor Author

Choose a reason for hiding this comment

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

not my proudest work but I have no idea why sometimes the tab doesn't click, and I think these tests are useful so here we are

Copy link
Contributor

Choose a reason for hiding this comment

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

humm, I thought this file was about the old host details, and that we should remove it?

@hop-dev hop-dev marked this pull request as ready for review February 23, 2024 09:36
@hop-dev hop-dev requested a review from a team as a code owner February 23, 2024 09:36
@hop-dev hop-dev self-assigned this Feb 23, 2024
@hop-dev hop-dev added release_note:skip Skip the PR/issue when compiling release notes v8.13.0 backport:prev-minor Backport to (8.x) the previous minor version (i.e. one version back from main) labels Feb 23, 2024
@hop-dev
Copy link
Contributor Author

hop-dev commented Feb 23, 2024

@elasticmachine merge upstream

@hop-dev
Copy link
Contributor Author

hop-dev commented Feb 23, 2024

/ci

@hop-dev hop-dev force-pushed the flaky-risk-tab-test branch from 2fffafd to f188673 Compare March 4, 2024 11:19
@hop-dev hop-dev closed this Mar 4, 2024
@hop-dev hop-dev deleted the flaky-risk-tab-test branch March 4, 2024 14:25
@hop-dev hop-dev restored the flaky-risk-tab-test branch March 7, 2024 12:02
@hop-dev hop-dev reopened this Mar 7, 2024
@hop-dev
Copy link
Contributor Author

hop-dev commented Mar 7, 2024

@elasticmachine merge upstream

@kibanamachine
Copy link
Contributor

merge conflict between base and head

@hop-dev
Copy link
Contributor Author

hop-dev commented Mar 11, 2024

@hop-dev
Copy link
Contributor Author

hop-dev commented Mar 11, 2024

@elasticmachine merge upstream

@hop-dev
Copy link
Contributor Author

hop-dev commented Mar 13, 2024

@elasticmachine merge upstream

@kibana-ci
Copy link
Collaborator

💚 Build Succeeded

The CI Stats report is too large to be displayed here, check out the CI build annotation for this information.

History

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

cc @hop-dev

@@ -15,9 +15,22 @@ import {
RISK_DETAILS_NAV,
} from '../screens/hosts/host_risk';

export const navigateToHostRiskDetailTab = () => {
export const navigateToHostRiskDetailTab = (attempts = 3) => {
Copy link
Contributor

Choose a reason for hiding this comment

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

humm, I thought this file was about the old host details, and that we should remove it?

@hop-dev hop-dev merged commit 5f1da5c into elastic:main Mar 14, 2024
34 checks passed
@hop-dev hop-dev deleted the flaky-risk-tab-test branch March 14, 2024 14:30
@kibanamachine
Copy link
Contributor

💔 All backports failed

Status Branch Result
8.13 Backport failed because of merge conflicts

Manual backport

To create the backport manually run:

node scripts/backport --pr 177421

Questions ?

Please refer to the Backport tool documentation

@kibanamachine
Copy link
Contributor

Friendly reminder: Looks like this PR hasn’t been backported yet.
To create automatically backports add the label auto-backport or prevent reminders by adding the backport:skip label.
You can also create backports manually by running node scripts/backport --pr 177421 locally

2 similar comments
@kibanamachine
Copy link
Contributor

Friendly reminder: Looks like this PR hasn’t been backported yet.
To create automatically backports add the label auto-backport or prevent reminders by adding the backport:skip label.
You can also create backports manually by running node scripts/backport --pr 177421 locally

@kibanamachine
Copy link
Contributor

Friendly reminder: Looks like this PR hasn’t been backported yet.
To create automatically backports add the label auto-backport or prevent reminders by adding the backport:skip label.
You can also create backports manually by running node scripts/backport --pr 177421 locally

@hop-dev hop-dev added backport:skip This commit does not require backporting and removed backport missing Added to PRs automatically when the are determined to be missing a backport. backport:prev-minor Backport to (8.x) the previous minor version (i.e. one version back from main) labels Aug 2, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backport:skip This commit does not require backporting release_note:skip Skip the PR/issue when compiling release notes v8.13.0 v8.14.0
Projects
None yet
5 participants