Added LogDumper rule with OAK-2721. Now you can make use of that in those test which fail intermittently to get better details around the failure
Chetan Mehrotra On Thu, Apr 2, 2015 at 3:21 PM, Chetan Mehrotra <[email protected]> wrote: > I implemented something on that line to get logs from remote server [1] > for Sling. Had plans to get that work for local jvm process also but never > got to complete it. Would try to get that done and see if that can be > leverage in Oak test. > > This feature would dump the logs as part of JUnit report rendered in > Jenkins. So along with failure stacktrace you can see what all logs were > captured in that run > > Chetan Mehrotra > [1] https://plus.google.com/+ChetanMehrotra/posts/Ao1w9SACKSh > > On Thu, Apr 2, 2015 at 2:43 PM, Davide Giannella <[email protected]> > wrote: > >> On 01/04/2015 07:29, Marcel Reutegger wrote: >> > The test failure was: >> > >> > Failed tests: >> > testProxyFlippedIntermediateByteChange( >> org.apache.jackrabbit.oak.plugins.se >> > gment.standby.ExternalSharedStoreIT): expected:<{ root = { ... } }> but >> > was:<{ root : { } }> >> > >> > >> > It's a bit difficult for me to see what went wrong, because the >> > test forcibly causes exceptions. So, many of the exceptions in >> > the log are kind of expected... >> > >> Could we catch all the logged exceptions with an ad-hoc appender and >> then in case output only the relevant ones? >> >> An example with custom appender for testing can be found in >> >> https://github.com/apache/jackrabbit-oak/blob/105f890e04ee990f0e71d88937955680670d96f7/oak-core/src/test/java/org/apache/jackrabbit/oak/plugins/index/property/Oak2077QueriesTest.java >> >> -- Davide >> >> >> >
