Github user ryan-williams commented on the issue:
https://github.com/apache/spark/pull/16311
While preparing this PR, I noted that spark-tags has 3 test-tags that are
each specifically directed at each of three modules' tests:
- `DockerTest` -> external/docker-integration-tests
- `ExtendedHiveTest` -> sql/hive
- `ExtendedYarnTest` -> resource-managers/yarn
It may make more sense to just move each test-tag to its corresponding
module, and do away with the spark-tags test-JAR altogether; I don't see that
their status as "tags" is the most important axis on which to physically group
them.
LMK if anyone would prefer that and I'll do it.
cc @vanzin @srowen
---
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]
