Some tests fails

[masesdevelopers]

Describe the bug
Some of the test running in workflows fails.

To Reproduce
Steps to reproduce the behavior:

1. Go to Actions
2. Click on Windows or Linux workflow
3. Search tests not working
4. See error

Expected behavior
The tests shall execute without error

Screenshots
If applicable, add screenshots to help explain your problem.

Desktop (please complete the following information):

• OS: Windows/Linux
• Version Latest

Additional context
N/A

[masesdevelopers]

Enhance tests with a better matrix for java like it was done in https://github.com/masesgroup/JNet/blob/63eff5f9f7dcd1e5ada9bc727f4a43e91fe0718e/.github/workflows/build.yaml

[masesdevelopers]

Looking at the workflows, and within the jobs with errors, some problems are raised within the execution of the tests related to network.

However the problem seems not related to the network itself, apart from some tests which fails to bind on network interface.

The problem is a function named ShouldNotReachHere() which is invoked. Looking at the OpenJDK code, since many JDK used are nearly closed, the function jobjectRefType JNIHandles::handle_type(Thread* thread, jobject handle) (the one found in some jobs) invokes ShouldNotReachHere() in one possible point and the function can reach that point if OopStorage::EntryStatus returned from OopStorage::EntryStatus OopStorage::allocation_status(const oop* ptr) const is a value outside the possible values of OopStorage::EntryStatus.

But OopStorage::EntryStatus OopStorage::allocation_status(const oop* ptr) const returns only:

• ALLOCATED_ENTRY
• UNALLOCATED_ENTRY
• INVALID_ENTRY

Maybe a memory corruption alters the value returned back to jobjectRefType JNIHandles::handle_type(Thread* thread, jobject handle); last workflows version uploads core dumps, a deeper analysis shall be done.