Re: Error building from source
ok, I've now fixed this test in the codebase (under ISIS-437) On 15 October 2013 16:57, james agada okwuiag...@gmail.com wrote: Thanks. On Mon, Oct 14, 2013 at 8:52 AM, Jeroen van der Wal jer...@stromboli.it wrote: There was a typo in the command. It should be: mvn clean install -DskipTests (note the capital T) On Mon, Oct 14, 2013 at 12:22 AM, james agada okwuiag...@gmail.com wrote: Thanks for the hint but still no luck. -- T E S T S --- SLF4J: Failed to load class org.slf4j.impl.StaticLoggerBinder. SLF4J: Defaulting to no-operation (NOP) logger implementation SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further details. the Mockery is not thread-safe: use a Synchroniser to ensure thread safety the Mockery is not thread-safe: use a Synchroniser to ensure thread safety the Mockery is not thread-safe: use a Synchroniser to ensure thread safety the Mockery is not thread-safe: use a Synchroniser to ensure thread safety the Mockery is not thread-safe: use a Synchroniser to ensure thread safety the Mockery is not thread-safe: use a Synchroniser to ensure thread safety the Mockery is not thread-safe: use a Synchroniser to ensure thread safety the Mockery is not thread-safe: use a Synchroniser to ensure thread safety the Mockery is not thread-safe: use a Synchroniser to ensure thread safety the Mockery is not thread-safe: use a Synchroniser to ensure thread safety the Mockery is not thread-safe: use a Synchroniser to ensure thread safety the Mockery is not thread-safe: use a Synchroniser to ensure thread safety the Mockery is not thread-safe: use a Synchroniser to ensure thread safety the Mockery is not thread-safe: use a Synchroniser to ensure thread safety the Mockery is not thread-safe: use a Synchroniser to ensure thread safety the Mockery is not thread-safe: use a Synchroniser to ensure thread safety the Mockery is not thread-safe: use a Synchroniser to ensure thread safety the Mockery is not thread-safe: use a Synchroniser to ensure thread safety the Mockery is not thread-safe: use a Synchroniser to ensure thread safety the Mockery is not thread-safe: use a Synchroniser to ensure thread safety the Mockery is not thread-safe: use a Synchroniser to ensure thread safety the Mockery is not thread-safe: use a Synchroniser to ensure thread safety Results : init_when_preDestroyMultiple(org.apache.isis.core.metamodel.specloader.ServiceInitializerTest): (..) init_when_postConstructMultiple(org.apache.isis.core.metamodel.specloader.ServiceInitializerTest): (..) Tests run: 1031, Failures: 2, Errors: 0, Skipped: 7 [INFO] [INFO] Reactor Summary: [INFO] [INFO] Apache Isis Core .. SUCCESS [5.771s] [INFO] Isis Core Unit Test Support ... SUCCESS [7.929s] [INFO] Isis Core AppLib .. SUCCESS [11.223s] [INFO] Isis Core Log4j Impls . SUCCESS [2.891s] [INFO] Isis Core MetaModel ... FAILURE [21.899s] [ On Sun, Oct 13, 2013 at 8:33 PM, Jeroen van der Wal jer...@stromboli.it wrote: Hi James, If you don't want to change the Isis code to have Maven ignore the failing test but still want to build Isis from source you could skip all tests [1] until this issue is resolved. [1] mvn clean install -Dskiptests Jeroen On Sun, Oct 13, 2013 at 8:48 PM, Dan Haywood d...@haywood-associates.co.ukwrote: Alongside the @Test of the failing tests. Make sure it is the org.junit.Ignore, not the Isis one in the applib. I take it you do my site tests., then :-)? Sorry to be brief, sent from my phone On 13 Oct 2013 19:07, james agada okwuiag...@gmail.com wrote: Where exactly am i to place the @Ignore? On Fri, Oct 11, 2013 at 4:07 PM, Dan Haywood d...@haywood-associates.co.ukwrote: Nice! I guess running a different JVM is altering the order of the methods being found. Could you raise a ticket (attach the above stacktrace) and I'll do a quick fix. In the meantime, suggest you add an @Ignore to your local copy of the failing test(s), so you aren't blocked. Thx Dan On 11 October 2013 16:02, james agada okwuiag...@gmail.com wrote: --- Test set:
Re: Error building from source
There was a typo in the command. It should be: mvn clean install -DskipTests (note the capital T) On Mon, Oct 14, 2013 at 12:22 AM, james agada okwuiag...@gmail.com wrote: Thanks for the hint but still no luck. -- T E S T S --- SLF4J: Failed to load class org.slf4j.impl.StaticLoggerBinder. SLF4J: Defaulting to no-operation (NOP) logger implementation SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further details. the Mockery is not thread-safe: use a Synchroniser to ensure thread safety the Mockery is not thread-safe: use a Synchroniser to ensure thread safety the Mockery is not thread-safe: use a Synchroniser to ensure thread safety the Mockery is not thread-safe: use a Synchroniser to ensure thread safety the Mockery is not thread-safe: use a Synchroniser to ensure thread safety the Mockery is not thread-safe: use a Synchroniser to ensure thread safety the Mockery is not thread-safe: use a Synchroniser to ensure thread safety the Mockery is not thread-safe: use a Synchroniser to ensure thread safety the Mockery is not thread-safe: use a Synchroniser to ensure thread safety the Mockery is not thread-safe: use a Synchroniser to ensure thread safety the Mockery is not thread-safe: use a Synchroniser to ensure thread safety the Mockery is not thread-safe: use a Synchroniser to ensure thread safety the Mockery is not thread-safe: use a Synchroniser to ensure thread safety the Mockery is not thread-safe: use a Synchroniser to ensure thread safety the Mockery is not thread-safe: use a Synchroniser to ensure thread safety the Mockery is not thread-safe: use a Synchroniser to ensure thread safety the Mockery is not thread-safe: use a Synchroniser to ensure thread safety the Mockery is not thread-safe: use a Synchroniser to ensure thread safety the Mockery is not thread-safe: use a Synchroniser to ensure thread safety the Mockery is not thread-safe: use a Synchroniser to ensure thread safety the Mockery is not thread-safe: use a Synchroniser to ensure thread safety the Mockery is not thread-safe: use a Synchroniser to ensure thread safety Results : init_when_preDestroyMultiple(org.apache.isis.core.metamodel.specloader.ServiceInitializerTest): (..) init_when_postConstructMultiple(org.apache.isis.core.metamodel.specloader.ServiceInitializerTest): (..) Tests run: 1031, Failures: 2, Errors: 0, Skipped: 7 [INFO] [INFO] Reactor Summary: [INFO] [INFO] Apache Isis Core .. SUCCESS [5.771s] [INFO] Isis Core Unit Test Support ... SUCCESS [7.929s] [INFO] Isis Core AppLib .. SUCCESS [11.223s] [INFO] Isis Core Log4j Impls . SUCCESS [2.891s] [INFO] Isis Core MetaModel ... FAILURE [21.899s] [ On Sun, Oct 13, 2013 at 8:33 PM, Jeroen van der Wal jer...@stromboli.it wrote: Hi James, If you don't want to change the Isis code to have Maven ignore the failing test but still want to build Isis from source you could skip all tests [1] until this issue is resolved. [1] mvn clean install -Dskiptests Jeroen On Sun, Oct 13, 2013 at 8:48 PM, Dan Haywood d...@haywood-associates.co.ukwrote: Alongside the @Test of the failing tests. Make sure it is the org.junit.Ignore, not the Isis one in the applib. I take it you do my site tests., then :-)? Sorry to be brief, sent from my phone On 13 Oct 2013 19:07, james agada okwuiag...@gmail.com wrote: Where exactly am i to place the @Ignore? On Fri, Oct 11, 2013 at 4:07 PM, Dan Haywood d...@haywood-associates.co.ukwrote: Nice! I guess running a different JVM is altering the order of the methods being found. Could you raise a ticket (attach the above stacktrace) and I'll do a quick fix. In the meantime, suggest you add an @Ignore to your local copy of the failing test(s), so you aren't blocked. Thx Dan On 11 October 2013 16:02, james agada okwuiag...@gmail.com wrote: --- Test set: org.apache.isis.core.metamodel.specloader.ServiceInitializerTest --- Tests run: 7, Failures: 2, Errors: 0, Skipped: 0, Time elapsed: 0.504 sec FAILURE! init_when_preDestroyMultiple(org.apache.isis.core.metamodel.specloader.ServiceInitializerTest) Time elapsed: 0.009 sec FAILURE! java.lang.AssertionError: Expected: exception with message a string containing Found more than one
