On Thu, 16 Oct 2025 02:40:12 GMT, Leonid Mesnik <[email protected]> wrote:
>> Seems reasonable. >> >> Would be good to know why some tests have stopped failing though. >> >> Thanks > >> Seems reasonable. >> >> Would be good to know why some tests have stopped failing though. >> >> Thanks > Thank you for reveiw. > For most if not all cases the reason is Security Manager removal. The tests > failed to obtain permissions from virtual threads. > @lmesnik - would I be correct to say that you are on a mission to get rid of > ProblemList-Virtual completely? Just to mention that there are a number of > tests that already skip when the test main thread is a virtual thread. We may > need to track these down and replace them with `@requires test.thread.factory > == null` so that it is cleared from the test description. I am going to mark with requires all incompatible tests. There are some tests that manually check if virtual thread is enabled and the tests that already have virtual thread cases. I'll clean up them later. However, the ProblemList-Virtual will remain. It should contains the test that fail because of bugs. Including RFE to improve test to support virtual threads. The `@requires test.thread.factory == null` means that test is incompatible with thread factory and unlikely is going to be fixed for this mode. ------------- PR Comment: https://git.openjdk.org/jdk/pull/27834#issuecomment-3409283143
