You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Andrei Dulvac (Jira)" <ji...@apache.org> on 2020/04/02 09:08:00 UTC

[jira] [Assigned] (SLING-9089) RemoteLogDumperRule is too verbose if the logs cannot be retrieved

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

Andrei Dulvac reassigned SLING-9089:
------------------------------------

    Assignee: Andrei Dulvac

> RemoteLogDumperRule is too verbose if the logs cannot be retrieved
> ------------------------------------------------------------------
>
>                 Key: SLING-9089
>                 URL: https://issues.apache.org/jira/browse/SLING-9089
>             Project: Sling
>          Issue Type: Bug
>          Components: Apache Sling Testing Rules
>            Reporter: Valentin Olteanu
>            Assignee: Andrei Dulvac
>            Priority: Minor
>
> In case of a test failure, if the testlog servlet is not installed or cannot be accessed, RemoteLogDumperRule prints a very verbose message to stderr, confusing the user which thinks this is the root error:
> {code}
> Error occurred while fetching test logs from server [https://example.com/]
> org.apache.sling.testing.clients.ClientException: Expected HTTP Status: 200 . Instead 404 was returned!
> Response Content:
> <!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">
> <html>
>     <head><title>404 Resource at '/system/sling/testlog' not found: No resource found</title></head>
> ...
> {code}
> I think we can move this to debug level.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)