*** --- Core Loader Conformance Suite --- *** --- Test result log for c:\omxil\test\compload_coreconftestinput.txt Core_Conf_SetTraceflags 0x0000003f Core_Conf_AddTest SetupTunnel Core_Conf_AddTest CompLoad OMX_CONF_ExecuteTests ## ## SetupTunnel ## calling OMX_Init Call processing time limit for OMX_Init exceeded : limit = 20 actual = 2495 Loading the 2 test components used in the OMX_SetupTunnel test scenarios calling OMX_GetHandle pHandle : 0x2886eb5c cComponentName : OMX.Symbian.testcomp1 pAppData : 0x41652c pCallBacks : 0x4122f0 Call processing time limit for OMX_GetHandle exceeded : limit = 20 actual = 70 calling OMX_GetHandle pHandle : 0x2886eb5c cComponentName : OMX.Symbian.testcomp2 pAppData : 0x416504 pCallBacks : 0x4122f0 Call processing time limit for OMX_GetHandle exceeded : limit = 20 actual = 40 Testing SetupTunnel case 1: Both interop profile components in loaded state calling OMX_SetupTunnel hOutput : 0x288b1374 nPortOutput : 1 hInput : 0x288b14d0 nPortInput : 0 Testing SetupTunnel case 2: 1st comp not supporting tunneling, 2nd comp supporting tunneling and in loaded state calling OMX_SetupTunnel hOutput : 0x288b1374 nPortOutput : 1 hInput : 0x288b14d0 nPortInput : 0 Testing SetupTunnel case 3: 1st comp supporting tunneling and in loaded state, 2nd comp not supporting tunneling calling OMX_SetupTunnel hOutput : 0x288b1374 nPortOutput : 1 hInput : 0x288b14d0 nPortInput : 0 Testing SetupTunnel case 4: 1st comp supporting tunneling and in state other than loaded and port enabled, 2nd comp supporting tunneling and in loaded state calling OMX_SetupTunnel hOutput : 0x288b1374 nPortOutput : 1 hInput : 0x288b14d0 nPortInput : 0 Testing SetupTunnel case 5: 1st comp supporting tunneling and in loaded state, 2nd comp supporting tunneling and in state other than loaded and port enabled calling OMX_SetupTunnel hOutput : 0x288b1374 nPortOutput : 1 hInput : 0x288b14d0 nPortInput : 0 Testing SetupTunnel case 6: 1st comp supporting tunneling and in loaded state, 2nd comp supporting tunneling and in loaded state and ports incompatible calling OMX_SetupTunnel hOutput : 0x288b1374 nPortOutput : 1 hInput : 0x288b14d0 nPortInput : 0 Testing SetupTunnel case 7: 1st comp NULL, 2nd comp supporting tunneling and in loaded state calling OMX_SetupTunnel hOutput : 0x0 nPortOutput : 0 hInput : 0x288b14d0 nPortInput : 0 Testing SetupTunnel case 8: 1st comp supporting tunneling and in loaded state, 2nd comp NULL calling OMX_SetupTunnel hOutput : 0x288b1374 nPortOutput : 1 hInput : 0x0 nPortInput : 0 Testing SetupTunnel case 9: 1st comp NULL, 2nd comp supporting tunneling and in state other than loaded and port enabled calling OMX_SetupTunnel hOutput : 0x0 nPortOutput : 0 hInput : 0x288b14d0 nPortInput : 0 Testing SetupTunnel case 10: 1st comp supporting tunneling and in state other than loaded and port enabled, 2nd comp NULL calling OMX_SetupTunnel hOutput : 0x288b1374 nPortOutput : 1 hInput : 0x0 nPortInput : 0 Testing SetupTunnel case 11: 1st comp supporting tunneling and in invalid state, 2nd comp supporting tunneling and in loaded state calling OMX_SetupTunnel hOutput : 0x288b1374 nPortOutput : 1 hInput : 0x288b14d0 nPortInput : 0 Testing SetupTunnel case 12: 1st comp supporting tunneling and in loaded state, 2nd comp supporting tunneling and in invalid state calling OMX_SetupTunnel hOutput : 0x288b1374 nPortOutput : 1 hInput : 0x288b14d0 nPortInput : 0 Testing SetupTunnel case 13: 1st comp supporting tunneling and in loaded state and bad port index, 2nd comp supporting tunneling and in loaded state calling OMX_SetupTunnel hOutput : 0x288b1374 nPortOutput : 1 hInput : 0x288b14d0 nPortInput : 0 Testing SetupTunnel case 14: 1st comp supporting tunneling and in loaded state, 2nd comp supporting tunneling and in loaded state and bad port index calling OMX_SetupTunnel hOutput : 0x288b1374 nPortOutput : 1 hInput : 0x288b14d0 nPortInput : 0 Testing SetupTunnel case 15: With bad parameters : Both comp handles NULL calling OMX_SetupTunnel hOutput : 0x0 nPortOutput : 0 hInput : 0x0 nPortInput : 0 Testing SetupTunnel case 16: With Output Port Component and Input Port Component passed in reverse order calling OMX_SetupTunnel hOutput : 0x288b14d0 nPortOutput : 0 hInput : 0x288b1374 nPortInput : 1 Unloading the 2 test components used in the OMX_SetupTunnel test scenarios calling OMX_FreeHandle pHandle : 0x2886eb68 calling OMX_FreeHandle pHandle : 0x2886eb68 calling OMX_Deinit *** SetupTunnel FAILED ## ## CompLoad ## calling OMX_Init Call processing time limit for OMX_Init exceeded : limit = 20 actual = 1250 Testing with the dummy test components calling OMX_GetHandle pHandle : 0x2888ec6c cComponentName : OMX.Symbian.testcomp1 pAppData : 0 pCallBacks : 0x4121a4 Call processing time limit for OMX_GetHandle exceeded : limit = 20 actual = 50 calling OMX_GetComponentVersion hComponent : 0x288d12b4 pComponentName : 0x2888ebec pComponentVersion : 0x2888ebe8 pSpecVersion : 0x2888ebe4 calling OMX_FreeHandle hComponent : 0x288d12b4 calling OMX_GetHandle pHandle : 0x2888ec6c cComponentName : OMX.Symbian.testcomp2 pAppData : 0 pCallBacks : 0x4121a4 calling OMX_GetComponentVersion hComponent : 0x288d13a8 pComponentName : 0x2888ebec pComponentVersion : 0x2888ebe8 pSpecVersion : 0x2888ebe4 calling OMX_FreeHandle hComponent : 0x288d13a8 Testing with error scenarios Testing with invalid component name calling OMX_GetHandle pHandle : 0x2888ec6c cComponentName : Invalid comp name pAppData : 0 pCallBacks : 0x4121a4 Testing with nonexisting component name calling OMX_GetHandle pHandle : 0x2888ec6c cComponentName : OMX.Vendor.nonexistingcomp pAppData : 0 pCallBacks : 0x4121a4 Testing with other invalid parameters calling OMX_GetHandle pHandle : 0 cComponentName : pAppData : 0 pCallBacks : 0 Testing OMX_FreeHandle with invalid component handle calling OMX_FreeHandle hComponent : 0 calling OMX_Deinit *** CompLoad FAILED *** *** Passed tests: *** *** Failed tests: *** CompLoad *** SetupTunnel *** *** Summary of tests executed *** ------------------------- *** Passed: 0 *** Failed: 2 *** Total : 2