>sorry, but something IS wrong with the log and the weighting. No matter how
>you twist and turn <G>. Fortunately, with 1.29 it finally is apparent, even
>to the naked eye:
OK -- I've gone through the issues and reports with 1.29, and it looks like
there is only one outstanding issue (albeit a complex one): Something
isn't working properly, that can cause failed tests not to get reported in
the log, and also prevent the actions from running.
If there are other issues that I've overlooked, please do let me know. I
want to make sure that all the issues get addressed, but it looks like this
is the only one left.
If that's correct, would it be possible to turn on the debugging in Declude
JunkMail (LOGLEVEL DEBUG) long enough to let one of these issues reproduce
itself? I think that would be the optimal way to continue, as it seems
that this is happening often enough that it wouldn't take too long to get
one of these to reproduce. With the debug logs, it will be a lot easier to
track down the problem, and nail it once and for all.
-Scott
---
[This E-mail was scanned for viruses by Declude Virus (http://www.declude.com)]
---
This E-mail came from the Declude.JunkMail mailing list. To
unsubscribe, just send an E-mail to [EMAIL PROTECTED], and
type "unsubscribe Declude.JunkMail". You can E-mail
[EMAIL PROTECTED] for assistance. You can visit our web
site at http://www.declude.com .
---
[This E-mail was scanned for viruses by Declude Virus (http://www.declude.com)]
