D-1.3 Document Test Fails on Windows

[jacobsb]

Running IPP Everywhere™ Printer Self-Certification Tools v1.1 Update 4 on Windows, I am seeing a consistent failure on a particular document test.

Test D-1.3 Print PWG @ max resolution (black_1, gzip) fails. The same tests is passing on Mac and Linux. The test fails in what looks like the initial part of the test since it never waits for the job to complete and nothing is printed as part of the test.

Note that removing all other tests from the document-tests.test file and running just the one test results in a PASS. It seems there is something in the sequence of jobs that is spurring the failure.

Attached logs from Windows (failing) and Mac (passing) Document Test Results plist.zip

[michaelrsweet]

Weird, can you run the document tests with debug logging enabled? The "setdebug.bat" batch file from the repository can be used to enable it in the current session:

@rem Script to enable debug logging for IPPTOOL
set CUPS_DEBUG_LOG=ipptool.log
set CUPS_DEBUG_LEVEL=6
set "CUPS_DEBUG_FILTER=^(http|_http|ipp|_ipp|cupsDo|cupsGetResponse|cupsSend|cupsWrite)"

[jacobsb]

Weird, can you run the document tests with debug logging enabled? The "setdebug.bat" batch file from the repository can be used to enable it in the current session:

@rem Script to enable debug logging for IPPTOOL
set CUPS_DEBUG_LOG=ipptool.log
set CUPS_DEBUG_LEVEL=6
set "CUPS_DEBUG_FILTER=^(http|_http|ipp|_ipp|cupsDo|cupsGetResponse|cupsSend|cupsWrite)"

Please see attached plist with debug Windows-Debug Lexmark CX635adwe Document Results.plist.zip

[michaelrsweet]

@jacobsb Sorry, I meant for you to attach the "ipptool.log" file, which is the debug log... :)

[jacobsb]

@jacobsb Sorry, I meant for you to attach the "ipptool.log" file, which is the debug log... :)

I can't find the file ipptool.log . I am opening a terminal window and running the setdebug.bat file followed by running the document-tests.bat file. When the tests complete I am searching the computer for ipptool.log but nothing is found.

[michaelrsweet]

@jacobsb Hmm, I wonder if this is a power shell thing. OK, try the following commands before you run the document tests:

$Env:CUPS_DEBUG_LOG = "ipptool.log"
$Env:CUPS_DEBUG_LEVEL = "6"
$Env:CUPS_DEBUG_FILTER = "^(http|_http|ipp|_ipp|cupsDo|cupsGetResponse|cupsSend|cupsWrite)"

[jacobsb]

@jacobsb Hmm, I wonder if this is a power shell thing. OK, try the following commands before you run the document tests:

$Env:CUPS_DEBUG_LOG = "ipptool.log"
$Env:CUPS_DEBUG_LEVEL = "6"
$Env:CUPS_DEBUG_FILTER = "^(http|_http|ipp|_ipp|cupsDo|cupsGetResponse|cupsSend|cupsWrite)"

This is the error I get from running the first command: C:\Program Files\IPP Everywhere v1.1 Update 4 Printer Self-Certification Tools>$Env:CUPS_DEBUG_LOG = "ipptool.log" The filename, directory name, or volume label syntax is incorrect.

C:\Program Files\IPP Everywhere v1.1 Update 4 Printer Self-Certification Tools>

[michaelrsweet]

I think the issue is that the Windows project files didn't have the debug logging enabled for production builds. Will make sure to fix this for the next tools release.

[michaelrsweet]

Got word out-of-band that running the Linux self-cert tools doesn't result in the same failure, so we need to see what is different between Windows and Linux...