summaryrefslogtreecommitdiff
path: root/test/test-execute/exec-capabilityboundingset-simple.service
diff options
context:
space:
mode:
authorFilipe Brandenburger <filbranden@google.com>2015-11-08 10:19:45 -0800
committerFilipe Brandenburger <filbranden@google.com>2015-11-10 07:58:29 -0800
commitcdaf5070480c09a7650589fa02b4d59c0af00112 (patch)
treeb72102d42e15a30ac0c3ff4c88cad7d00aaea4af /test/test-execute/exec-capabilityboundingset-simple.service
parent8f84882240b776dab07c4ee5aaf2dd1acd8cb45b (diff)
test-execute: Fix systemd escaping and shell issues
In most cases, systemd requires escaping $ (for systemd variable substitution) and % (for specifiers) by doubling them. This was somewhat of an issue in tests like exec-environment*.service where systemd was doing the substitutions and we were not really checking that those were available in the actual environment of the command. Fix that. Expressions such as `exit $(test ...)` are incorrect. They only work because $(test ...) will produce no output, so the command will become a bare "exit" which will exit with the status of the latest executed command which turns out to be the test... The direct approach is simply calling "test" as the last command, for which the shell will propagate the exit status. One situation where this was breaking tests was on `exit $(test ...) && $(test ...) && $(test ...)` where the second and third tests were not really executing, since the first command is actually `exit` so && was doing nothing there. Fixed it by just using `test ... && test ... && test ...` as it was initially intended. Pass -x to all shell executions for them to produce useful debugging output to stderr. Consequently, removed most of the explicit `echo`s that are no longer needed. Mark all units as Type=oneshot explicitly. Also made sure all shell variables are properly quoted. v2: Added an explicit LC_ALL=C to ionice invocations since some locales (such as French) will add a space before the colon in the output. Tested by running `sudo ./test-execute` and confirming all tests enabled on my system (essentially all of them except for the s390 one) passed. Tweaked the variables or options or expected values and confirmed the tests do indeed fail when the values are not exactly the expected ones. v2: Also tested with `LANG=fr_FR.UTF-8 sudo ./test-execute` to confirm it still works in a different locale.
Diffstat (limited to 'test/test-execute/exec-capabilityboundingset-simple.service')
-rw-r--r--test/test-execute/exec-capabilityboundingset-simple.service3
1 files changed, 2 insertions, 1 deletions
diff --git a/test/test-execute/exec-capabilityboundingset-simple.service b/test/test-execute/exec-capabilityboundingset-simple.service
index b9037a0ddf..bf1a7f575a 100644
--- a/test/test-execute/exec-capabilityboundingset-simple.service
+++ b/test/test-execute/exec-capabilityboundingset-simple.service
@@ -2,5 +2,6 @@
Description=Test for CapabilityBoundingSet
[Service]
-ExecStart=/bin/sh -c 'c=$(capsh --print | grep "Bounding set " | cut -f 2 -d "="); echo $c; exit $(test $c = "cap_fowner,cap_kill")'
+ExecStart=/bin/sh -x -c 'c=$$(capsh --print | grep "Bounding set "); test "$$c" = "Bounding set =cap_fowner,cap_kill"'
+Type=oneshot
CapabilityBoundingSet=CAP_FOWNER CAP_KILL