You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Carsten Ziegeler (Jira)" <ji...@apache.org> on 2023/04/14 07:46:00 UTC

[jira] [Resolved] (SLING-2430) Testing tools: RetryLoop swallows the interesting exception

     [ https://issues.apache.org/jira/browse/SLING-2430?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Carsten Ziegeler resolved SLING-2430.
-------------------------------------
    Resolution: Won't Fix

> Testing tools: RetryLoop swallows the interesting exception
> -----------------------------------------------------------
>
>                 Key: SLING-2430
>                 URL: https://issues.apache.org/jira/browse/SLING-2430
>             Project: Sling
>          Issue Type: Improvement
>          Components: Testing
>            Reporter: Alexander Klimetschek
>            Priority: Minor
>
> The fail at the end of the RetryLoop() constructor does not report the last exception catches inside the loop, which is usually of interest. Instead, these are passed to reportException(), which turns out not really useful, since the fail will break through the outer code and the code would have to remember the exception, catch the AssertionError etc.
> It might still make sense to report *all* inner exceptions in the loop, but a good default behavior should include the actual exception right away in the fail().



--
This message was sent by Atlassian Jira
(v8.20.10#820010)