Fix and disable masterfs lockfile test which is failing since 17u18

[mbien]

this test was patched in past for similar reasons and can start failing again when the JDK updates.

testLockFile() is now disabled in CI

[lkishalmi]

If this happened and patched in the past, do we have a reference on that?

[lkishalmi]

A little more info would be good to be provided in this issue at least.

[mbien]

those tests monitor file IO by counting reads/writes. This calls something directly and eagerly which also does file IO. This method would have been called later indirectly by unrelated JDK API which would fail the tests - or worse - fail tests based on JDK update release or order of execution

[mbien]

If this happened and patched in the past, do we have a reference on that?

https://github.com/mbien/netbeans/commits/53fc45b42e1479ce0b1f1103d47cf5d99220ec19/platform/masterfs/test/unit/src/org/netbeans/modules/masterfs/filebasedfs/fileobjects/StatFilesTest.java

the hg archive repo seems to be down atm?

or #7410, #7974

[mbien]

merging to delivery so that we have CI again

[lahodaj]

I think I can live with this. (I would be completely OK with the isHeadless(), counting file accesses inevitably will be tricky and will need some code to warm up - alternative would be to trial-run one or more tests to warm up, and then do the real test run, but that's a bit tricky as well. So the @RandomlFails, well, it is what it is.)

[mbien]

we can revisit those test after #9151 is merged, because this will:

a) reduce the testing range and we can remove some of the patches again (e.g sections like if (version > 18) assume one read more etc)

b) we will have a list of tests which need to be migrated away from SM to JFR or other IO tracing methods and can handle them one by one.