none
USB Camera test issue for HLK Version 1607 build 14393 + client OS 10586x86 RRS feed

  • Question

  • Microsoft only accept HLK Version 1607 to test and submit after 10/29.

    So we test the usb camera device with client- Windows 10 Build 10586 and the HLK  Version 1607 (build14393). And found the client prompts "Test Authoring and Execution Framework [v5.8] has stopped working" dialog box, close the dialog and Test fails.

    How to solve this problem? 

    (Both can reproduce by using in-box driver usbvideo.sys and our vendor driver)

    (Also can reproduce in other USB camera devices  with in-box driver)

    NOTE. In the same test platform, we try different HLK/Client OS version to double confirm this issue:

    l   HLK 14393+ Client OS W10x86 14393 => Can't Reproduce

    l   HLK 14393+ Client OS W10x64 14393 => Can't Reproduce

    l   HLK 10586 + Client OS W10x86 10586 => Can't Reproduce

    l   HLK 10586 + Client OS W10x64 10586 => Can't Reproduce

    l   HLK 14393 + Client OS W10x86 10586 => 5 FAIL times

    l   HLK 14393 + Client OS W10x64 10586 => 1 FAIL times

    -----------------------------

    Test Environment: HLK Version 1607 build14393 + Windows 10 TH2 build 10586 (x86+x64)

    (Both can reproduce by using in-box driver usbvideo.sys and our vendor driver)

    HLK 14393 + Client OS W10x86 10586:   5 Fail Items:

    • Camera Driver Device Test - MediaCapture  TestConcurrentRecordAndPhotoCapture   (Has warning dialog box Test Authoring and Execution Framework[v5.8] has stopped working)
    • Camera Driver Device Test - MediaCapture TestPhotoCapture ((Has warning dialog box Test Authoring and Execution Framework[v5.8] has stopped working)
    • Camera Driver Device Test - MediaCapture TestVideoCapture  (Has warning dialog box Test Authoring and Execution Framework[v5.8] has stopped working)
    • Camera Driver Device Test - MediaCapture TestPreview
    • Camera Driver Registration, Metadata, and Dependency Test

    HLK 14393 + Client OS W10x64 10586:  1 Fail Item:

    • Camera Driver Registration, Metadata, and Dependency Test

    "Test Authoring and Execution Framework [v5.8] has stopped working" dialog box  

    [Detail Information]

    -------------------------------------------------

    Test Authoring and Execution Framework: TE.Host v5.8k for x86
    Structured exception was encountered: 0xC0000005 - EXCEPTION_ACCESS_VIOLATION
    MediaCaptureCPPTest.dll!DllGetActivationFactory+0x42272
    MediaCaptureCPPTest.dll!DllGetActivationFactory+0x45e3d
    MediaCaptureCPPTest.dll+0xa4d11
    MediaCaptureCPPTest.dll!DllGetActivationFactory+0x48bbb
    MediaCaptureCPPTest.dll!DllGetActivationFactory+0x48b55
    MediaCaptureCPPTest.dll!DllGetActivationFactory+0x9ecd2
    MediaCaptureCPPTest.dll!DllGetActivationFactory+0x8cc32
    MediaCaptureCPPTest.dll!?YOU_CAN_ONLY_DESIGNATE_ONE_CLASS_METHOD_TO_BE_A_TEST_METHOD_SETUP_METHOD@TaefMediaCaptureControlTests@Controls@MediaCaptureTests@@SGPBUFixtureMethodInfo@WEX@@XZ+0x43264
    MediaCaptureCPPTest.dll!?AACS_RecordScenarios_TAEF_PinTestMethodInfo@TaefMediaCaptureCppTests@CPP@Tests@MediaCapture@@SGPBUTestMethodInfo@WEX@@XZ+0x748
    MediaCaptureCPPTest.dll!?TestPerformance_VideoCapture_TAEF_PinTestMethodInfo@TaefMediaCaptureCppTests@CPP@Tests@MediaCapture@@SGPBUTestMethodInfo@WEX@@XZ+0x2a
    MediaCaptureCPPTest.dll+0xa7992
    MediaCaptureCPPTest.dll+0xa789c
    MediaCaptureCPPTest.dll!?TAEF_GetTestClassInfo@TaefMediaCaptureCppTests@CPP@Tests@MediaCapture@@SGPBUTestClassInfo@WEX@@XZ+0x9ad
    TE.Loaders.dll!LogWarningUnderSpecificSession+0x261
    TE.Host.dll!HostApplicationRunWithArgumentsInEnvironmentVariable+0x2e4c
    Te.Common.dll!?Initialize@CommandThread@TestExecution@WEX@@QAEXI@Z+0x579
    Te.Common.dll!?Initialize@CommandThread@TestExecution@WEX@@QAEXI@Z+0x222
    Te.Common.dll!?Initialize@CommandThread@TestExecution@WEX@@QAEXI@Z+0x6e4
    Te.Common.dll!?Initialize@CommandThread@TestExecution@WEX@@QAEXI@Z+0x4fe
    KERNEL32.DLL!BaseThreadInitThunk+0x24
    ntdll.dll!RtlCheckPortableOperatingSystem+0x16a
    ntdll.dll!RtlCheckPortableOperatingSystem+0x139
    If the stack trace above was incomplete, please set the _NT_SYMBOL_PATH environment variable.

     

    Thursday, October 13, 2016 3:24 AM