.NET Framework tests reports `InvalidOperationException: ICLRListenerInternal.Release()`

[masesdevelopers]

Describe the bug
At the end of the execution the following error is raised:

InvalidOperationException: ICLRListenerInternal.Release(): Report this condition and we will investigate on it.

To Reproduce
Steps to reproduce the behavior:

1. Go to build.yaml
2. Click on Run workflow
3. Wait execution of tests
4. Open tests executed on Windows and net462

Expected behavior
Just like the other tests, no error shall be reported

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

Environment (please complete the following information):

• OS
  • Windows - Version: [e.g. Windows 11]
  • MacOS - Version: [e.g. 14]
  • Linux
    • Distribution: [e.g. Ubuntu]
    • Version: [e.g. 22.04]
• .NET
  • .NET Framework
  • .NET 8
  • .NET 9
• JVM
  • Oracle - Version: [e.g. 11]
  • GraalVM - Version: [e.g. 11]
  • Temurin - Version: [e.g. 11]
  • Zulu - Version: [e.g. 11]
  • Microsoft - Version: [e.g. 11]
  • Corretto - Version: [e.g. 11]
  • Other
    • Distribution:
    • Version:

Additional context
Add any other context about the problem here.

[masesdevelopers]

Since the tests activate the report of underlying subsystem event or exception using:

KNet/tests/net/Common/SharedKNetCore.cs

Line 82 in fb60329

ApplicationWriteEventOrExceptionOnCmdLine = true;

this error probably comes from JCOBridge: set the value to false and verify if it is raised.
Based on the results of the previous test, the bug can be propagated to https://github.com/masesgroup/JCOBridgePublic/issues or eventually to https://github.com/masesgroup/JNet/issues

[masesdevelopers]

Since the tests activate the report of underlying subsystem event or exception using:

KNet/tests/net/Common/SharedKNetCore.cs

Line 82 in fb60329
ApplicationWriteEventOrExceptionOnCmdLine = true;

this error probably comes from JCOBridge: set the value to false and verify if it is raised. Based on the results of the previous test, the bug can be propagated to https://github.com/masesgroup/JCOBridgePublic/issues or eventually to https://github.com/masesgroup/JNet/issues

Executing the tests the error is not reported so the error is reported from the underlying JCOBridge subsystem