I’m running into something odd with the HLK 1607 “Static Tools Logo Test”; the 1607 tests are being used to certify the driver for Server 2016 Core.
The driver project has been recently updated to build with WDK 1803. It passes CA tests clean, passes the SDV “MustFix” rules, then VS2017 is used to produce the DVL.XML file (the x64.CodeAnalysis.Summary is assessment is in the file, with no defects listed, along with all the SDV rule results). This I drop into the target’s C:\DVL folder prior to running the HLK tests (and yes, I installed the latest HLK filters on the controller prior to running the test).
The failure I’m getting isn’t making much sense to me, and I was hoping someone here might have a suggestion into what HLK’s actual gripe is. The error I see in the log is:
DVL test failed:
Microsoft.StaticToolsLogo.ObjectModel.DvlException: DvlChecker: missing SDV DVL log content for driver ‘msdmfilt’ with the OS architecture ‘x64’.
at Microsoft.StaticToolsLogo.ObjectModel.DvlChecker.CheckDvl()
at DevfundTests.DvlTest.DvlCheck()
The error code is 0x0, and error text is “Error 0x00000000”.
The driver name in that message (“msdmfilt”) is a Microsoft driver used for testing, not the name of the driver I’m testing. So, yeah, *that* DVL isn’t there. But perhaps this is just a misleading error message, and it really has some complaint about the DVL.XML for the driver under test.
I used the same test controller and target a week or two ago for another driver, following the same procedures, and didn’t run into this. Comparing the DVL.XML files for differences, nothing is really jumping out at me.
Anything in particular I should suspect, here?
Thanks,
Dave