#438: repoclosure test is failing due to change in behavior upstream --------------------+-------------------------------------------------- Reporter: tflink | Owner: Type: defect | Status: new Priority: major | Milestone: Package Update Acceptance Test Plan Component: tests | Resolution: Keywords: | Blocked By: Blocking: | --------------------+--------------------------------------------------
Comment (by kparal):
If I were to decide, I'd just stop executing this test. I don't see anyone checking the results (mostly because we don't have the infrastructure in place to easily check the results and be notified of changes), thus I consider this test not being helpful (at the moment).
Plus, there's a daily report of rawhide repoclosure sent to the test list, and it's damn easy to execute it yourself locally for any our repos if you need to have a look.
I don't think it's currently worth the time to work on fixing the test.
Opinions?