Yes, I see the same. On Mon, Dec 12, 2016 at 5:52 PM, Marcelo Vanzin <van...@cloudera.com> wrote:
> Another failing test is "ReplSuite:should clone and clean line object > in ClosureCleaner". It never passes for me, just keeps spinning until > the JVM eventually starts throwing OOM errors. Anyone seeing that? > > On Thu, Dec 8, 2016 at 12:39 AM, Reynold Xin <r...@databricks.com> wrote: > > Please vote on releasing the following candidate as Apache Spark version > > 2.1.0. The vote is open until Sun, December 11, 2016 at 1:00 PT and > passes > > if a majority of at least 3 +1 PMC votes are cast. > > > > [ ] +1 Release this package as Apache Spark 2.1.0 > > [ ] -1 Do not release this package because ... > > > > > > To learn more about Apache Spark, please see http://spark.apache.org/ > > > > The tag to be voted on is v2.1.0-rc2 > > (080717497365b83bc202ab16812ced93eb1ea7bd) > > > > List of JIRA tickets resolved are: > > https://issues.apache.org/jira/issues/?jql=project%20% > 3D%20SPARK%20AND%20fixVersion%20%3D%202.1.0 > > > > The release files, including signatures, digests, etc. can be found at: > > http://people.apache.org/~pwendell/spark-releases/spark-2.1.0-rc2-bin/ > > > > Release artifacts are signed with the following key: > > https://people.apache.org/keys/committer/pwendell.asc > > > > The staging repository for this release can be found at: > > https://repository.apache.org/content/repositories/orgapachespark-1217 > > > > The documentation corresponding to this release can be found at: > > http://people.apache.org/~pwendell/spark-releases/spark-2.1.0-rc2-docs/ > > > > > > (Note that the docs and staging repo are still being uploaded and will be > > available soon) > > > > > > ======================================= > > How can I help test this release? > > ======================================= > > If you are a Spark user, you can help us test this release by taking an > > existing Spark workload and running on this release candidate, then > > reporting any regressions. > > > > =============================================================== > > What should happen to JIRA tickets still targeting 2.1.0? > > =============================================================== > > Committers should look at those and triage. Extremely important bug > fixes, > > documentation, and API tweaks that impact compatibility should be worked > on > > immediately. Everything else please retarget to 2.1.1 or 2.2.0. > > > > -- > Marcelo > > --------------------------------------------------------------------- > To unsubscribe e-mail: dev-unsubscr...@spark.apache.org > >
