Skip to content

fix: forward signals to the teardown command - #630

Merged
gustavohenke merged 1 commit into
open-cli-tools:mainfrom
fzakaria:teardown-signal
Oct 25, 2026
Merged

gustavohenke merged 1 commit into
open-cli-tools:mainfrom
fzakaria:teardown-signal

Conversation

@fzakaria

Copy link
Copy Markdown
Contributor

The signal handlers are removed when the commands finish, which is when teardown starts. A SIGINT, SIGTERM or SIGHUP during teardown then killed concurrently and left the teardown command running.

Teardown now handles those signals itself: it sends them to the running teardown command and starts no further ones.

The signal handlers are removed when the commands finish, which is
when teardown starts. A SIGINT, SIGTERM or SIGHUP during teardown then
killed concurrently and left the teardown command running.

Teardown now handles those signals itself: it sends them to the
running teardown command and starts no further ones.
@fzakaria

Copy link
Copy Markdown
Contributor Author

Context:
I found this with Rewind VM, a deterministic VM that records a run and reruns it under different thread schedules; I have been stress testing the tool.

@coveralls

Copy link
Copy Markdown

Coverage Status

coverage: 98.78% (-0.05%) from 98.83% — fzakaria:teardown-signal into open-cli-tools:main

@gustavohenke gustavohenke left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks!

@gustavohenke
gustavohenke merged commit 2a80d44 into open-cli-tools:main Oct 25, 2026
21 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants