reef-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Julia Wang (QIUHE)" <>
Subject RE: List of special tests for release
Date Mon, 11 Dec 2017 21:16:05 GMT
Those will be part of the yarn tests. Just like running local runtime tests, we should run
those tests to ensure nothing is broken. If any, we should either modify the code or modify
the tests accordingly. For any new features that we need to add new yarn tests, we can just
add them into the list.


-----Original Message-----
From: Saikat Kanjilal [] 
Sent: Monday, December 11, 2017 1:13 PM
Subject: Re: List of special tests for release

I agree, however my question is whether we'll be able to keep this up to date in a disciplined
manner or will this be yet another thing to maintain that will fall by the wayside and become
eventually outdated.

On Mon, Dec 11, 2017 at 12:45 PM, Mariia Mykhailova <>

> Hi,
> REEF has features which are not covered by testing on local runtime 
> and the few examples we run manually when testing release in clusters.
> One example of such a feature is driver restart on .NET side - AFAIK 
> it is only covered in O.A.R.Examples.DriverRestart and requires a 
> cluster with special YARN settings to run (a comment in the code says 
> "Can only be run on HDInsight clusters with 
> set to greater than or equal to 
> 2."). This feature was broken and went unnoticed for several months. 
> I'm sure there are other features like this which are not documented 
> enough for the release manager to be aware of them (and more importantly of how to verify
that they still work).
> What do you think about putting together a list of such features and 
> the process of their testing to follow during the release? This way 
> we'd have a checklist for the release manager to verify testers' 
> reports against rather than rely on the authors of all individual 
> features to remember to test them and report back.
> -Mariia
View raw message