Failed
com.sun.ts.tests.jaxws.api.jakarta_xml_ws_handler.LogicalHandler.Client.ClientLogicalHandlerTest_from_standalone_reverse (from xml-ws-tck)
Error Message
test result: Error. VI classes and/or archives have not been built.
Stacktrace
test result: Error. VI classes and/or archives have not been built.
Standard Output
#Test Results (version 2) #Fri Mar 26 03:38:27 UTC 2021 #-----testdescription----- $file=/home/jenkins/agent/workspace/jakartaee-tck_master/xml-ws-tck/src/com/sun/ts/tests/jaxws/api/jakarta_xml_ws_handler/LogicalHandler/Client.java $root=/home/jenkins/agent/workspace/jakartaee-tck_master/xml-ws-tck/src assertion_ids=JAXWS\:SPEC\:9002 All binding implementations MUST support logical handlers being deployed in their handler chains.\nJAXWS\:SPEC\:9007 The handler chain for a binding is constructed by starting with the handler chain as returned by the HandlerResolver for the service in use and sorting its elements so that all logical handlers precede all protocol handlers.\nJAXWS\:SPEC\:9012 After injection has been completed, an implementation MUST call the lifecycle method annotated with PostConstruct, if present, prior to invoking any other method on a handler instance.\nJAXWS\:SPEC\:9014 For outbound messages handler processing starts with the first handler in the chain and proceeds in the same order as the handler chain. For inbound messages the order of processing is reversed\: processing starts with the last handler in the chain and proceeds in the reverse order of the handler chain.\nJAXWS\:SPEC\:9015 handleMessage\nJAXWS\:SPEC\:9015.1 Return true This indicates that normal message processing should continue. The runtime invokes handleMessage on the next handler or dispatches the message if there are no further handlers.\nJAXWS\:SPEC\:9017 Invoking close\: At the conclusion of an MEP, an implementation MUST call the close method of each handler that was previously invoked during that MEP via either handleMessage or handleFault.\nJAXWS\:SPEC\:9018 Conformance (Order of close invocations)\: Handlers are invoked in the reverse order in which they were first invoked to handle a message according to the rules for normal message processing\nWS4EE\:SPEC\:6005 See assertion html documents.\nWS4EE\:SPEC\:6008 See assertion html documents.\nWS4EE\:SPEC\:6010 See assertion html documents.\nWS4EE\:SPEC\:6015.1 See assertion html documents.\nWS4EE\:SPEC\:6015.2 See assertion html documents.\nWS4EE\:SPEC\:6015.3 See assertion html documents.\nWS4EE\:SPEC\:6028 See assertion html documents.\nWS4EE\:SPEC\:6051 See assertion html documents. classname=com.sun.ts.tests.jaxws.api.jakarta_xml_ws_handler.LogicalHandler.Client direction=reverse finder=cts id=ClientLogicalHandlerTest_from_standalone_reverse keywords=all ClientLogicalHandlerTest standalone_vehicle reverse service_eetest=yes testArgs=-ap jaxws-url-props.dat testName=ClientLogicalHandlerTest testProps=\ webServerHost webServerPort platform.mode test_directory=com/sun/ts/tests/jaxws/api/jakarta_xml_ws_handler/LogicalHandler #-----environment----- #-----testresult----- description=file\:/home/jenkins/agent/workspace/jakartaee-tck_master/xml-ws-tck/src/com/sun/ts/tests/jaxws/api/jakarta_xml_ws_handler/LogicalHandler/Client.java\#ClientLogicalHandlerTest_from_standalone_reverse end=Fri Mar 26 03\:38\:27 UTC 2021 environment=ts_unix execStatus=Error. VI classes and/or archives have not been built. harnessLoaderMode=Classpath Loader harnessVariety=Full Bundle javatestOS=Linux 3.10.0-1127.el7.x86_64 (amd64) javatestVersion=5.0 script=com.sun.ts.lib.harness.TSScript sections=script_messages TestRun start=Fri Mar 26 03\:38\:27 UTC 2021 test=com/sun/ts/tests/jaxws/api/jakarta_xml_ws_handler/LogicalHandler/Client.java\#ClientLogicalHandlerTest_from_standalone_reverse timeoutSeconds=1200 totalTime=1 work=/home/jenkins/agent/workspace/jakartaee-tck_master/xml-ws-tckwork/xml-ws-tck/com/sun/ts/tests/jaxws/api/jakarta_xml_ws_handler/LogicalHandler #section:script_messages ----------messages:(0/0)---------- #section:TestRun ----------messages:(0/0)---------- ----------log:(6/278)---------- ********************************************* TEST NOT RUN: This test cannot be run until you rebuild the test classes and/or archives associated with it. Please see the TCK documentation for more information on rebuildable tests. ********************************************* result: Not run. Test running... test result: Error. VI classes and/or archives have not been built.