The test assumes the dataset is in a particular (usually limited) state, which might not be true depending on when the test run during the test suite.

The test is assuming a specific date or time.

A flaky test issue arising from timing-related factors, such as delays, eventual consistency, asynchronous operations, or race conditions. These issues may stem from shortcomings in the test logic, the system under test, or their interaction. While tests can sometimes address these issues through improved synchronization, they may also reveal underlying system bugs that require resolution.

The test use random values, that sometimes match the expectations, and sometimes not.

Test data state leaked through test cases. See https://docs.gitlab.com/ee/development/testing_guide/flaky_tests.html#state-leak

Master broken incidents caused by flaky tests which are failing because sql queries limit has exceeded

Test is failing intermittently due to a transient bug in our software

The DOM selector used in the test is unreliable.

The test fails from time to time due to infrastructure issues.

Test data state leaked through test cases. The same as ~"flaky-test::state leak" but it's considered broken because it's almost always happening. See https://docs.gitlab.com/ee/development/testing_guide/flaky_tests.html#state-leak