Re: [Sbcl-devel] Freeze for 1.0.27

[Richard M K. <kr...@pr...>]

Paul Khuong writes:
> On 28-Mar-09, at 1:52 PM, Richard M Kreuter wrote:
> > Please consider SBCL CVS frozen pending a 1.0.27 release on April  
> > 2...
>
> I'm testing on OS X/x86[-64]. Without threads, the tests pass as  
> expected. With threads, I don't think there's any regression compared  
> to 1.0.26 (results in the postscript). I quickly ran the tests on  
> linux/x86-64; nothing unexpected.

Does anybody think the unexpected failures below ought to hold up the
release today?

--
Richard

> On x86-64:
> 
> Finished running tests.
> Status:
>   Expected failure:    float.pure.lisp / (SCALE-FLOAT-OVERFLOW BUG-372)
>   Expected failure:    float.pure.lisp / (ADDITION-OVERFLOW BUG-372)
>   Expected failure:    threads.pure.lisp / WITHOUT-INTERRUPTS 
> +CONDITION-WAIT
>   Expected failure:    callback.impure.lisp / UNDERFLOW-DETECTION
> ;; The following are ok when run separately
>   Invalid exit status: clos-add-remove-method.impure.lisp
>   Invalid exit status: clos-cache.impure.lisp
>   Invalid exit status: clos-interrupts.impure.lisp
>   Invalid exit status: compare-and-swap.impure.lisp
>   Invalid exit status: debug.impure.lisp
>   Expected failure:    external-format.impure.lisp / (CHARACTER-DECODE- 
> LARGE
>                                                       FORCE-END-OF-FILE)
> ;; So are these
>   Invalid exit status: gc.impure.lisp
>   Invalid exit status: hash.impure.lisp
>   Expected failure:    packages.impure.lisp / USE-PACKAGE-CONFLICT-SET
>   Expected failure:    packages.impure.lisp / IMPORT-SINGLE-CONFLICT
> ;; signals and timer fail; threads hangs (for a couple minutes at  
> least) in the locking tests.
>   Invalid exit status: signals.impure.lisp
>   Invalid exit status: threads.impure.lisp
>   Invalid exit status: timer.impure.lisp
> test failed, expected 104 return code, got 1
> 
> On x86:
> 
> Finished running tests.
> Status:
>   Expected failure:    float.pure.lisp / (SCALE-FLOAT-OVERFLOW BUG-372)
>   Expected failure:    float.pure.lisp / (ADDITION-OVERFLOW BUG-372)
>   Expected failure:    threads.pure.lisp / WITHOUT-INTERRUPTS 
> +CONDITION-WAIT
> ;; The following are ok when run separately
>   Invalid exit status: clos-add-remove-method.impure.lisp
>   Invalid exit status: clos-cache.impure.lisp
>   Invalid exit status: clos-interrupts.impure.lisp
>   Invalid exit status: compare-and-swap.impure.lisp
>   Invalid exit status: debug.impure.lisp
>   Expected failure:    external-format.impure.lisp / (CHARACTER-DECODE- 
> LARGE
>                                                       FORCE-END-OF-FILE)
> ;; Same here
>   Invalid exit status: gc.impure.lisp
>   Invalid exit status: hash.impure.lisp
>   Expected failure:    packages.impure.lisp / USE-PACKAGE-CONFLICT-SET
>   Expected failure:    packages.impure.lisp / IMPORT-SINGLE-CONFLICT
> ;; signals and timer also die; threads gets farther, and hangs for at  
> least a couple minutes in (:CONDITION-VARIABLE :WAIT-MULTIPLE)
>   Invalid exit status: signals.impure.lisp
>   Invalid exit status: threads.impure.lisp
>   Invalid exit status: timer.impure.lisp
> test failed, expected 104 return code, got 1
> 
> 
> -----------------------------------------------------------------------------
> -
> _______________________________________________
> Sbcl-devel mailing list
> Sbc...@li...
> https://lists.sourceforge.net/lists/listinfo/sbcl-devel
>