kriegaex commented on PR #133: URL: https://github.com/apache/xalan-java/pull/133#issuecomment-1836480790
> > Question: Do the log lines "eat any bread", as we say in German? > > They do. Frankly, if CI fails (e.g. due to a failed test), I typically scroll the log to check the failure. The current 5900 lines are hard to scroll even with my quite powerful notebook. Navigating logs is also a developer skill. I never had any big problems doing so. Sure, 5900 lines are not little, but also not much. Maybe you want to select the option to open the raw log without fancy HTML navigation and syntax colouring instead. It scrolls much faster. Either way, this is totally out of scaope of this PR. The extensive logs you complain about do not come frommy changes but from stuff that was put in place by someone else and exists without this PR, too. Most OSS project using Maven Invoker 1. stream the fulllogs of the embedded Maven builds into their main build logs and 2. also activate debug logging for each IT build. I deactivated both already. So, I am considerate about this issue. The passing ITs produce next to no logs (only in case of an IT failure, the build log for that IT is being streamed), the unit tests not much, only the logged exceptions for the reproduced error cases, which are helpful context info. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@xalan.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@xalan.apache.org For additional commands, e-mail: dev-h...@xalan.apache.org
