renu-123-pixel commented on issue #30854: URL: https://github.com/apache/beam/issues/30854#issuecomment-3797024472
Proposed fix: explicitly configure Java in CI by setting JAVA_HOME. The observed flakiness occurs during Java discovery, where Beam internally relies on a subprocess call equivalent to which java. On GitHub Actions runners, this lookup intermittently hangs, causing the test to block until the global timeout is reached. By explicitly installing Java and exporting JAVA_HOME (and updating PATH) in the workflow, we avoid relying on dynamic PATH resolution entirely. This allows Beam to resolve Java directly without invoking which java, eliminating the hanging subprocess scenario. This approach aligns with standard CI best practices and is the preferred long-term solution, as it stabilizes the environment rather than masking the failure or disabling tests. -- 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]
