~ chicken-core (chicken-5) ff1cf21c790127839c610f802ff078b8097cc2b4

commit ff1cf21c790127839c610f802ff078b8097cc2b4
Author:     felix <felix@call-with-current-continuation.org>
AuthorDate: Mon Jan 8 22:03:31 2018 +0100
Commit:     felix <felix@call-with-current-continuation.org>
CommitDate: Mon Jan 8 22:03:31 2018 +0100

    Disable finalizer-test for toplevel literals
    
    This test fails on a regular basis for not directly related reasons,
    depending on toplevel allocation patterns and GC-frequency. Since
    the situation is relatively obscure (finailzer on code literal in evaluated
    code only) and since faiilures are frequently triggered by changes
    that do not directly refer to this, I have temporarily disabled the
    test until we settle on a desired semantics or a complete and final
    fix.

diff --git a/tests/test-finalizers.scm b/tests/test-finalizers.scm
index 23e568f7..3b083a0d 100644
--- a/tests/test-finalizers.scm
+++ b/tests/test-finalizers.scm
@@ -70,6 +70,10 @@ a fix that unfortunately disables finalizers in the interpreter
 ;; Finalizers on constants are ignored in compiled mode (because
 ;; they're never GCed).  Reported by "Pluijzer".
 
+#| this doesn't always work in csi, for some unknown reason,
+   depending on unrelated factors (command-line options,
+   memory usage patterns, etc.)
+                                                
 (set! n 0)
 (define bar "constant string")
 (set-finalizer! bar bump)
@@ -79,3 +83,4 @@ a fix that unfortunately disables finalizers in the interpreter
 (cond-expand
   (compiling (assert (= 0 n)))
   (else (assert (= 1 n))))
+|#