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

Failing test: Chrome X-Pack UI Functional Tests - aiops.x-pack/test/functional/apps/aiops/log_rate_analysis·ts - aiops log rate analysis with 'ft_farequote' farequote with spike displays index details #176066

Closed
kibanamachine opened this issue Feb 1, 2024 · 3 comments · Fixed by #176130
Assignees
Labels
failed-test A test failure on a tracked branch, potentially flaky-test :ml

Comments

@kibanamachine
Copy link
Contributor

kibanamachine commented Feb 1, 2024

A test failed on a tracked branch

Error: retry.tryForTime timeout: Error: expected testSubject(globalLoadingIndicator-hidden) to exist
    at TestSubjects.existOrFail (test_subjects.ts:71:13)
    at processTicksAndRejections (node:internal/process/task_queues:95:5)
    at HeaderPageObject.awaitGlobalLoadingIndicatorHidden (header_page.ts:72:5)
    at HeaderPageObject.waitUntilLoadingHasFinished (header_page.ts:63:5)
    at log_rate_analysis_page.ts:62:9
    at runAttempt (retry_for_success.ts:29:15)
    at retryForSuccess (retry_for_success.ts:79:21)
    at RetryService.tryForTime (retry.ts:23:12)
    at Object.setQueryInput (log_rate_analysis_page.ts:50:7)
    at Context.<anonymous> (log_rate_analysis.ts:45:9)
    at Object.apply (wrap_function.js:73:16)
    at onFailure (retry_for_success.ts:17:9)
    at retryForSuccess (retry_for_success.ts:67:13)
    at RetryService.tryForTime (retry.ts:23:12)
    at Object.setQueryInput (log_rate_analysis_page.ts:50:7)
    at Context.<anonymous> (log_rate_analysis.ts:45:9)
    at Object.apply (wrap_function.js:73:16)

First failure: CI Build - main

@kibanamachine kibanamachine added the failed-test A test failure on a tracked branch, potentially flaky-test label Feb 1, 2024
@botelastic botelastic bot added the needs-team Issues missing a team label label Feb 1, 2024
@kibanamachine
Copy link
Contributor Author

New failure: CI Build - main

@mistic mistic added the :ml label Feb 1, 2024
@elasticmachine
Copy link
Contributor

Pinging @elastic/ml-ui (:ml)

@botelastic botelastic bot removed the needs-team Issues missing a team label label Feb 1, 2024
mistic added a commit that referenced this issue Feb 1, 2024
@mistic
Copy link
Member

mistic commented Feb 1, 2024

Skipped.

main: 2e161d6

@walterra walterra self-assigned this Feb 1, 2024
walterra added a commit that referenced this issue Feb 6, 2024
…5 minutes" (#176130)

## Summary

Fixes #176066. Regression introduced in #175289.

Fixes a rerendering issue with relative time ranges like "Last 15
minutes". The memoization didn't work correctly because for the relative
time range we would constantly get updated bounds.

### Checklist

Delete any items that are not applicable to this PR.

- [x] [Unit or functional
tests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)
were updated or added to match the most common scenarios
- [x] [Flaky Test
Runner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was
used on any tests changed
- [x] This was checked for breaking API changes and was [labeled
appropriately](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)
fkanout pushed a commit to fkanout/kibana that referenced this issue Feb 7, 2024
fkanout pushed a commit to fkanout/kibana that referenced this issue Feb 7, 2024
…5 minutes" (elastic#176130)

## Summary

Fixes elastic#176066. Regression introduced in elastic#175289.

Fixes a rerendering issue with relative time ranges like "Last 15
minutes". The memoization didn't work correctly because for the relative
time range we would constantly get updated bounds.

### Checklist

Delete any items that are not applicable to this PR.

- [x] [Unit or functional
tests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)
were updated or added to match the most common scenarios
- [x] [Flaky Test
Runner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was
used on any tests changed
- [x] This was checked for breaking API changes and was [labeled
appropriately](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)
CoenWarmer pushed a commit to CoenWarmer/kibana that referenced this issue Feb 15, 2024
CoenWarmer pushed a commit to CoenWarmer/kibana that referenced this issue Feb 15, 2024
…5 minutes" (elastic#176130)

## Summary

Fixes elastic#176066. Regression introduced in elastic#175289.

Fixes a rerendering issue with relative time ranges like "Last 15
minutes". The memoization didn't work correctly because for the relative
time range we would constantly get updated bounds.

### Checklist

Delete any items that are not applicable to this PR.

- [x] [Unit or functional
tests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)
were updated or added to match the most common scenarios
- [x] [Flaky Test
Runner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was
used on any tests changed
- [x] This was checked for breaking API changes and was [labeled
appropriately](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)
fkanout pushed a commit to fkanout/kibana that referenced this issue Mar 4, 2024
fkanout pushed a commit to fkanout/kibana that referenced this issue Mar 4, 2024
…5 minutes" (elastic#176130)

## Summary

Fixes elastic#176066. Regression introduced in elastic#175289.

Fixes a rerendering issue with relative time ranges like "Last 15
minutes". The memoization didn't work correctly because for the relative
time range we would constantly get updated bounds.

### Checklist

Delete any items that are not applicable to this PR.

- [x] [Unit or functional
tests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)
were updated or added to match the most common scenarios
- [x] [Flaky Test
Runner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was
used on any tests changed
- [x] This was checked for breaking API changes and was [labeled
appropriately](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
failed-test A test failure on a tracked branch, potentially flaky-test :ml
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants