This could be a potential issue that has been fixed in a new release of
the logmanager. I don't see anything obvious in the test that could
cause this, but if it continues to be an issue I'll take a harder look.
On 01/27/2013 04:44 PM, ci-builds(a)redhat.com wrote:
as7-master-testsuite-ip6 - Build # 6976 - Failure:
Check console output at to view the results.
Public:
http://hudson.jboss.org/hudson/job/as7-master-testsuite-ip6/6976
Internal:
http://lightning.mw.lab.eng.bos.redhat.com/jenkins/job/as7-master-testsui...
Test summary:
1 tests failed.
REGRESSION:
org.jboss.as.test.integration.logging.perdeploy.Log4jPropertiesTestCase.logsTest
Error Message:
Log file should contain line: Log4j logging bean - trace
_______________________________________________
jboss-as7-dev mailing list
jboss-as7-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
--
James R. Perkins
JBoss by Red Hat