[MAGNOLIA-7074] Fix Flaky AsyncCommandLockingTest#oneCommandIsResponsibleForUnlockingThenNoExceptionOccurs test Created: 15/Jun/17  Updated: 03/Nov/17  Resolved: 03/Nov/17

Status: Closed
Project: Magnolia
Component/s: None
Affects Version/s: 5.5.4
Fix Version/s: None

Type: Task Priority: Neutral
Reporter: Ilgun Ilgun Assignee: Unassigned
Resolution: Obsolete Votes: 0
Labels: quickwin
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Template:
Acceptance criteria:
Empty
Task DoR:
Empty
Date of First Response:
Epic Link: Improve QA setup

 Description   

The test is randomly failing due to timing issues since it aims to check async commands and we have to time it correctly in order to have the order one throw exception or not.

One solution might be to have the first command run for a longer period and therefore the second one will hit to LockException.

Other one would be to have something similar to -> https://git.magnolia-cms.com/projects/PLATFORM/repos/main/pull-requests/358/overview



 Comments   
Comment by Antti Hietala [ 03/Nov/17 ]

Haven't seen this failure recently. Pls reopen if it occurs. Closing as obsolete.

Generated at Mon Feb 12 04:20:29 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.