I think we should disable these tests at least on jenkins (by disabling @BadApples?). These are really complex tests and I know Mark has put a lot of effort to stabilize them but they're still causing a lot of noise. I don't think they're "easy" to fix -- these "error code 11" is a JVM-level trap (that results from a resource deadlock, supposedly) -- but I have a suspicion people simply stopped looking at these failures.
I really don't want to hurt anybody's feelings but there should be a "hard" limit of failures after which we consider a test unfixable and it should be excluded from normal jenkins runs. I tried to stabilize those tests myself and failed miserably. Dawid --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
