test-check-shbang: work around check-code not wanting hardcoded paths
authorAugie Fackler <augie@google.com>
Tue, 12 Jul 2016 15:32:24 -0400
changeset 29515 bd18c2178fac
parent 29514 280528245ecf
child 29516 e5c61e745cd7
test-check-shbang: work around check-code not wanting hardcoded paths I'm about to fix a bug in check-code that a # anywhere on a line treated the rest of the line as a comment, even if it was meaningful. This test is the one place we explicitly *do* want hardcoded paths referenced, but we can work around that by specifying bin as a regular expression.
tests/test-check-shbang.t
--- a/tests/test-check-shbang.t	Tue Jul 12 11:20:30 2016 -0400
+++ b/tests/test-check-shbang.t	Tue Jul 12 15:32:24 2016 -0400
@@ -5,10 +5,10 @@
 
 look for python scripts that do not use /usr/bin/env
 
-  $ hg files 'set:grep(r"^#!.*?python") and not grep(r"^#!/usr/bin/env python")'
+  $ hg files 'set:grep(r"^#!.*?python") and not grep(r"^#!/usr/bi{1}n/env python")'
   [1]
 
 look for shell scripts that do not use /bin/sh
 
-  $ hg files 'set:grep(r"^#!.*/bin/sh") and not grep(r"^#!/bin/sh")'
+  $ hg files 'set:grep(r"^#!.*/bi{1}n/sh") and not grep(r"^#!/bi{1}n/sh")'
   [1]