[jboss-jira] [JBoss JIRA] (WFCORE-3177) The BootLoggingPatchingStateTestCase fails if the message assertion is flipped

[James Perkins (JIRA)]

James Perkins created WFCORE-3177:
-------------------------------------

             Summary: The BootLoggingPatchingStateTestCase fails if the message assertion is flipped
                 Key: WFCORE-3177
                 URL: https://issues.jboss.org/browse/WFCORE-3177
             Project: WildFly Core
          Issue Type: Bug
          Components: Patching , Test Suite
            Reporter: James Perkins
            Assignee: Alexey Loubyansky
            Priority: Blocker
             Fix For: 3.0.0.CR1


The {{BootLoggingPatchingStateTestCase}} tests two patches which use a different version and product id for the patch. The tests currently pass because of the order of the [{{Collection.containsAll()}}|https://github.com/wildfly/wildfly-core/blob/0b51f7c1cce7286bf4f4e3f5c9250bf351bbdf1b/testsuite/patching/src/test/java/org/jboss/as/test/patching/BootLoggingPatchingStateTestCase.java#L151]. However if this is flipped the tests fail.

It appears that the messages logged always contain the "WildFly" product id. Also the UUID for the failing examples seems to not be logged either.

Example of logged messages for the "lp1" patch in the test:
{code}
WildFly cumulative patch ID is: 936c95a3-f08e-4fc0-9917-f7feead4ef25, one-off patches include: 00699c2c-84a5-4bdb-b469-8c2fd66afe2a, c6df609e-1620-4369-af48-8041d4be093f
WildFly cumulative patch ID is: 936c95a3-f08e-4fc0-9917-f7feead4ef25, one-off patches include: 00699c2c-84a5-4bdb-b469-8c2fd66afe2a, c6df609e-1620-4369-af48-8041d4be093f
{code}

It looks like the same message is logged twice. However the following is what's expected:
{code}
lp1 cumulative patch ID is: base, one-off patches include: 50a820e4-3659-437d-86f2-fa1d64728adb
WildFly cumulative patch ID is: 936c95a3-f08e-4fc0-9917-f7feead4ef25, one-off patches include: 00699c2c-84a5-4bdb-b469-8c2fd66afe2a, c6df609e-1620-4369-af48-8041d4be093f
{code}

I'm not sure if this is just an issue with the test or if there is a bug in patching.



--
This message was sent by Atlassian JIRA
(v7.2.3#72005)