arn -Phadoop-2.3
>>>>> -Dhadoop.version=2.3.0 -Pkinesis-asl test
>>>>>
>>>>> Is anyone testing individual pull requests against Hadoop 2.4 or 2.6
>>>>> before the code is declared "clean"?
>>>>>
>>>
ith these arguments: -Pyarn -Phadoop-2.3
>>>> -Dhadoop.version=2.3.0 -Pkinesis-asl test
>>>>
>>>> Is anyone testing individual pull requests against Hadoop 2.4 or 2.6
>>>> before the code is declared "clean"?
>>>>
>>>> Fred
>
> Is anyone testing individual pull requests against Hadoop 2.4 or 2.6
>>> before the code is declared "clean"?
>>>
>>> Fred
>>>
>>> [image: Inactive hide details for Ted Yu ---05/15/2015 09:29:09
>>> AM---Jenkins build
/15/2015 09:29:09 AM---Jenkins build against hadoop 2.4 has been
>> unstable recently: https://amplab.cs.berkeley.edu/jenkins/
>>
>> From: Ted Yu
>> To: Andrew Or
>> Cc: "dev@spark.apache.org"
>> Date: 05/15/2015 09:29 AM
>> Subject: Re: Recent Spa
u ---05/15/2015 09:29:09
> AM---Jenkins build against hadoop 2.4 has been unstable recently: https]Ted
> Yu ---05/15/2015 09:29:09 AM---Jenkins build against hadoop 2.4 has been
> unstable recently: https://amplab.cs.berkeley.edu/jenkins/
>
> From: Ted Yu
> To: Andrew Or
is declared "clean"?
Fred
From: Ted Yu
To: Andrew Or
Cc: "dev@spark.apache.org"
Date: 05/15/2015 09:29 AM
Subject: Re: Recent Spark test failures
Jenkins build against hadoop 2.4 has been unstable recently:
https://amplab.cs.berkeley.edu/jenkins/
From
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/32831/consoleFull
:
[info] Building Spark with these arguments: -Pyarn -Phadoop-2.3
-Dhadoop.version=2.3.0 -Pkinesis-asl -Phive -Phive-thriftserver
Should PR builder cover hadoop 2.4 as well ?
Thanks
On Fri, May 15, 2015
Jenkins build against hadoop 2.4 has been unstable recently:
https://amplab.cs.berkeley.edu/jenkins/view/Spark/job/Spark-Master-Maven-with-YARN/HADOOP_PROFILE=hadoop-2.4,label=centos/
I haven't found the test which hung / failed in recent Jenkins builds.
But PR builder has several green builds la
> On 7 May 2015, at 01:41, Andrew Or wrote:
>
> Dear all,
>
> I'm sure you have all noticed that the Spark tests have been fairly
> unstable recently. I wanted to share a tool that I use to track which tests
> have been failing most often in order to prioritize fixing these flaky
> tests.
>
>
Makes sense.
Having high determinism in these tests would make Jenkins build stable.
On Mon, May 11, 2015 at 1:08 PM, Andrew Or wrote:
> Hi Ted,
>
> Yes, those two options can be useful, but in general I think the standard
> to set is that tests should never fail. It's actually the worst if tes
Hi Ted,
Yes, those two options can be useful, but in general I think the standard
to set is that tests should never fail. It's actually the worst if tests
fail sometimes but not others, because we can't reproduce them
deterministically. Using -M and -A actually tolerates flaky tests to a
certain e
Andrew:
Do you think the -M and -A options described here can be used in test runs ?
http://scalatest.org/user_guide/using_the_runner
Cheers
On Wed, May 6, 2015 at 5:41 PM, Andrew Or wrote:
> Dear all,
>
> I'm sure you have all noticed that the Spark tests have been fairly
> unstable recently.
Thanks for doing this. Testing infra is one of the most important parts of
a project, and this will make it easier to identify flaky tests.
On Wed, May 6, 2015 at 5:41 PM, Andrew Or wrote:
> Dear all,
>
> I'm sure you have all noticed that the Spark tests have been fairly
> unstable recently. I
Dear all,
I'm sure you have all noticed that the Spark tests have been fairly
unstable recently. I wanted to share a tool that I use to track which tests
have been failing most often in order to prioritize fixing these flaky
tests.
Here is an output of the tool. This spreadsheet reports the top 1
14 matches
Mail list logo
