[jboss-jira] [JBoss JIRA] (WFLY-9937) Enable CompensationScopedTestCase as it was disabled based on intermittent failures

[Ondra Chaloupka (JIRA)]

     [ https://issues.jboss.org/browse/WFLY-9937?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ondra Chaloupka updated WFLY-9937:
----------------------------------
    Steps to Reproduce: 
I simulated the ordering of the tests as it was in the failing CI job - you can check here, it's hacky way:

https://github.com/ochaloup/wildfly/tree/WFLY-9871-reordering-testcases

for decreasing number of thread to be used the {{io}} subsystem could be changed.

{code}
<subsystem xmlns="urn:jboss:domain:io:2.0">
  <worker name="default" task-max-threads="3" io-threads="3" />
  <buffer-pool name="default"/>
</subsystem>
{code}

Tried to run with elytron as it was the case where intermittent failures happened. No idea about relationship of the issue and the elytron.

{code}
cd testsuite/integration/xts
mvn test -Delytron
{code}

  was:
I simulated the ordering of the tests as it was in the failing CI job - you can check here, it's hacky way:

https://github.com/ochaloup/wildfly/tree/WFLY-9871-reordering-testcases

for decreasing number of thread to be used the {{io}} subsystem could be changed.

Tried to run with elytron as it was the case where intermittent failures happened. No idea about relationship of the issue and the elytron.

{code}
cd testsuite/integration/xts
mvn test -Delytron
{code}



> Enable CompensationScopedTestCase as it was disabled based on intermittent failures
> -----------------------------------------------------------------------------------
>
>                 Key: WFLY-9937
>                 URL: https://issues.jboss.org/browse/WFLY-9937
>             Project: WildFly
>          Issue Type: Bug
>          Components: Test Suite, XTS
>    Affects Versions: 12.0.0.Final
>            Reporter: Ondra Chaloupka
>            Assignee: Ondra Chaloupka
>            Priority: Minor
>
> The CompensationScopedTestCase should be enabled again.
> It was disabled based on the intermittent failures at jira WFLY-9871. See the discussion there for more details.
> From my review it sounds that this could be a functional issue but it's hard to say as I was not able to reproduce the behaviour.



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