Tests: ClassPathEntryTest and ResourceAccumulatorTest fail on macOS

[jnehlmeier]

Description

Both tests depend on JDK FileWatcher and macOS is known to have a bad implementation of it. It is relatively slow and resource intensive.

I am not yet sure if these tests are implemented to aggressively or if ClassPathEntry and ResourceAccumulator simply do not work correctly on macOS.

• ClassPathEntryTest
  • testResourceRenamed
  • testResourceDeleted
  • testResourceCreated
• ResourceAccumulatorTest
  • testListensInNewDirectories
  • testRenameParentDirectory
  • testRenameDirectory
  • testRenameFile
  • testSymlinkInfiniteLoop
  • testSymlinks
  • testMultipleListeners
  • testDeleteFile

Steps to reproduce

Run dev tests via ANT on macOS.

Known workarounds

Links to further discussions

[jnehlmeier]

The following tests in ClassPathEntryTest are flaky as well. Sometimes they work, sometimes they don't. Seems like they don't work if they are executed last in the test run. ResourceAccumulatorManager.getActiveListenerCount() does not return the expected 0 in the failing case.

• testForResourceListenerLeaks_pathPrefixSetIsCollected
• testForResourceListenerLeaks_classPathEntryIsCollected