Hi,

these randomly failing tests in BlazeDS were sort of annoying. Especially as I 
knew there wasn't actually anything wrong with the tests. I did notice that the 
a few tests on our build server seemed to always fail and on the ASF infra, 
they only tended to fail if the build server was under heavy load. So I think I 
found a timing problem and resolved this by completely refactoring the way the 
test-server is started and while at it also made sure the TestServer is only 
started once for every test class and not for every test. It definitely looks 
as if we might get the build stable now [😊]


Chris

Reply via email to