thanks. All I'd need would be the base class, so that new tests can be written
to work across branches.
-steve
On 1 Jun 2015, at 18:45, Andrew Or
mailto:and...@databricks.com>> wrote:
It will be within the next few days
2015-06-01 9:17 GMT-07:00 Reynold Xin
mailto:r...@databricks.com>>:
I do
It will be within the next few days
2015-06-01 9:17 GMT-07:00 Reynold Xin :
> I don't think so.
>
>
> On Monday, June 1, 2015, Steve Loughran wrote:
>
>> Is this backported to branch 1.3?
>>
>> On 31 May 2015, at 00:44, Reynold Xin wrote:
>>
>> FYI we merged a patch that improves unit test l
I don't think so.
On Monday, June 1, 2015, Steve Loughran wrote:
> Is this backported to branch 1.3?
>
> On 31 May 2015, at 00:44, Reynold Xin > wrote:
>
> FYI we merged a patch that improves unit test log debugging. In order
> for that to work, all test suites have been changed to extend Sp
Is this backported to branch 1.3?
On 31 May 2015, at 00:44, Reynold Xin
mailto:r...@databricks.com>> wrote:
FYI we merged a patch that improves unit test log debugging. In order for that
to work, all test suites have been changed to extend SparkFunSuite instead of
ScalaTest's FunSuite. We also
FYI we merged a patch that improves unit test log debugging. In order for
that to work, all test suites have been changed to extend SparkFunSuite
instead of ScalaTest's FunSuite. We also added a rule in the Scala style
checker to fail Jenkins if FunSuite is used.
The patch that introduced SparkFun
