[jboss-jira] [JBoss JIRA] (WFCORE-3875) [jdk10] PatchModuleInvalidationWithRenamingFailureTestCase#test failure

Alexey Loubyansky (JIRA) issues at jboss.org
Mon May 28 12:35:00 EDT 2018


    [ https://issues.jboss.org/browse/WFCORE-3875?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13583053#comment-13583053 ] 

Alexey Loubyansky commented on WFCORE-3875:
-------------------------------------------

Looks like this is the cause:

Corrupted STDOUT by directly writing to native stream in forked JVM 1. Stream 'AccessManager:init Initialising JDK9 AccessManager'.
java.lang.IllegalArgumentException: Stream stdin corrupted. Expected comma after third character in command 'AccessManager:init Initialising JDK9 AccessManager'.
        at org.apache.maven.plugin.surefire.booterclient.output.ForkClient$OperationalData.<init>(ForkClient.java:511)
        at org.apache.maven.plugin.surefire.booterclient.output.ForkClient.processLine(ForkClient.java:209)
        at org.apache.maven.plugin.surefire.booterclient.output.ForkClient.consumeLine(ForkClient.java:176)
        at org.apache.maven.plugin.surefire.booterclient.output.ThreadedStreamConsumer$Pumper.run(ThreadedStreamConsumer.java:88)
        at java.base/java.lang.Thread.run(Thread.java:844)


> [jdk10] PatchModuleInvalidationWithRenamingFailureTestCase#test failure
> -----------------------------------------------------------------------
>
>                 Key: WFCORE-3875
>                 URL: https://issues.jboss.org/browse/WFCORE-3875
>             Project: WildFly Core
>          Issue Type: Bug
>          Components: Patching , Test Suite
>    Affects Versions: 5.0.0.Beta4
>            Reporter: Petr Kremensky
>            Assignee: Alexey Loubyansky
>
> org.jboss.as.patching.tests.PatchModuleInvalidationWithRenamingFailureTestCase#test from patching module of wildfly-core fails with JDK10, works fine with JDK9.
>    
> *reproduce*
> {noformat}
> wildfly-core]$ mvn  test -Dtest=PatchModuleInvalidationWithRenamingFailureTestCase#test -pl patching
> ...
> [INFO] Running org.jboss.as.patching.tests.PatchModuleInvalidationWithRenamingFailureTestCase
> [ERROR] Tests run: 1, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 0.363 s <<< FAILURE! - in org.jboss.as.patching.tests.PatchModuleInvalidationWithRenamingFailureTestCase
> [ERROR] test(org.jboss.as.patching.tests.PatchModuleInvalidationWithRenamingFailureTestCase)  Time elapsed: 0.359 s  <<< FAILURE!
> java.lang.AssertionError: 
> Expected: is <false>
>      but: was <true>
> 	at org.hamcrest.MatcherAssert.assertThat(MatcherAssert.java:20)
> 	at org.junit.Assert.assertThat(Assert.java:956)
> 	at org.junit.Assert.assertThat(Assert.java:923)
> 	at org.jboss.as.patching.tests.PatchModuleInvalidationWithRenamingFailureTestCase.test(PatchModuleInvalidationWithRenamingFailureTestCase.java:97)
> ...
> {noformat}
>    
> Environment:
> {noformat}
> Apache Maven 3.5.3 (3383c37e1f9e9b3bc3df5050c29c8aff9f295297; 2018-02-24T20:49:05+01:00)
> Maven home: /usr/lib/maven
> Java version: 10.0.1, vendor: Oracle Corporation
> {noformat}
> Byteman is being involved in the test.



--
This message was sent by Atlassian JIRA
(v7.5.0#75005)


More information about the jboss-jira mailing list