Skip to content

[SPARK-58746][INFRA] Remove a dead lsof workaround and fix stale references in release tooling - #57972

Open
uros-b wants to merge 1 commit into
apache:masterfrom
uros-b:devexp-stale-paths-and-dead-lsof
Open

[SPARK-58746][INFRA] Remove a dead lsof workaround and fix stale references in release tooling#57972
uros-b wants to merge 1 commit into
apache:masterfrom
uros-b:devexp-stale-paths-and-dead-lsof

Conversation

@uros-b

@uros-b uros-b commented Aug 12, 2026

Copy link
Copy Markdown
Member

What changes were proposed in this pull request?

Three fixes to developer and release tooling:

  • dev/create-release/release-build.sh: removes the dead lsof band-aid block, and fixes a typo in the usage help (reposiotry to repository).
  • .github/PULL_REQUEST_TEMPLATE: updates the ConfigEntry.scala path to its current location under common/utils.

Why are the changes needed?

The lsof block assigns $LSOF and probes for the binary, but $LSOF is never used anywhere in the script or in anything it sources or that calls it, so the SPARK-22377 workaround has had no effect since the Jenkins machines it targeted were retired. The PR template points contributors at core/src/main/scala/org/apache/spark/internal/config/ConfigEntry.scala, which no longer exists; the file now lives under common/utils.

Does this PR introduce any user-facing change?

No. Developer and release tooling only.

How was this patch tested?

No functional change. release-build.sh still parses (bash -n), $LSOF was confirmed to have no reference outside the removed block (including in release-util.sh and do-release.sh), and the corrected ConfigEntry.scala path exists on master while the old one does not.

Was this patch authored or co-authored using generative AI tooling?

Generated-by: Claude Code (Opus 4.8)

@uros-b uros-b left a comment

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Waiting for CI

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant