No, not really. I have a very similar problem on my current project. I had to remove the tests from the build process because I just don't have the time to figure out why the tests won't all run together as a group, even though they all run fine individually. And if I ever do figure out the source of the problem, it will almost certainly be due to Logback. On Wed, Apr 17, 2013 at 10:28 AM, ceki <ceki@qos.ch> wrote:
It sounds pretty pathetic to make a big deal out of clean builds. However, getting all the tests to pass consistently has proven to be a big challenge. Frustratingly enough, none of the failures have to do anything with the "actual" logback code but with test code.
On 17.04.2013 15:34, Donald McLean wrote:
"and there was much rejoicing."
On Wed, Apr 17, 2013 at 9:32 AM, ceki <ceki@qos.ch <mailto:ceki@qos.ch>>
wrote:
Hi all,
In light of recent improvements in the test suite, we had a streak of of 18 successive clean builds by Jenkins. It ended with a failure in ch.qos.logback.classic.net <http://ch.qos.logback.**classic.net<http://ch.qos.logback.classic.net>
.__SMTPAppender_**GreenTest.__testMultipleTo
[1].
In any case, we are making progress.
[1] http://logback.qos.ch/jenkins/**__job/logback/91/<http://logback.qos.ch/jenkins/__job/logback/91/>