The GitHub Actions job "Required Checks" on 
texera.git/ci/6523-cu-worker-cluster-join-smoke has succeeded.
Run started by GitHub user mengw15 (triggered by mengw15).

Head commit for run:
52e89d221ac66e352ae7352d77fc42e82c31eb34 / mengw15 
<[email protected]>
ci: smoke-test the computing-unit cluster (master boot + worker join)

Nothing in CI verified that an amber worker node can join a running
cluster: the standalone computing-unit-master boot check formed only a
1-node self-seeded cluster, and the packaged computing-unit-worker launcher
was 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 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.

Replace the standalone master boot step with a single cluster check.
smoke-cluster.sh boots a computing-unit-master (non-cluster mode self-seeds
pekko://Amber@localhost:2552) and a no-arg computing-unit-worker (joins
:2552, skipping 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 signal, not a crash-scan (contrast
#6332). Because it boots and waits for the master first, it still catches a
#6204-class linkage crash on master startup (reported as "master exited
before listening"), so the separate smoke-boot master step it supersedes is
redundant. It fails fast if either JVM dies and reaps both on exit. Wired
into 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/29870792130

With regards,
GitHub Actions via GitBox

Reply via email to