Skip to content

Add improved sigint handling for cancellation#33

Closed
midnightveil wants to merge 1 commit intoseL4:masterfrom
au-ts:julia/sigint
Closed

Add improved sigint handling for cancellation#33
midnightveil wants to merge 1 commit intoseL4:masterfrom
au-ts:julia/sigint

Conversation

@midnightveil
Copy link
Copy Markdown
Contributor

Actually propagate upwards the SIGINT as the cause of the failure.

Actually propagate upwards the SIGINT as the cause
of the failure.

Signed-off-by: Julia Vassiliki <julia.vassiliki@unsw.edu.au>
@midnightveil
Copy link
Copy Markdown
Contributor Author

Requesting a review from @wom-bat.

Comment thread scripts/enqueue
# https://github.com/openssh/openssh-portable/blob/V_10_0_P1/mux.c#L2057-L2059
# (However, sometimes it will instead forward through status 130 from the process
# which received SIGINT on the other end of the SSH session. Sometimes...)
if [ "${ret}" == "255" ]; then
Copy link
Copy Markdown
Contributor Author

@midnightveil midnightveil Apr 23, 2026

Choose a reason for hiding this comment

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

OK, so this doesn't seem to be reliable.

Our console scripts in /tftpboot will return -1 if various subcommands fail, which results in sys.exit(-1) which terminates python with code 255.

This seems like it would be a bad idea.

I'm going to go with Indan's suggestion: seL4/ci-actions#461 (comment)

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.

1 participant