-
Bug
-
Resolution: Unresolved
-
Low
-
None
-
6.0.4, 6.2.0, 6.1.1, 6.9.0
-
5
-
Severity 3 - Minor
-
2
-
HTR
It's not easy to reproduce by normal application usage. Issue may occur on heavy app load. However, it's easy to reproduce the problem by SQL manipulation.
- Create plan with at least one test case
- Add this test to quarantine
- Use SQL to duplicate this test case in DB (test_case table)
- Run build
- Remove quarantine for this test
- Run build
Expected behavior
Test is no longer quarantined
Actual behavior
Removing quarantine action removed the quarantine from the newest test case in DB. The duplicated entity has still quarantine properties set and because of that quarantine for given test case is still in place. It's not possible to change that state via UI.
Quarantine processor should take into consideration only the newest test case or unleashing test should either remove quarantine properties from all test cases with given name and job (including duplicated ones). (Both perhaps?)
Workaround
Use REST to remove quarantine for duplicated test case.
- is caused by
-
BDEV-13684 Loading...