1. 25 Jul, 2016 1 commit
    • 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
  2. 24 Jul, 2016 1 commit
    • 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
  3. 21 Mar, 2016 1 commit
  4. 20 Mar, 2016 1 commit
    • 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
  5. 14 Sep, 2015 1 commit
  6. 30 Aug, 2015 1 commit
  7. 08 Jul, 2015 1 commit
  8. 08 Jun, 2015 1 commit
  9. 26 May, 2015 1 commit
  10. 08 May, 2015 1 commit
  11. 12 Mar, 2015 1 commit
  12. 31 Oct, 2014 1 commit
  13. 11 Sep, 2014 1 commit
  14. 10 Jul, 2014 1 commit
    • 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
  15. 19 May, 2014 1 commit
  16. 18 Mar, 2014 1 commit
  17. 17 Mar, 2014 2 commits
  18. 28 Feb, 2014 2 commits
  19. 26 Feb, 2014 1 commit
  20. 21 Feb, 2014 2 commits
  21. 19 Feb, 2014 1 commit
  22. 10 Feb, 2014 1 commit
  23. 20 Dec, 2013 2 commits
  24. 11 Dec, 2013 1 commit
  25. 20 Nov, 2013 1 commit
  26. 18 Nov, 2013 2 commits
  27. 16 Nov, 2013 2 commits
  28. 12 Nov, 2013 2 commits
  29. 06 Nov, 2013 1 commit
  30. 24 Oct, 2013 1 commit
  31. 20 Oct, 2013 2 commits
  32. 19 Oct, 2013 1 commit