jkesselm commented on PR #133: URL: https://github.com/apache/xalan-java/pull/133#issuecomment-1836433686
> > I agree that CI can be terser > > The opposite is true IMO. As we have no way to remote-debug CI, the only chance we have to identify problems there is verbose logging. Not debug level, of course, but default Maven logging. I split the difference. Default logging includes a lot of stuff that we really don't need to see every time right now, such as the javadoc warnings (best I was able to do was make them not be errors). Yes, the right answer is for someone to find time to clean up the javadoc at least enough to silence these complaints, but we don't need to know that during CI. Might be able to use grep to filter out [warning] lines, if the CI system has a portable way if doing that. If we need that any point, we can always check in a change to remove that filter temporarily. If I have to re-run a test locally for analysis after CI says there's an issue, I'm willing to do so. What I want from CI is usually an alert, not diagnosis. With the uncommon exception of transient problems that are hard to reproduce, or environments I can't replicate. But I may be out of date here. -- 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
