none
WHCK 2.1 is suddenly very slow in executing tests. RRS feed

  • General discussion

  • Hello,

    As of a few days ago, WHCK started executing tests very slowly. This was working as usual last week, and I completed WHCK testing on the same set of systems last week for 2 sets of drivers on Windows 7. I then moved to Windows 8 (systems re-imaged), and began testing. X86 completed all but one test, in which the SUT bugchecked, and x64 stopped on another test. This is not unusual. However, what is unusual, is that in the last 2 days, test execution is VERY slow.

    Example: NDISTest 6.5 - [2 Machine] - ConfigCheck.

    This test previously took only about 5 minutes to execute. Now it takes about a full 90 seconds for EACH step to execute. taking about 15-20 minutes for the test to complete.

    The steps I have taken to try to resolve/troubleshoot this:

    * Verified full communication (without packet loss) between SUT, DUT, and Controller.

    * Put SUT and DUT into unsafe, uninstalled, rebooted, then reinstalled the WHCK Client software.

    * Multiple reboots of the WHCK Controller/Server.

    * Updated Controller to Latest QFE, followed by a reboot.

    Has anyone seen this, or does MSFT have any help regarding this type of issue?

    Regards,

    ThomasW

    Tuesday, April 1, 2014 8:49 PM

All replies

  • It appears that there are a number of errors in the event log:

    Log Name:      HCK - Hardware Certification Kit
    Source:        Machine
    Date:          4/1/2014 3:37:38 PM
    Event ID:      0
    Task Category: None
    Level:         Error
    Keywords:      Classic
    User:          N/A
    Computer:      HCK-SERVER
    Description:
    Exception thrown looking for property Networking\LMSRole on machine (WHCK_W8X64_SUT)

    System.Collections.Generic.KeyNotFoundException: The given key was not present in the dictionary.
       at System.Collections.Generic.Dictionary`2.get_Item(TKey key)
       at Microsoft.Windows.Kits.Hardware.ObjectModel.DBConnection.WttMachine.GetFullPropertyByName(String propertyName)
    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
      <System>
        <Provider Name="Machine" />
        <EventID Qualifiers="0">0</EventID>
        <Level>2</Level>
        <Task>0</Task>
        <Keywords>0x80000000000000</Keywords>
        <TimeCreated SystemTime="2014-04-01T20:37:38.000000000Z" />
        <EventRecordID>156062</EventRecordID>
        <Channel>HCK - Hardware Certification Kit</Channel>
        <Computer>HCK-SERVER</Computer>
        <Security />
      </System>
      <EventData>
        <Data>Exception thrown looking for property Networking\LMSRole on machine (WHCK_W8X64_SUT)

    System.Collections.Generic.KeyNotFoundException: The given key was not present in the dictionary.
       at System.Collections.Generic.Dictionary`2.get_Item(TKey key)
       at Microsoft.Windows.Kits.Hardware.ObjectModel.DBConnection.WttMachine.GetFullPropertyByName(String propertyName)</Data>
      </EventData>
    </Event>

    • Edited by Thomasw_Tx Tuesday, April 1, 2014 9:11 PM
    Tuesday, April 1, 2014 9:06 PM
  • After trying numerous attempted solutions, the only way to fix was to UNINSTALL, then REINSTALL the controller/sql/studio on the server..

    -Thomas

    Wednesday, April 2, 2014 10:28 PM
  • Hi Thomas,

    If you using QFE008 kit, then don't use it. You may hit other issues as well related to TCPIP test cases.

    Thanks,

    Mudit

    Thursday, April 3, 2014 10:42 AM
  • Mudit,

    Unfortunately there is not any way to back-version WHCK. My reinstallation forced install of QFE008.

    -Thomas

    Thursday, April 3, 2014 2:44 PM
  • The slowness has come back, albeit not quite as bad as before.

    Event viewer is now not showing any errors. I have also changed the switch that the controller/SUT/DUT are connected to. Backchannel between SUT and DUT are direct connection, as recommended by Ethernet testing setup guide.

    -Thomas

    Thursday, April 3, 2014 8:43 PM
  • hi Thomas,

    Always download the new QFE's as a standalone installers not just HCKSetup.exe and also never upgrade the existing HCK Controller. Whenever new QFE release, setup new controller , don't disturb the old controller which you were previously using. Once you sure that new QFE is working good for you, then you can scrap old Controller.

    Thanks,

    Mudit

    Friday, April 4, 2014 3:25 AM