sure @michelletorres, this issue was not delivered in the retrospective due to unforeseeing the impact of the change.
This is a really simple change where only a :reliable metadata needs to be added to the test in order to make it part of a so-called Reliable test suite.
This test suite is running on each deployment and failures in this set of tests block the deployments.
This test is a very long-running one, taking at least 45 minutes, and runs only in the preprod (pre.gitlab.com) test environment since that environment has different settings than any other environments for garbage collection.
Failing to agree and understand that this test would increase a lot the deployment testing time, by being added to the reliable set of tests, the impact vs benefit is not clear. The test continues to run daily and we would be able to surface issues even if not adding the test to the deployment test suite.
Given this is a very long test and we want to have efficient deployment times, as well as this is can only be run on pre-production, this won't be promoted to :reliable . The test still proves valuable by running a few times a day only on pre-prod.