I'm making a guess, but where I'd be looking is in SLF4J at bogoInstruction. It is using Random to presumably compute the speed of the processor. But many CPUs have optimizations for this while some don't. And the processor's efficiency in computing a random number probably has little to do with most of the work being done in Logback. Just a guess though. Ralph noreply.ceki@qos.ch wrote:
Author: ceki Date: Thu Oct 23 15:13:49 2008 New Revision: 1864
Modified: logback/trunk/logback-core/src/test/java/ch/qos/logback/core/joran/SkippingInInterpreterTest.java
Log: - bug hunting
Modified: logback/trunk/logback-core/src/test/java/ch/qos/logback/core/joran/SkippingInInterpreterTest.java ============================================================================== --- logback/trunk/logback-core/src/test/java/ch/qos/logback/core/joran/SkippingInInterpreterTest.java (original) +++ logback/trunk/logback-core/src/test/java/ch/qos/logback/core/joran/SkippingInInterpreterTest.java Thu Oct 23 15:13:49 2008 @@ -34,6 +34,7 @@ import ch.qos.logback.core.status.Status; import ch.qos.logback.core.status.StatusManager; import ch.qos.logback.core.util.Constants; +import ch.qos.logback.core.util.StatusPrinter;
/** * Test the way Interpreter skips child elements in case of exceptions thrown by @@ -82,6 +83,7 @@ assertEquals(expectedInt, i); }
+ StatusPrinter.print(context); // check the existence of an ERROR status List<Status> statusList = sm.getCopyOfStatusList(); Status s0 = statusList.get(0); _______________________________________________ logback-dev mailing list logback-dev@qos.ch http://qos.ch/mailman/listinfo/logback-dev