Skip to content

Quarantine a flaky test

Ghost User requested to merge quarantine-flaky-tests-spec-lib-omni_auth-strategies-jwt_spec-rb-125 into master

The OmniAuth::Strategies::Jwt#decoded when timestamp claim is too skewed from present raises error test matches one of the following conditions:

  1. has either flakiness1 or flakiness2 label set, which means the number of reported failures is at or above 95 percentile, indicating unusually high failure count.

  2. has severity1 label set, which means the number of reported failures spiked and exceeded its daily threshold.

This MR quarantines the test. This is a discussion starting point to let the responsible group know about the flakiness so that they can take action:

  • accept the merge request and schedule the associated issue to improve the test
  • close the merge request in favor of another merge request to delete the test

Please follow the Flaky tests management process to help us increase master stability.

Please let us know your feedback in the Engineering Productivity issue tracker.

Related to #463694 (closed).

This change was generated by gitlab-housekeeper using the Keeps::QuarantineFlakyTests keep.

To provide feedback on your experience with gitlab-housekeeper please create an issue with the label GitLab Housekeeper and consider pinging the author of this keep.

Edited by Auto-quarantining bot

Merge request reports