Add workaround in log4j legacy API test
authorAlexandre Montplaisir <alexmonthy@voxpopuli.im>
Thu, 2 Jun 2016 22:41:18 +0000 (18:41 -0400)
committerAlexandre Montplaisir <alexmonthy@voxpopuli.im>
Thu, 2 Jun 2016 22:41:18 +0000 (18:41 -0400)
commitb342ee75b8f1dd103fc049095de6e1242fc119a6
tree58cb6839964d806dc339908b3e9bd6fff02f1ea7
parent0fcd7d54f65aac677d9431b3ff95c9274646970c
Add workaround in log4j legacy API test

log4j doesn't seem to make it possible clear loggers the way
JUL does, so all loggers defined in previous tests are still
present in subsequent ones.

This coupled with the fact that the legacy agent attaches one
handler to the root logger, all loggers defined in previous
tests end up being visible by LTTng.

Ease up the passing requirement for a test so that it can
still work in these conditions.

Signed-off-by: Alexandre Montplaisir <alexmonthy@voxpopuli.im>
lttng-ust-java-tests-log4j/src/test/java/org/lttng/ust/agent/integration/events/Log4jLegacyApiIT.java
This page took 0.022739 seconds and 4 git commands to generate.