andygrove opened a new pull request, #2538: URL: https://github.com/apache/datafusion-ballista/pull/2538
# Which issue does this PR close? None; follows up on the 55.0.0 RC1 release-verification vote discussion. # Rationale for this change The release verification instructions do not mention the shell's open-file limit. During the 55.0.0 RC1 vote, Marko reported that raising the limit to 2048 allowed verification to pass on another machine. This is a reported working value, not a measured minimum or confirmation that every reported test failure has the same cause. # What changes are included in this PR? Add an open-file limit check before the verification script invocation on macOS and Linux. The Bash/Zsh example raises only a lower soft limit to 2048, retains higher or unlimited limits, and leaves the hard limit unchanged. Explain the hard-limit caveat and why verification must run from the same shell to inherit the setting. Validation: Bash and Zsh syntax checks and bounded disposable-process checks for lower/equal/higher soft limits, unchanged hard limits, child-process inheritance, and insufficient-hard-limit handling; mocked unlimited-limit branch; Prettier 2.7.1 on the edited section; `git diff --check`. Checks ran on macOS; Linux runtime and full release-verification tests were not run for this documentation-only change. # Are there any user-facing changes? Release verifiers now have an explicit limit setup step before running tests. Only `dev/release/README.md` changes. -- 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] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
