-
Notifications
You must be signed in to change notification settings - Fork 8.2k
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
[Logs UI] Stabilize and re-enable functional log reordering test #41749
Labels
Comments
weltenwort
added
Feature:Logs UI
Logs UI feature
Team:Infra Monitoring UI - DEPRECATED
DEPRECATED - Label for the Infra Monitoring UI team. Use Team:obs-ux-infra_services
v7.4.0
labels
Jul 23, 2019
Pinging @elastic/infra-logs-ui |
4 tasks
Test is unfortunately still flaky after #41777: https://kibana-ci.elastic.co/job/elastic+kibana+7.x/JOB=x-pack-firefoxSmoke,node=linux-immutable/1265/console |
sgrodzicki
added
[zube]: Inbox
and removed
Team:Infra Monitoring UI - DEPRECATED
DEPRECATED - Label for the Infra Monitoring UI team. Use Team:obs-ux-infra_services
[zube]: Ready
labels
May 15, 2020
sgrodzicki
added
the
Team:Infra Monitoring UI - DEPRECATED
DEPRECATED - Label for the Infra Monitoring UI team. Use Team:obs-ux-infra_services
label
Jun 15, 2020
Pinging @elastic/logs-metrics-ui (Team:logs-metrics-ui) |
gbamparop
added
Team:obs-ux-logs
Observability Logs User Experience Team
and removed
Team:Infra Monitoring UI - DEPRECATED
DEPRECATED - Label for the Infra Monitoring UI team. Use Team:obs-ux-infra_services
labels
Nov 9, 2023
Pinging @elastic/obs-ux-logs-team (Team:obs-ux-logs) |
botelastic
bot
added
needs-team
Issues missing a team label
and removed
needs-team
Issues missing a team label
labels
Nov 9, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
Some steps from the log column reordering test added in #41035 were commented out in #41743, because they proved to be flakey in #41717. They should be made more robust and re-enabled.
A possible cause for the flakyness is that the reordering operation did not reach the form component state before the save button was clicked. That sequence should probably be fortified with some kind of retry/wait operation.
The text was updated successfully, but these errors were encountered: