[Followup][JVM-Packages] re-architecture the xgboost testing framework
Open
- Dominant language
- C++
- Stars
- 28.8k
- Forks
- 8.9k
- Avg merge
- 1d 12h
- Merged PRs (30d)
- 54
Description
This is the follow up of https://github.com/dmlc/xgboost/pull/7836, which has introduced the barrier execution mode, and the killing SparkContext is not needed anymore, it's time to re-org the testing framework
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by reviewing pull request #7836 and its barrier execution mode changes, then trace the JVM-Packages testing framework and where it manages SparkContext. Reorganize the framework so it no longer kills SparkContext, and verify that the JVM package tests still run correctly under the new structure.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, scala
- Domain
- testing
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100