From: Andy Wingo Date: Fri, 1 Feb 2019 16:18:50 +0000 (+0100) Subject: Fix crypt-on-glibc test error X-Git-Tag: v2.9.2~2^2~19 X-Git-Url: http://review.tizen.org/git/?a=commitdiff_plain;h=27ffbfb0235de466016ea5a6421508f6548971b6;p=platform%2Fupstream%2Fguile.git Fix crypt-on-glibc test error * test-suite/tests/posix.test ("crypt"): Allow for the given salt being valid. Thanks to Jonathan Brielmaier for the report and debugging! --- diff --git a/test-suite/tests/posix.test b/test-suite/tests/posix.test index d3170c743..87a0c704a 100644 --- a/test-suite/tests/posix.test +++ b/test-suite/tests/posix.test @@ -262,10 +262,17 @@ (pass-if "basic usage" (string? (crypt "pass" "abcdefg"))) - (pass-if-exception "glibc EINVAL" exception:system-error - ;; This used to deadlock while trying to throw to 'system-error'. - ;; This test uses the special interpretation of the salt that glibc - ;; does; specifically, we pass a syntactically invalid salt here. - (if (string-contains %host-type "-gnu") - (crypt "pass" "$X$abc") ;EINVAL - (throw 'unresolved)))) + (pass-if "crypt invalid salt on glibc" + (begin + (unless (string-contains %host-type "-gnu") + (throw 'unresolved)) + (catch 'system-error + (lambda () + ;; This used to deadlock on glibc while trying to throw to + ;; 'system-error'. This test uses the special + ;; interpretation of the salt that glibc does; + ;; specifically, we pass a salt that's probably + ;; syntactically invalid here. Note, whether it's invalid + ;; or not is system-defined, so it's possible it just works. + (string? (crypt "pass" "$X$abc"))) + (lambda _ #t)))))