On 08.06.2015 15:37, Ivan Zhakov wrote: > I didn't think that any test suite failure should be called as release > blocker and after thinking more I agree that this particular failure > also should not be considered as blocker. Even it breaks my release > testing scripts, since failure in one configurations causes abort of > all test run :(
Yeah, that's painful ... of course, you can always fix your scripts. :) > My original intention was "we need this fix in 1.9.x before 1.9.0 to > speed up release, because it could slowdown release signing process", > but I should put this in Note field instead marking nomination as a > release-blocker. Ack. > But I think that test failures could be release blocker in case it > happens in common configuration or affects many tests. Ack, makes sense. -- Brane
