Re: [weld-dev] 1.1 incontainer test failures

Caused by commit https://github.com/weld/core/commit/add07e82562c8da314556a96678aa5840dc037ec How come CI didn't catch this? ---------------------------------- Failed tests: testBeginAlreadyLongRunningConversationThrowsException(org.jboss.jsr299.tck.tests.context.conversation.ClientConversationContextTest): Found class com.gargoylesoftware.htmlunit.WebResponse, but interface was expected testConversationBeginMakesConversationLongRunning(org.jboss.jsr299.tck.tests.context.conversation.ClientConversationContextTest): Found class com.gargoylesoftware.htmlunit.WebResponse, but interface was expected ... Tests run: 821, Failures: 22, Errors: 0, Skipped: 0 [INFO] ------------------------------------------------------------------------ [INFO] Reactor Summary: [INFO] [INFO] Weld: Build Configuration ......................... SUCCESS [1.699s] [INFO] Weld Parent ....................................... SUCCESS [1.052s] [INFO] Weld Implementation ............................... SUCCESS [3.503s] [INFO] Weld Integration Tests - JBoss Test Harness (JBoss AS) SUCCESS [6.885s] [INFO] Weld Porting Package for the CDI TCK .............. SUCCESS [1.523s] [INFO] Weld Integration Tests (JBoss AS) ................. SUCCESS [1:13.289s] [INFO] AtInject TCK runner for Weld ...................... SUCCESS [2.675s] [INFO] CDI TCK runner for Weld (JBoss AS) ................ FAILURE [5:18.466s] [INFO] Weld SE (Core) .................................... SKIPPED _______________________________________________ weld-dev mailing list weld-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-dev