spark-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Josh Rosen <rosenvi...@gmail.com>
Subject Re: Avoiding unnecessary build changes until tests are in better shape
Date Wed, 05 Aug 2015 18:41:45 GMT
+1.  I've been holding off on reviewing / merging patches like the 
run-tests-jenkins Python refactoring for exactly this reason.

On 8/5/15 11:24 AM, Patrick Wendell wrote:
> Hey All,
>
> Was wondering if people would be willing to avoid merging build
> changes until we have put the tests in better shape. The reason is
> that build changes are the most likely to cause downstream issues with
> the test matrix and it's very difficult to reverse engineer which
> patches caused which problems when the tests are not in a stable
> state. For instance, the updates to Hive 1.2.1 caused cascading
> failures that have lasted several days now and in the mean time a few
> other build related patches were also merged - as these pile up it
> gets harder for us to have confidence those other patches didn't
> introduce problems.
>
> https://amplab.cs.berkeley.edu/jenkins/view/Spark-QA-Test/
>
> - Patrick
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@spark.apache.org
> For additional commands, e-mail: dev-help@spark.apache.org
>


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@spark.apache.org
For additional commands, e-mail: dev-help@spark.apache.org


Mime
View raw message