diff options
| author | Pjotr <wrk@bosa.lan> | 2026-11-08 15:51:15 +0000 |
|---|---|---|
| committer | Pjotr <wrk@bosa.lan> | 2026-11-08 15:51:15 +0000 |
| commit | cfe873f6d60820f258a154e9c89c519687cb23c6 (patch) | |
| tree | 942ff2652d8aeb8a129fd5f0bdf44af9224a36a5 /test/python/test_groups.py | |
| parent | b5b425a850b2f892ae931f6298c336b1d5ce9e0c (diff) | |
| download | genenetwork4-cfe873f6d60820f258a154e9c89c519687cb23c6.tar.gz | |
docs: a restart that reports success and changes nothing
Deploying today, `nohup env … ./target/release/genenetwork4 &` left an intermediate process's pid in `$!`, so `kill $(cat /tmp/gn4.pid)` stopped that and the server kept answering. The replacement died with `AddrInUse` -- in its own log, where nobody was looking -- and `/version` still reported the previous commit. Everything looked fine: the port answered, the smoke tests passed, the notes were the old ones. The checklist now says what actually decides it: read `/proc` for the process running the release binary (there is no `ps` on this box), and believe `/version`'s `git` over a successful-looking start -- a `git` older than the build just made is this mistake, not a build problem. Start the replacement only once `:3000` has stopped answering, and write the resolved pid into the pid file.
Diffstat (limited to 'test/python/test_groups.py')
0 files changed, 0 insertions, 0 deletions
