rangareddy commented on issue #17055: URL: https://github.com/apache/hudi/issues/17055#issuecomment-5391451506
This issue was reviewed as part of the JIRA-migrated backlog triage (HUDI-9523). **Findings: not done, and the linked PR is closed without merging.** PR #13430 (`[HUDI-9523][Minor] [UT] Fix UT Only one SparkContext should be running in this JVM`) is **closed and unmerged**, so the `status:pr-available` label is misleading and worth removing. One practical problem with this ticket: the body carries only JIRA boilerplate, so the failing test is not named. "Only one SparkContext should be running in this JVM" is a generic symptom - a test class created a `SparkContext` without stopping a previous one, or two harnesses initialised concurrently in the same JVM - and it can come from any of dozens of suites. Without the suite name it is not actionable, and it will keep resurfacing under different tickets. Recommend attaching the failing test (and ideally the module) before this is picked up again. Keeping this open. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
