reef-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Mariia Mykhailova <mamyk...@microsoft.com>
Subject RE: REEF.NET test failures with current master
Date Thu, 07 Apr 2016 19:00:09 GMT
I've filed REEF-1323 as an umbrella and moved existing JIRAs under it. Also, I can repro failure
of TcpConnectionRetryTest.TestConnectionRetries, so I created JIRA for that.

-Mariia

-----Original Message-----
From: Boris Shulman [mailto:shulmanb@gmail.com] 
Sent: Thursday, April 7, 2016 10:02 AM
To: dev@reef.apache.org
Subject: RE: REEF.NET test failures with current master

Sounds good. Do we have  test owners so Jira's will be assigned to a specific people and resolved
with priority?

-----Original Message-----
From: "Markus Weimer" <markus@weimo.de>
Sent: ‎4/‎7/‎2016 10:00 AM
To: "dev@reef.apache.org" <dev@reef.apache.org>
Subject: Re: https://na01.safelinks.protection.outlook.com/?url=REEF.NET&data=01%7c01%7cmamykhai%40microsoft.com%7c44752d46989445ffc87208d35f0668dc%7c72f988bf86f141af91ab2d7cd011db47%7c1&sdata=koywMvJc8IES9BLNFopPlkBzgYpJ%2fH4TS%2b754AWdYEA%3d
test failures with current master

On 2016-04-06 20:39, Boris Shulman wrote:
> I am getting the same inconsistent behavior for tests.

Thanks for the confirmation. So it doesn't seem to be a machine issue, but an issue with our
tests. I feel quite uncomfortable with merging anything in this state.

Hence: How shall we proceed? I'm tempted to just disable the tests that give us trouble and
file one JIRA for each of them until we have a set of tests that passes reliably. That way,
we can at least know whether new code breaks something we reliably test.

What do you think?

Markus
Mime
View raw message