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-unsubscr...@spark.apache.org For additional commands, e-mail: dev-h...@spark.apache.org