Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

"make test" (level 3) fails with 2 tests ("lprm Test1" and "cancel Test1") #33

Closed
michaelrsweet opened this issue Apr 20, 2003 · 4 comments

Comments

@michaelrsweet
Copy link
Collaborator

Version: 1.1.19rc2
CUPS.org User: pipitas

"make test" (level 3):

2 tests failed : "lprm Test1" und "cancel Test1"

Question: I have only 2 job IDs (6 and 108) in the page_log
(both with 6 pages/1 copy, both for printer test-1). I see
however with the "flood test" there are sent 2x 100 jobs
(textfile.txt). Shouldn't all jobs appear in the page_log?

I will do more tests on other machines...

@michaelrsweet
Copy link
Collaborator Author

CUPS.org User: pipitas

Did send this before I had finished...

It is on Linux, kernel 2.4.18, 512 MByte RAM, 1 GB Swap space, Pentium-IV, 1700 MHz.

@michaelrsweet
Copy link
Collaborator Author

CUPS.org User: mike

Can you attach a copy of the error_log file (/tmp/$USER/log/error_log for the tests)?

Also, do you get the same results from multiple runs?

From different test levels?

@michaelrsweet
Copy link
Collaborator Author

CUPS.org User: pipitas

I'll send the error_logs via e-Mail (I'm not sure if it is
useful for anyone to see these 2 file with 1 MB each...).

I got same results from 4 level 3 runs now regarding the
2 failed tests ("cancel Test1" and "lprm Test1"). I get
slightly varying results in the "page_log" -- but I don't
get more than 5 jobs listed, namely "2", "6", "7", "108"
and "109"...)

With level 2 testing, I don't get the two failures for
lprm and cancel.

Probably you want to change the testscript to allow for
a bigger error_log file size. My level 3 test prompted
at least 80 log rotations with the current setting of
MaxLogSize. I'll now hack it to have "MaxLogSize 0" and
repeat the exercise...

Oh dear! This produced an error_log of 125 MByte (in
LogLevel debug2) and a PDF test report of 21514 pages
(sized 20 MByte). Hmmm... now this is a good testimony to
the robustness of your htmldoc code too ;-)

I guess you won't really look at these data... I'm seeing
208 "Hint: Do you have ESP Ghostscript installed?" in the
log. Of course I have! It is 7.05.6, installed in /usr/bin/gs. And "/usr/bin/" is in the $PATH as noted (for
each single job) in the error_log messages:

"envp[0]="PATH=/tmp/root/bin/filter:/bin:/usr/bin"

For now, I will hack the script again and set "LogLevel
debug" for some more sane data size to send you....

@michaelrsweet
Copy link
Collaborator Author

CUPS.org User: mike

This is fixed in CVS for the next release candidate.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant