You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Valentin Olteanu (Jira)" <ji...@apache.org> on 2020/02/19 14:29:00 UTC
[jira] [Commented] (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:comment-tabpanel&focusedCommentId=17040097#comment-17040097 ]
Valentin Olteanu commented on SLING-9089:
-----------------------------------------
Created a PR for this: https://github.com/apache/sling-org-apache-sling-testing-rules/pull/1
[~andrei.dulvac] would you mind checking this?
> 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
> 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)