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

Ondra Chaloupka (Jira) issues at jboss.org
Thu Feb 21 07:37:00 EST 2019

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

Ondra Chaloupka commented on JBTM-3090:

[~mmusgrov] is this issue still relevant? I expect there could not enough information in the LRA TCK tests but just after refactoring it behaves a bit differently. So I'm just asking if this JIRA is not for to be reconsidered.

> 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
>            Priority: Major
>             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

More information about the jbossts-issues mailing list