>> Sure, do we know what broke it? > >I don't know yet. In theory whoever made those breaking changes should >have run the tests and seen the failures...
the problem is that these integration tests run on some environments, and on some not, on some they succeed sometime and sometimes not. this makes it so difficult to spot the real problem, maybe its just a racing condition or similar. thus my proposal to deactivate those tests in Jenkins for now and create a ticket for each one. we pick one to start with and ask around who has an environment where those tests fail every time or most times and try to find the issue. if it then runs on those environment we have a good chance that it will run on Jenkins as well. stefan
