- Sep 12, 2016
-
-
Elias Pipping authored
-
- Sep 02, 2016
-
-
Francois-Rene Rideau authored
-
- Aug 27, 2016
-
-
Francois-Rene Rideau authored
This makes it easier to search for the backtrace when debugging.
-
- Aug 16, 2016
-
-
Robert Goldman authored
This condition, incorrectly made a subclass of SERIOUS-CONDITION, was breaking some tests, because a normal termination using (EXIT-LISP 0) could cause this to be signaled.
-
- Aug 15, 2016
-
-
Robert Goldman authored
Previously, if the tests failed because of unexpected warnings, the WITH-ASDF-CONDITIONS macro would swallow the warning you needed to fix.
-
- Jul 25, 2016
-
-
Robert Goldman authored
See https://bugs.launchpad.net/asdf/+bug/1605650 According to the spec, SERIOUS-CONDITIONs are "All conditions serious enough to require interactive intervention if not handled should inherit from the type serious-condition." This is almost exactly the definition of *FATAL-CONDITIONS*, so I substituted SERIOUS-CONDITION for ERROR here. Added exceptions to the set of *FATAL-CONDITIONS* in order to fix test condition handling for CCL. The exceptions permit us to have a class of conditions (e.g., SERIOUS-CONDITION) that has a subclass that is not a FATAL-CONDITION, but that does not have an obvious more specific alternative. The specific example that caused me to add this: On shutdown, CCL signals CCL:PROCESS-RESET, a subclass of SERIOUS-CONDITION. So recent test harness modifications to handle SERIOUS-CONDITIONs caused the test scripts to mistakenly think there were failures because of calls to EXIT-LISP.
-
- Jul 24, 2016
-
-
Robert Goldman authored
There are some serious conditions (e.g., STORAGE-CONDITION) that are not ERRORs. Previously, our test scripts only caught ERRORs, meaning that if a lisp implementation encountered a non-ERROR SERIOUS-CONDITION in the course of running the tests, odd behavior could result. E.g., running in ECL we would drop into the debugger instead of exiting with a non-zero exit status.
-
- Mar 21, 2016
-
-
Robert Goldman authored
Incorrectly was using code that relied on not-yet-loaded ASDF functions.
-
- Mar 20, 2016
-
-
Robert Goldman authored
Trying to test ASDF on Windows, running the makefile in cygwin was ending up causing troubles where the cygwin pathnames would get into lisp, where they would be useless. So we allow the tester to specify the location of ASDF with an environment variable instead.
-
- Sep 14, 2015
-
-
Francois-Rene Rideau authored
-
- Aug 30, 2015
-
-
Francois-Rene Rideau authored
Also, tweak default parameters in source-registry after debugging on Allegro 10. Add two debugging functions in test/script-support.
-
- Jul 08, 2015
-
-
Francois-Rene Rideau authored
-
- Jun 08, 2015
-
-
Francois-Rene Rideau authored
-
- May 26, 2015
-
-
Francois-Rene Rideau authored
Fix the use of the new run-command protocol.
-
- May 08, 2015
-
-
Francois-Rene Rideau authored
-
- Mar 12, 2015
-
-
Francois-Rene Rideau authored
Based on a contribution by Christian Shafmeister.
-
- Oct 31, 2014
-
-
Francois-Rene Rideau authored
-
- Sep 11, 2014
-
-
Francois-Rene Rideau authored
* README updated, converted to markdown * Some documentation updates * bin/install-asdf-as-module renamed to tools/install-asdf.lisp and improved. * Update test scripts to be work even when the initial getcwd isn't in test/
-
- Jul 10, 2014
-
-
Robert P. Goldman authored
Caching negative results here causes pervasive problems, and removing negative caching only would be very messy, so we are removing caching here altogether. This required some modification to the test code, which was directly using LOCATE-SYSTEM, and LOCATE-SYSTEM cannot be safely invoked unless the ASDF-CACHE has been established.
-
- May 19, 2014
-
-
Francois-Rene Rideau authored
fixing bugs, moving asdf-builder into tools and splitting it into minimal script itself and Lisp source.
-
- Mar 18, 2014
-
-
Francois-Rene Rideau authored
-
- Mar 17, 2014
-
-
Francois-Rene Rideau authored
-
Robert P. Goldman authored
-
- Feb 28, 2014
-
-
Robert P. Goldman authored
-
Francois-Rene Rideau authored
(improved comments, whitespace, remove doubly exported symbols).
-
- Feb 26, 2014
-
-
Robert P. Goldman authored
-
- Feb 21, 2014
-
-
Francois-Rene Rideau authored
(improved comments, whitespace, remove doubly exported symbols).
-
Robert P. Goldman authored
-
- Feb 19, 2014
-
-
Robert P. Goldman authored
-
- Feb 10, 2014
-
-
Robert P. Goldman authored
Test for DIRECTORY-FILES returning only files; text for SUBDIRECTORIES returning only subdirectories. According to Fare, DIRECTORY-FILES should *not* return subdirectories, but it does on several implementations. See https://bugs.launchpad.net/asdf/+bug/1276748
-
- Dec 20, 2013
-
-
Francois-Rene Rideau authored
Why is this somehow not affecting other implementations???
-
Francois-Rene Rideau authored
-
- Dec 11, 2013
-
-
Francois-Rene Rideau authored
Tweak some test output.
-
- Nov 20, 2013
-
-
Francois-Rene Rideau authored
CMUCL: hush some warnings
-
- Nov 18, 2013
-
-
Francois-Rene Rideau authored
-
Francois-Rene Rideau authored
-
- Nov 16, 2013
-
-
Francois-Rene Rideau authored
-
Francois-Rene Rideau authored
-
- Nov 12, 2013
-
-
Francois-Rene Rideau authored
Everyone should be using a recent 2.7.0 (in ANSI mode) from master for ASDF.
-
Francois-Rene Rideau authored
-