mirror of
https://github.com/fish-shell/fish-shell
synced 2024-11-14 08:58:01 +00:00
a447a9aeff
This is a partial fix for issue #3737. It only addresses the SIGHUP aspect of the problem. Fixing SIGTERM is TBD.
37 lines
1.1 KiB
Text
37 lines
1.1 KiB
Text
# vim: set filetype=expect:
|
|
#
|
|
# Test handling of the `exit` command.
|
|
set pid [spawn $fish]
|
|
expect_prompt
|
|
|
|
# Verify that if we attempt to exit with a job in the background we get warned
|
|
# about that job and are told to type `exit` a second time.
|
|
send "sleep 111 &\r"
|
|
expect_prompt
|
|
send "exit\r"
|
|
expect "There are still jobs active"
|
|
expect "A second attempt to exit will terminate them."
|
|
expect_prompt
|
|
|
|
# Running anything other than `exit` should result in the same warning with
|
|
# the shell still running.
|
|
send "sleep 113 &\r"
|
|
expect_prompt
|
|
send "exit\r"
|
|
expect "There are still jobs active"
|
|
expect "A second attempt to exit will terminate them."
|
|
expect_prompt
|
|
|
|
# Verify that asking to exit a second time does so.
|
|
send "exit\r"
|
|
catch {expect default exp_continue} output
|
|
wait
|
|
|
|
# Verify all child processes have been killed. We don't use `-p $pid` because
|
|
# if the shell has a bug the child processes might have been reparented to pid
|
|
# 1 rather than killed.
|
|
set status [catch {exec pgrep -l -f "sleep 11"} output]
|
|
if {$status == 0} {
|
|
puts stderr "Commands spawned by the shell still running after `exit`"
|
|
puts stderr $output
|
|
}
|