Skip to content
Snippets Groups Projects
  1. Sep 12, 2016
  2. Sep 02, 2016
  3. Aug 27, 2016
  4. Aug 16, 2016
    • Robert Goldman's avatar
      Fix treatment of CCL:PROCESS-RESET. · ff34993c
      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.
      ff34993c
  5. Aug 15, 2016
  6. Jul 25, 2016
    • Robert Goldman's avatar
      Redefined *FATAL-CONDITIONS* per 1605650. · 9fd59ed8
      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.
      9fd59ed8
  7. Jul 24, 2016
    • Robert Goldman's avatar
      Modify test-running scripts to catch SERIOUS-CONDITIONs. · 1ef5c959
      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.
      1ef5c959
  8. Mar 21, 2016
  9. Mar 20, 2016
    • Robert Goldman's avatar
      Allow ASDF directory to be found by environment variable. · 32eef692
      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.
      32eef692
  10. Sep 14, 2015
  11. Aug 30, 2015
  12. Jul 08, 2015
  13. Jun 08, 2015
  14. May 26, 2015
  15. May 08, 2015
  16. Mar 12, 2015
  17. Oct 31, 2014
  18. Sep 11, 2014
  19. Jul 10, 2014
    • Robert P. Goldman's avatar
      Drop caching from LOCATE-SYSTEM. · 00256418
      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.
      00256418
  20. May 19, 2014
  21. Mar 18, 2014
  22. Mar 17, 2014
  23. Feb 28, 2014
  24. Feb 26, 2014
  25. Feb 21, 2014
  26. Feb 19, 2014
  27. Feb 10, 2014
  28. Dec 20, 2013
  29. Dec 11, 2013
  30. Nov 20, 2013
  31. Nov 18, 2013
  32. Nov 16, 2013
  33. Nov 12, 2013
Loading