[MAGNOLIA-7589] DirectoryWatcher non-deterministically failing Integration tests Created: 23/Jul/19  Updated: 23/Jul/19

Status: Open
Project: Magnolia
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Bug Priority: Neutral
Reporter: Rishab Dhar Assignee: Unassigned
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Template:
Acceptance criteria:
Empty
Task DoD:
[ ]* Doc/release notes changes? Comment present?
[ ]* Downstream builds green?
[ ]* Solution information and context easily available?
[ ]* Tests
[ ]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Bug DoR:
[ ]* Steps to reproduce, expected, and actual results filled
[ ]* Affected version filled

 Description   

The test cases in class DirectoryWatchterTest test whether a file has been registered, deleted, or modified by the DirectoryWatcher. These tests are written with timeouts in order to compensate for factors such as slow disk or under pressure system (e.g. Jenkins build). Under certain circumstances these tests nevertheless fail and result in build failures for unrelated issues (an undesirable outcome).

Using completable futures API to have a hook on the watcher when it is completed. For this, the public API method register(...) which has a void return type needs to be unfortunately modified to have a return type of the list of futures which can be waited on for completion. The consequence is possibly breaking API changes for third parties which might be replying on this code. To reduce the impact a planned deprecation could be a solution to the side effect.


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