- 05 Jan, 2014 1 commit
-
-
Latest test results "Java_HotSpot(TM)_64-Bit_Server_VM-Oracle_Corporation-1.7.0_45-b18" on "x86_64-Mac_OS_X-10.9.1".
-
- 09 Nov, 2013 1 commit
-
-
Added recent trunk ansi-compiled, ansi-interpreter results. A few (~10) new regressions that need to be hunted down.
-
- 19 Jun, 2013 2 commits
-
-
- 12 Jun, 2013 1 commit
-
-
LOAD.18 the only additional one over abcl-1.1.1.
-
- 14 Feb, 2013 1 commit
-
-
1.1.1: Update the ANSI tests failures.
-
- 02 Dec, 2012 2 commits
-
-
-
13 out of 21707 total tests failed (PSETF.37 CALL-NEXT-METHOD.ERROR.1 CALL-NEXT-METHOD.ERROR.2 INVOKE-DEBUGGER.1 MAKE-CONDITION.3 MAKE-CONDITION.4 SXHASH.8 MAP.48 TYPE-OF.1 TYPE-OF.4 MAKE-CONCATENATED-STREAM.30 PRINT.RANDOM-STATE.1 PPRINT-LOGICAL-BLOCK.17)
-
- 16 Nov, 2012 2 commits
-
-
-
Now output the removed artifacts to *STANDARD-OUTPUT*.
-
- 11 Oct, 2012 1 commit
-
-
- 04 May, 2012 3 commits
-
-
-
A bit of a circular dance here to be able to use the ANSI-TESTS via ASDF. In order to define functions like ABCL.TEST.ANSI:DO-TESTS-MATCHING we need to have loaded the REGRESSION-TEST package included with the ANSI-TESTS, so we can no longer use the value of the ABCL.TEST.ANSI:*ANSI-TESTS-DIRECTORY*. We now do this via a relative pathname of the form '../ansi-tests/' to the location of 'abcl.asd' file, whereas our api previously suggested that one could set the contents of ABCL.TEST.ANSI:*ANSI-TESTS-DIRECTORY* to an arbitrary pathname. This fixes the location of the ANSI-TESTS on the filesystem to be a sibling directory named 'ansi-tests' to the truename of the directory containing 'abcl.asd'. I tried to add some sort of :before method to either the ASDF:LOAD-OP or the ASDF:COMPILE-OP for the ANSI-RT definition, but assuming that the source named in an system definition exists locally seems too baked into ASDF2 to be cleanly intercepted.
-
An ASDF load of ANSI-INTERPRETED now loads the interpreted tests into memory via an :around specialization. Changes in ABCL.TEST.ANSI (aka ANSI-TESTS): DO-TESTS-MATCHING implemented (cribbed from ABCL-TEST-LISP). Refactored DEFPACKAGE forms out of ABCL-ANSI-TESTS code, creating abcl-ansi.lisp to hold all other forms. Import symbols from REGRESSION-TEST where it makes sense (list could probably be larger; why not just use the package?)
-
- 31 Jul, 2011 2 commits
-
-
- 26 Jul, 2011 1 commit
-
-
We make #\Uxxxx a synonym of character code but not the cannonical character name, using instead the unicode character at that point.
-
- 22 Jul, 2011 1 commit
-
-
- 14 Jul, 2011 2 commits
-
-
Export ANSI-TESTS:FULL-REPORT as it seems useful enough.
-
Added test results between 0.25.0 and 0.26.0 on Solaris.
-
- 25 May, 2011 1 commit
-
-
Refactor code into separate CLEAN-TEST and VERIFY-ANSI-TEST which facilitates interactive use of the package.
-
- 14 Apr, 2011 1 commit
-
-
- 03 Oct, 2010 1 commit
-
-
the patch by David Kirkman, kudos for the hard work. I merely added fixes for the other hashtables according to David's patch, and fixed the ansi error parsing, reported again by David. MASSIVE thanks for the patch!
-
- 24 Sep, 2010 1 commit
-
-
- 12 Aug, 2010 1 commit
-
-
- 21 Jul, 2010 1 commit
-
-
- 17 Jul, 2010 1 commit
-
-
Thanks to Matt Sedon.
-
- 15 Apr, 2010 1 commit
-
-
- 17 Mar, 2010 1 commit
-
-
- 14 Mar, 2010 1 commit
-
-
- 27 Feb, 2010 2 commits
-
-
We change the syntax of the ANSI test results database to allow the specification of a unique identifier plus other optional identifying information by allowing keyword/value pairs. The keyword :ID specifies the identifier, which should be a symbol. Other arbitrary keywords are allowed which specify additional information to be associated with the symbol specified by :ID in the *ID* hashtable. Not every test failure entry needs to specify this information. In case of duplicates, the last entry wins. Suggested other keywords are :JVM to specify the Java virtual machine, and :UNAME to specify the operating system/hardware combination in a GNU autoconf-like string. See the comments at the beginning of 'parse-ansi-errors.lisp' for more details. The utility has been packaged in ABCL.ANSI.TEST, showing up in the ANSI-COMPILED and ANSI-INTERPRETED ASDF systems loadable from 'abcl.asd'. A database of failures has been included in 'ansi-test-failures'. It is intended that other developers entrich this database with their own test results.
-
-
- 06 Jan, 2010 1 commit
-
-
Use ASDF to invoke all tests from Ant. Add working test for Ant version at least 1.7.1. Changed structure of 'build.xml' slightly to emphasize 'help' target by placing it first. Include cl-bench tests in 'abcl.test.lisp' Ant target. Added 'help.test' target for help invoking tests. abcl.asd now works for invoking tests. ASDF systems with empty component specifications must be invoked with the :force t option to execute correctly.
-
- 29 Jan, 2009 1 commit
-
-
Further incremental work on ABCL-TEST-LISP (aka the internal ABCL tests) necessitated by the fact that both it and the ANSI tests use the REGRESSION-TEST framework which doesn't work well in the same Lisp instances. Trying to repackage this correctly, but it needs more work.
-
- 28 Jan, 2009 1 commit
-
-
- 27 Jan, 2009 1 commit
-
-
Optimized 'build.xml' run time for typical (repeated) usage scenarios: o downloading of 'junit.jar' based on presence on filesystem. o rebuilding of 'abcl.jar' based on explicit check via Ant Removed automatic execution of ABCL-TESTS based on load. Ant 'abcl.test' target not working in all situations. Needs further debugging. Workaround: use the Lisp-based ASDF test entry point for now. ANSI-TESTS-COMPILED ANSI-TESTS-INTERPRETED need a sibling directory containing the GCL ANSI tests from <svn://common-lisp.net/project/ansi-test/svn/trunk/ansi-tests>. They complain semi-intellibly if not found.
-
- 04 Jan, 2009 1 commit
-
-
In order for these tests to work, you will need a sibling directory of 'abcl' called 'ansi-tests' which contains the GCL ANSI-TEST suite from <svn://common-lisp.net/project/ansi-test/svn/trunk/ansi-tests>.
-
- 03 Jan, 2009 1 commit
-
-
First stab at a collected test infrastructure for ABCL using ASDF packaging. Currently, only the GCL ANSI-TEST suite really works: create a sibling directory to the 'abcl' top-level directory called 'ansi-tests' to get them to run automagically.
-