The GitHub Actions job "Required Checks" on texera.git/ci/6523-cu-worker-cluster-join-smoke has failed. Run started by GitHub user mengw15 (triggered by mengw15).
Head commit for run: 7d0a8fa2a08c0fddc117cf3a9ff7114f7effe277 / mengw15 <[email protected]> ci: add a computing-unit-worker cluster-join smoke test in amber-integration Nothing in CI verifies that an amber worker node can join a running cluster: the computing-unit-master boot forms only a 1-node self-seeded cluster, and the packaged computing-unit-worker launcher (bin/computing-unit-worker) is never started at all. A regression in the worker's join path -- its Pekko remoting/serialization, seed-node config, or startActorWorker itself -- would break the deployed worker while build, unit tests, and the existing boot checks all stay green. The worker can't reuse smoke-boot.sh: it runs no HTTP server and binds a random Pekko remote port, so there is no fixed port to probe, and booted standalone it just retries its seed and stays up (so "did not crash" proves nothing). Its real health signal is cluster membership. Add smoke-cluster.sh: it boots a computing-unit-master (non-cluster mode self-seeds pekko://Amber@localhost:2552) and a no-arg computing-unit-worker (joins :2552, and skips the getNodeIpAddress/checkip.amazonaws.com lookup that only fires with --serverAddr, so no external network), then asserts the worker JOINS by waiting for ClusterListener's "2 nodes in the cluster" readiness line on the master -- a deliberate readiness signal, not a crash-scan (contrast amber-integration after the texera-web boot, reusing the same dist; ubuntu-only. test_smoke_cluster.sh drives the harness end-to-end with fake launchers, asserting the specific verdict message for each outcome so a deleted fast-fail branch turns the test red. Closes #6523. Report URL: https://github.com/apache/texera/actions/runs/29867044082 With regards, GitHub Actions via GitBox
