Github user vanzin commented on the issue:
https://github.com/apache/spark/pull/16311
> we have submodule-specific tags that have been module-sharded by their
tag-ness instead of by their submodule-relevance
Again, that is because of the issue with sbt complaining if you try to run
tests excluding the tags, and they don't exist. My original version of the
change, which caused test breakages, had the tags in the "test" directory of
the respective modules.
If you want more history, those tags used to be in a purely "test-tags"
module which was only used in test scope, but at some point more, non-test tags
were added to the same module and it was re-purposed, but caused the current
scalatest leakage issue.
So you have 3 options, actually, here:
- add the test-jar to all poms
- don't inherit from the Spark root pom
- remove the test tags and run those tests in all PR builds
Given how slow the current tests already are, and what I've said before
about VersionsSuite / YARN tests, I think the latter is ok. Maybe even ok as a
2.1 patch, now that 2.1.0 is out. But the other two are fine too.
---
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 [email protected] or file a JIRA ticket
with INFRA.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
