On Mon, 21 Nov 2011 17:39:17 +0100, Steve Ebersole
wrote:
> Why don't we just manually run the tests once against all the QA
> databases with logging cranked up to ferret out any of these string
> format issues.
Sure, that works for me
___
hibern
Why don't we just manually run the tests once against all the QA
databases with logging cranked up to ferret out any of these string
format issues. I just still do not see why we need to make this a
routine part of the CI runs and slow them down even more.
On Fri 18 Nov 2011 05:01:36 PM CST,
Reviewing your stack trace, I can see that you're using debugf, which
passes through to the logger. If you have an error in your format then
there is nothing which can be done about that by the logging framework.
You would get a similar error if you were using String.format()
directly with a
Can you send us (off-list) a copy of the CoreMessageLogger interface
along with the generated CoreMessageLogger_$logger class?
Thanks.
On 11/18/2011 09:06 AM, Hardy Ferentschik wrote:
> Hi,
>
> we recently discussed on IRC the need to run the builds with debug/trace
> level.
> I totally agree th
