BuildUtils::sh() runs each build command in its own process group, so SIGKILL on the wrapper leaves that group running. A lock recovered from the dead wrapper then lets a second build into the same checkout, and cancel_build's retention is undone by the same recovery: it keeps the lock when workers survive, and the next build reads a dead owner and takes it. build_lock_stale_owner.t covers a wrapper and nothing below it. The name reads wider than the check: the holder it kills has no build worker, so the worker case was never measured. Its comment says so now. A new check is the reviewer's case. A worker runs in its own process group, a wrapper takes the build lock and records it, the wrapper alone is killed, and a second build must stay blocked. Then the worker exits and the same build must take the lock: without that half, a lock that recovers nothing would pass. The handshake is two one-byte reads on separate pipes, each bounded. One read of two bytes made it a timing test, which passed on this host and killed the wrapper before it held the lock. The vendored XCAT::NFSLock gains attach, detach and live_workers, which these checks drive. Signed-off-by: Daniel Hilst <392820+dhilst@users.noreply.github.com>
xCAT
xCAT is a toolkit for deployment and administration of clusters of all sizes.
The xCAT sunset was only a quick eclipse
Dear xCAT Community,
The xCAT sunset has changed course. VersatusHPC has been invited to join the xCAT Consortium, and future development will move toward direct upstream contributions coordinated with the Consortium and its existing member companies.
That matters most for Enterprise Linux 10 (EL10). EL10 support is coming to xCAT, restoring a future operating-system path for sites that still rely on xCAT. This is an important change from the previous sunset guidance, where the lack of an EL10 path was one of the strongest reasons to move away from xCAT.
The xCAT Consortium continues to recommend Confluent as the long-term successor to xCAT, and that remains the Consortium position. Users planning new cluster-management deployments should evaluate Confluent and its xCAT comparison documentation.
At the same time, xCAT is no longer sunsetted. The Consortium and participating companies will continue updating xCAT while there is community and user demand for it.
In summary:
- xCAT development is continuing upstream through the Consortium and participating companies.
- Enterprise Linux 10 support is coming.
- Confluent remains the Consortium-recommended successor and migration path.
- xCAT updates will continue while there is community and user demand.
We want to thank the xCAT Consortium and community for keeping this project moving. The sun went behind the moon for a moment, but xCAT is still here.
For more information on Confluent and how to get started, please visit the Confluent: Project Page, Documentation or Confluent vs xCAT comparison.
With thanks,
The xCAT Consortium
Documentation
xCAT Documentation is hosted on Read The Docs: https://xcat-docs.readthedocs.io
Status
| xCAT Version | Build Status |
|---|---|
| Latest (master branch) | |
| Stable (latest release) |
Looking for older versions?
Open Source License
xCAT is made available under the EPL license: https://opensource.org/licenses/eclipse-1.0.php
Developers
Want to help? Check out the developers guide!