spark-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Sean Owen <so...@cloudera.com>
Subject Re: Is this a little bug in BlockTransferMessage ?
Date Wed, 10 Dec 2014 07:22:36 GMT
Oops, yes I see Java tests run with SBT now. You're right, it must be
because of the assertion. I can try to add '-ea' to the SBT build as a
closely-related change for SPARK-4159.

FWIW this error is the only one I saw once the Maven tests ran the Java tests.

On Wed, Dec 10, 2014 at 6:07 AM, Patrick Wendell <pwendell@gmail.com> wrote:
> Hey Nick,
>
> Thanks for bringing this up. I believe these Java tests are running in
> the sbt build right now, the issue is that this particular bug was
> flagged by the triggering of a runtime Java "assert" (not a normal
> Junit test assertion) and those are not enabled in our sbt tests. It
> would be good to fix it so that assertions run when we do the sbt
> tests, for some reason I think the sbt tests disable them by default.
>
> I think the original issue is fixed now (that Sean found and
> reported). It would be good to get assertions running in our tests,
> but I'm not sure I'd block the release on it. The normal JUnit
> assertions are running correctly.
>
> - Patrick

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


Mime
View raw message