On Mon, Jan 9, 2012 at 7:57 AM, Srinath Perera srin...@wso2.com wrote:
So our success so short lived?
Funny thing is Harashana's commits look unrelated from these test
failures.
Yes, they have nothing to do with those commits :(
--Srinath
-- Forwarded message --
I won't be too concerned. Even in the Axis2 Jenkins server you get weird
failures once in a while. Apart from the timestamp comparison test failure,
I don't see any real issue in the other 2 tests that failed.
On Mon, Jan 9, 2012 at 8:04 AM, Samisa Abeysinghe sam...@wso2.com wrote:
On Mon,
IMHO, we should change the tests that lead to transient errors if at all
possible ...
Fails positives will hurt us lot when we try to get everyone to really
serious about keeping the build unbroken
--Srinath
On Mon, Jan 9, 2012 at 8:08 AM, Afkham Azeez az...@wso2.com wrote:
I won't be too
Why do we not get rid of those ones that are likely to fail for no reason?
I too am concerned on false positives aspect. In other words, if there is a
failure, it better be one that we got to jump up and fix.
Apache Axis2 is far more simple to live with few failures here and there.
But not in
totally +1
On Mon, Jan 9, 2012 at 8:49 AM, Samisa Abeysinghe sam...@wso2.com wrote:
Why do we not get rid of those ones that are likely to fail for no reason?
I too am concerned on false positives aspect. In other words, if there is
a failure, it better be one that we got to jump up and fix.
