Skip to content

Update max Capybara timeout to 45 seconds

Alina Mihaila requested to merge am-update-max-timeout-limit into master

What does this MR do and why?

Describe in detail what your merge request does and why.

This was lowered with MR and I'm concerned that it results in master broken incidents.

https://app.periscopedata.com/app/gitlab/1082465/Master-Broken-Incidents-Root-Cause-Analysis

Looking at master broken root cause analyses we have top root cause flaky tests and from there flaky-testunreliable dom selector

https://app.periscopedata.com/app/gitlab/1082465/Master-Broken-Incidents-Root-Cause-Analysis?widget=16485875&udv=0

Screenshot_2023-03-23_at_13.39.38

Example of jobs that fail because of reaching the timeout is https://gitlab.com/gitlab-org/gitlab/-/jobs/3964964228

With this proposal we extent the timeout to 45 seconds.

Screenshots or screen recordings

Screenshots are required for UI changes, and strongly recommended for all other merge requests.

How to set up and validate locally

Numbered steps to set up and validate the change are strongly suggested.

MR acceptance checklist

This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.

Edited by David Dieulivol

Merge request reports

Loading