[asdf-devel] Just pulled an update and now CCL fails the tests

[Robert Goldman]

I am now getting 8 test failures:

Ran 42 tests:
  34 passing and 8 failing
failing test(s):  test-bundle.script test-compile-file-failure.script
test-concatenate-source.script test-force.script
test-nested-components.script test-package.script
test-touch-system-2.script test-xach-update-bug.script

Testing: test-bundle.script
+ /Users/rpg/ccl/dx86cl64 --no-init --quiet --batch --eval '(load
"test-bundle.script")'
; Registering #<SYSTEM "test-bundle-1">
; Registering #<SYSTEM "test-bundle-2">
TEST-BUNDLE
  ASDF-TEST::BUNDLE-1 =>
#P"/Users/rpg/lisp/asdf/build/fasls/ccl-1.8-f95-macosx-x64/asdf/test/test-bundle-1\\.system.dx64fsl"
  ASDF-TEST::BUNDLE-2 =>
#P"/Users/rpg/lisp/asdf/build/fasls/ccl-1.8-f95-macosx-x64/asdf/test/test-bundle-2\\.system.dx64fsl"
TEST ABORTED: Failed assertion: (PROBE-FILE BUNDLE-1)

Testing: test-compile-file-failure.script
+ /Users/rpg/ccl/dx86cl64 --no-init --quiet --batch --eval '(load
"test-compile-file-failure.script")'
; Warning: Warning.
; While executing: #<Anonymous Function #x30200099F98F>, in process
listener(1).
TEST ABORTED: Failed assertion: (HANDLER-CASE (LET
((*COMPILE-FILE-FAILURE-BEHAVIOUR* :ERROR)) (LOAD-SYSTEM
'TEST-COMPILE-FILE-FAILURE :FORCE T) NIL) (COMPILE-ERROR NIL T))

Testing: test-concatenate-source.script
+ /Users/rpg/ccl/dx86cl64 --no-init --quiet --batch --eval '(load
"test-concatenate-source.script")'
; Registering #<SYSTEM "test-concatenate-source">
; Loading system definition from
/Users/rpg/lisp/asdf/test/file3-only.asd into #<Package "ASDF-0">
; Registering #<SYSTEM "file3-only">
TEST ABORTED: These two expressions fail comparison with EQUAL:
(PRINC-TO-STRING (INPUT-FILES MCSO SYS)) evaluates to "NIL"
 (PRINC-TO-STRING (LOOP :FOR N :IN '(3 1 2) :COLLECT (SUBPATHNAME
*TEST-DIRECTORY* (FORMAT NIL "file~D.lisp" N)))) evaluates to
"(/Users/rpg/lisp/asdf/test/file3.lisp
/Users/rpg/lisp/asdf/test/file1.lisp /Users/rpg/lisp/asdf/test/file2.lisp)"


Testing: test-force.script
+ /Users/rpg/ccl/dx86cl64 --no-init --quiet --batch --eval '(load
"test-force.script")'
TEST ABORTED: Failed assertion: (>= (FILE-WRITE-DATE FILE1) FILE1-DATE)

Testing: test-nested-components.script
+ /Users/rpg/ccl/dx86cl64 --no-init --quiet --batch --eval '(load
"test-nested-components.script")'
; Registering #<SYSTEM "test-nested-components-a">
TEST ABORTED: Invalid pathname #P"test-nested-components-1.asd":
Expected an absolute pathname

Testing: test-package.script
+ /Users/rpg/ccl/dx86cl64 --no-init --quiet --batch --eval '(load
"test-package.script")'
; Registering #<SYSTEM "test-package">
TEST ABORTED: Invalid relative pathname #P"test-package/" for component
("test-package")


Testing: test-touch-system-2.script
+ /Users/rpg/ccl/dx86cl64 --no-init --quiet --batch --eval '(load
"test-touch-system-2.script")'
; Registering #<SYSTEM "test1">
TEST ABORTED: Invalid pathname #P"test1.asd": Expected an absolute pathname


Now, change registry so foo is found from xach-foo-2/
load foo yet again. It should see the pathname has changed and load it anew
TEST ABORTED: No package named "SECOND-VERSION"


cheers,
r