Skip to content
Snippets Groups Projects
  1. Jul 20, 2017
    • Robert Goldman's avatar
      Allow user to disable backtraces. · b0f468c0
      Robert Goldman authored
      In some cases the backtraces aren't useful, and obscure more important
      information.  Now the user can disable them with lisp variable or
      environment variable.
      
      (cherry picked from commit 99422ff9238f72fbad557e8d716bee9df2e84d7c)
      b0f468c0
    • Francois-Rene Rideau's avatar
      Separate forcing from plan · 897a142b
      Francois-Rene Rideau authored
      Move forcing into its own file.
      Include forcing, not plan, among session slots.
      Share a toplevel forcing for all performable plans.
      Have REQUIRE use load-system, not require-system,
      so as not to conflict with session forcing options.
      Don't call with-asdf-session outside the test scripts themselves.
      Cleanup a few scripts accordingly, and beyond.
      897a142b
    • Francois-Rene Rideau's avatar
      Move node visit information from plan to session · a9c22442
      Francois-Rene Rideau authored
      Significantly refactor plan internals.
      
      Move visited-actions, visiting-action-set, visiting-action-list,
      total-action-count, planned-action-count, planned-output-action-count
      from plan to session (remove the plan- prefix to accessors).
      
      Move sysdef-error from component to session.
      
      Remove plan as a parameter of action-valid-p (made simple defun)
      and while-visiting-action (both moved to action), but also
      map-direct-dependencies, reduce-direct-dependencies, direct-dependencies.
      
      Rename *default-plan-class* to *plan-class*,
      plan-record-dependency to record-dependency,
      plan-action-status to action-status
      plan-forced (accessor) to forced, plan-forced-not (accessor) to forced-not.
      
      Introduce define-op, and visit a suitable action while loading an asd file.
      Accumulate inner operate dependencies in a slot definition-dependencies of
      a registered system or a newly registered undefined-system.
      
      Introduce reset-session or reset-session-visited in various tests,
      so operations aren't considered as layered atop each other, but
      as restarting from a fresh planning session.
      
      Use with-asdf-session in required-components, make-plan.
      
      Stop using node-for, use cons directly, now that operations are safe.
      
      Export format-action from action.
      
      Move some conditions and generic functions around and reorder dependencies.
      a9c22442
    • Francois-Rene Rideau's avatar
      Introduce an *asdf-session* that may contain more than a cache. · f98aaa6b
      Francois-Rene Rideau authored
      Replace with-asdf-cache with with-asdf-session.
      Introduce *asdf-session-class* to hold the class of the session.
      Introduce caching-cache, currently the only session class,
      that only contains a cache, for now.
      f98aaa6b
    • Francois-Rene Rideau's avatar
      Rename asdf/cache to asdf/session · 49dbfc0c
      Francois-Rene Rideau authored
      49dbfc0c
  2. Feb 17, 2017
    • Francois-Rene Rideau's avatar
      Fix images for ASDF-dependent systems on ECL · bae381cb
      Francois-Rene Rideau authored
      Recent ECLs have libasdf.a instead of asdf.a.
      
      Not all bundle-op is a basic-compile-op (e.g. concatenate-source-op).
      Declaring otherwise was causing asdf/defsystem to appear as a compiled
      dependency, causing incorrect double inclusion of symbols in the link
      when asdf was explicitly depended on.
      
      Make sure to include only one of uiop or asdf as the fallback support file,
      and only when neither uiop nor asdf is explicitly depended on.
      
      Improve test-program.script for ECL.
      
      This fixes https://bugs.launchpad.net/bugs/1660547
      bae381cb
  3. Dec 07, 2016
    • Francois-Rene Rideau's avatar
      Support for notification that some functions are deprecated. · c1652787
      Francois-Rene Rideau authored
      Deprecation goes through the following phases:
      style-warning, warning, cerror, functionality removed.
      Automatically upgrade the deprecation phase at every minor version change
      (not every release).
      
      Include minimal testing of the deprecation functionality.
      Add deprecation TODO items.
      
      Deprecation will start with 3.2.
      c1652787
  4. Sep 30, 2016
  5. Sep 25, 2016
    • Francois-Rene Rideau's avatar
      script-support: reinstate call-with-asdf-cache · 338af8ca
      Francois-Rene Rideau authored
      When testing upgrade from old versions of ASDF, we must accommodate the need
      that some old versions have for us to wrap the calls in c-w-a-c, and the need
      for yet older versions for us not to call c-w-a-c, that didn't exist back then.
      338af8ca
  6. Sep 16, 2016
  7. Sep 13, 2016
    • Robert Goldman's avatar
      Simplify TOUCH-FILE. · 08d59a6d
      Robert Goldman authored
      There was a very complex conditional in the middle controlling how it
      was implemented.  I simplified the conditions to make it easier to
      understand how it works.
      I also modified it so that if you tell TOUCH-FILE to use the cache, and
      the cache hasn't been initialized, it will raise an error.
      08d59a6d
  8. Sep 12, 2016
  9. Sep 02, 2016
  10. Aug 27, 2016
  11. 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
  12. Aug 15, 2016
  13. 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
  14. 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
  15. Mar 21, 2016
  16. 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
  17. Sep 14, 2015
  18. Aug 30, 2015
  19. Jul 08, 2015
  20. Jun 08, 2015
  21. May 26, 2015
  22. May 08, 2015
  23. Mar 12, 2015
  24. Oct 31, 2014
  25. Sep 11, 2014
  26. 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
  27. May 19, 2014
  28. Mar 18, 2014
  29. Mar 17, 2014
  30. Feb 28, 2014
  31. Feb 26, 2014
  32. Feb 21, 2014
Loading