[Commented] (SUREFIRE-1780) Print JPMS errors from native stream of the fork JVM

Previous Topic Next Topic
classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view

[Commented] (SUREFIRE-1780) Print JPMS errors from native stream of the fork JVM

Herve Boutemy (Jira)

    [ https://issues.apache.org/jira/browse/SUREFIRE-1780?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17264081#comment-17264081 ]

Vaïk Duhautois commented on SUREFIRE-1780:

I recently upgrade from 3.0.0-M4 to 3.0.0-M5 and I have something wrong with some JVM logs, and it may be related to this issue you've been working on :

[INFO] -------------------------------------------------------
[INFO] -------------------------------------------------------
[ERROR] Jan 13, 2021 12:09:44 PM org.junit.platform.launcher.core.LauncherConfigurationParameters loadClasspathResource
[ERROR] INFO: Loading JUnit Platform configuration parameters from classpath resource [file:/home/vaik/workspace/concord-e2e-tests/target/test-classes/junit-platform.properties].
[INFO] Running com.concordnow.e2e.tests.account.login.LoginTest
[ERROR] WARNING: An illegal reflective access operation has occurred
[ERROR] WARNING: Illegal reflective access by retrofit2.Platform (file:/home/vaik/.m2/repository/com/squareup/retrofit2/retrofit/2.9.0/retrofit-2.9.0.jar) to constructor java.lang.invoke.MethodHandles$Lookup(java.lang.Class,int)
[ERROR] WARNING: Please consider reporting this to the maintainers of retrofit2.Platform
[ERROR] WARNING: Use --illegal-access=warn to enable warnings of further illegal reflective access operations
[ERROR] WARNING: All illegal access operations will be denied in a future release{code}
Some INFO or WARNING logs are now tagged with [ERROR] and it's really confusing.

Do you think it's related to this issue ?


Vaïk Duhautois

> Print JPMS errors from native stream of the fork JVM
> ----------------------------------------------------
>                 Key: SUREFIRE-1780
>                 URL: https://issues.apache.org/jira/browse/SUREFIRE-1780
>             Project: Maven Surefire
>          Issue Type: Improvement
>          Components: process forking
>         Environment: Java 9+
>            Reporter: Tibor Digana
>            Assignee: Tibor Digana
>            Priority: Major
>             Fix For: 3.0.0-M5
> When JVM prints own logs to the native stream, the surefire stream becomes corrupted. These are printed in a dump file and they are supposed a stream corruption. We can extract some special logs from this corrupted stream.
> This issue is based on the last discussion in SUREFIRE-1262.

This message was sent by Atlassian Jira