Github user srowen commented on the issue:
https://github.com/apache/spark/pull/19098
Hm, I wonder how that results in an assertion? that's a normal error case
and shouldn't cause an assert. Is it from a third-party library in this case,
like Arrow? really we should fix that somehow so that the user-visible contract
for this behavior never involves AssertionError.
Still, assertions ought to be _enabled_ during tests anyway, so I don't see
how this doesn't actually fire. If it only affects the Maven build I'd suspect
that maybe the scalatest-maven-plugin somehow doesn't turn on assertions? but
it has `-ea` in its command line.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org
For additional commands, e-mail: reviews-h...@spark.apache.org
