From fb2b96be043fdba3ab70f256cad339b848b8c30f Mon Sep 17 00:00:00 2001
From: Curtis McEnroe <june@causal.agency>
Date: Thu, 10 Jan 2019 20:19:51 -0500
Subject: Remove cash/tests

---
 bin/cash/tests/execution/killed2.0 | 10 ----------
 1 file changed, 10 deletions(-)
 delete mode 100644 bin/cash/tests/execution/killed2.0

(limited to 'bin/cash/tests/execution/killed2.0')

diff --git a/bin/cash/tests/execution/killed2.0 b/bin/cash/tests/execution/killed2.0
deleted file mode 100644
index f9a67876..00000000
--- a/bin/cash/tests/execution/killed2.0
+++ /dev/null
@@ -1,10 +0,0 @@
-# $FreeBSD: releng/12.0/bin/sh/tests/execution/killed2.0 218105 2011-01-30 22:57:52Z jilles $
-# Most shells print a message when a foreground job is killed by a signal.
-# POSIX allows this, provided the message is sent to stderr, not stdout.
-# Some trickery is needed to capture the message as redirecting stderr of
-# the command itself does not affect it. The colon command ensures that
-# the subshell forks for ${SH}.
-
-exec 3>&1
-r=`(${SH} -c 'kill $$'; :) 2>&1 >&3`
-[ -n "$r" ]
-- 
cgit 1.4.1