[jbossts-issues] [JBoss JIRA] (JBTM-3090) LRA TCK failures need to report more context to facilitate debugging

[Michael Musgrove (Jira)]

Michael Musgrove created JBTM-3090:
--------------------------------------

             Summary: LRA TCK failures need to report more context to facilitate debugging
                 Key: JBTM-3090
                 URL: https://issues.jboss.org/browse/JBTM-3090
             Project: JBoss Transaction Manager
          Issue Type: Task
          Components: LRA
    Affects Versions: 5.9.2.Final
            Reporter: Michael Musgrove
            Assignee: Michael Musgrove
             Fix For: 5.next


The TCK test failure message reports 

> failures.forEach(f -> System.out.printf("%s%n", f));

where f is the failure reason. There is also a verbose option which prints out the stack trace where the failure was reported. But in some failure cases these two pieces of information are insufficient to debug the failure. It would be nice if the resources that participated in the test also logged information which could be reported for more effective analysis of the reasons for the failure. This last requirement may affect the TCK itself so the code in the eclipse microprofile-lra repo should be analysed as well.



--
This message was sent by Atlassian Jira
(v7.12.1#712002)