merge core-8-6-branch

1 files changed, 8 insertions, 8 deletions

diff --git a/tests/resolver.test b/tests/resolver.test
index dc38ff0..9bb4c08 100644
--- a/tests/resolver.test
+++ b/tests/resolver.test
@@ -187,7 +187,7 @@ test resolver-2.1 {compiled var resolver: Bug #3383616} -setup {
     # During the compilation the compiled var resolver, the resolve-specific
     # var info is allocated, during the execution of the body, the variable is
     # fetched and cached.
-    x;
+    x
     # During later calls, the cached variable is reused.
     x
     # When the proc is freed, the resolver-specific resolver var info is
@@ -223,14 +223,14 @@ test resolver-3.1a {
 	proc y {} { return yy }
 	namespace eval ::ns {
 	    proc x1 {} { z }
-	}	
+	}
     }
 } -constraints testinterpresolver -body {
-    
+
     set r [i0 eval {namespace eval ::ctx1 {
 	::ns::x1
     }}]
-    
+
     return $r
 } -cleanup {
     testinterpresolver down i0
@@ -251,7 +251,7 @@ test resolver-3.1b {
 	proc Y {} { return YY }
 	namespace eval ::ns {
 	    proc x2 {} { z }
-	}	
+	}
     }
 } -constraints testinterpresolver -body {
 
@@ -274,7 +274,7 @@ test resolver-3.1c {
     interp command resolver,
     resolve literal "z" in proc "x1" in context "ctx1",
     resolve literal "z" in proc "x2" in context "ctx2"
-    
+
     Test, whether the shared cmd literal created by the first byte-code
     compilation interacts with the second one.
 } -setup {
@@ -288,7 +288,7 @@ test resolver-3.1c {
 	namespace eval ::ns {
 	    proc x1 {} { z }
 	    proc x2 {} { z }
-	}	
+	}
     }
 
 } -constraints testinterpresolver -body {
@@ -304,7 +304,7 @@ test resolver-3.1c {
     set r3 [i0 eval {namespace eval ::ctx1 {
 	::ns::x1
     }}]
-    
+
     return [list $r1 $r2 $r3]
 } -cleanup {
     testinterpresolver down i0