[asdf-devel] Test results: one failure on CCL
Running test-all-noupgrade, CCL fails for me on test-encodings.script: Testing: test-encodings.script + /Users/rpg/ccl/dx86cl64 --no-init --quiet --eval '(load "test-encodings.script")' Test TEST-ENCODING-EXPLICIT-U8: should be UTF-8 ; Registering #<SYSTEM "test-encoding-explicit-u8"> TEST ABORTED: Component "asdf-encodings" not found Looks like this might be a simple bundling problem? Mac OS X, CCL 1.8 cheers, r
Yes, to run this test, one needs asdf-encodings installed next to asdf. I've added a check to disable the rest of the test when asdf-encodings is missing. I've also made many, many improvements to the runtime part of ASDF, so it provides things like backtraces, image dump and resume hooks, controlled conditions, etc. It all started as having to dig again deep into the pathname compatibility, then the run-program compatibility, and I finally decided to just move all the remaining general-purpose parts of XCVB-driver into a layer of ASDF called ASDF/DRIVER. And I'm putting it to good use in the test support and in bin/bump-version which was re-written from an unholy mix of shell and perl to Common Lisp. I'm homesteading the package nickname :D for asdf/driver. PS: You may or may not like the magic macro (d:asdf-debug). In other news, after a coding marathon fighting package surgery issues, the ASDF looks like it's working and mostly stable, and I'm again going to look into trying it with cl-test-grid. —♯ƒ • François-René ÐVB Rideau •Reflection&Cybernethics• http://fare.tunes.org The truth of a proposition has nothing to do with its credibility. And vice versa. — Robert Heinlein, "Time Enough For Love"
On 1/13/13 Jan 13 -9:46 PM, Faré wrote:
PS: You may or may not like the magic macro (d:asdf-debug).
Is that what's being used in run-tests.sh now when I give the -d option? If so, it may not be working on ACL. When I give the -d option now, I get dropped into the REPL after the test, seemingly whether it succeeds or not. I get dropped in after every test when doing ./run-tests -d allegro cheers, r
Is that what's being used in run-tests.sh now when I give the -d option? If so, it may not be working on ACL. When I give the -d option now, I get dropped into the REPL after the test, seemingly whether it succeeds or not. I get dropped in after every test when doing ./run-tests -d allegro
Oh, I had been conflating two things: whether or not you want a debug prompt rather than quit when a script has a failure, and whether or not you want to quit when a given test script ran successfully. It's now two flags. Sorry. PS: the image.lisp support file in ASDF is now ready for people to look at. See how the *command-line-argument* are used in bin/bump-version. —♯ƒ • François-René ÐVB Rideau •Reflection&Cybernethics• http://fare.tunes.org Women can form a friendship with a man very well; but to preserve it — to that end a slight physical antipathy must probably help. — Nietzsche, HAH
On 1/14/13 Jan 14 -1:19 PM, Faré wrote:
Is that what's being used in run-tests.sh now when I give the -d option? If so, it may not be working on ACL. When I give the -d option now, I get dropped into the REPL after the test, seemingly whether it succeeds or not. I get dropped in after every test when doing ./run-tests -d allegro
Oh, I had been conflating two things: whether or not you want a debug prompt rather than quit when a script has a failure, and whether or not you want to quit when a given test script ran successfully. It's now two flags. Sorry.
I think I was conflating also. But the behavior I saw was that ACL would not exit after the tests, even when the tests succeeded. Anyway, after my latest git pull, things are looking better. Cheers, r
participants (2)
-
Faré -
Robert Goldman