1. 17 Apr, 2014 1 commit
  2. 05 Jan, 2014 1 commit
  3. 09 Nov, 2013 1 commit
  4. 19 Jun, 2013 2 commits
  5. 12 Jun, 2013 1 commit
  6. 14 Feb, 2013 1 commit
  7. 02 Dec, 2012 2 commits
  8. 16 Nov, 2012 1 commit
  9. 31 Jul, 2011 2 commits
  10. 26 Jul, 2011 1 commit
  11. 22 Jul, 2011 1 commit
  12. 14 Jul, 2011 2 commits
  13. 17 Mar, 2010 1 commit
  14. 14 Mar, 2010 1 commit
  15. 27 Feb, 2010 1 commit
    • mevenson@1c010e3e-69d0-11dd-93a8-456734b0d56f's avatar
      ANSI test database can now contain multiple test results per version. · 6cb21dae
      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.
      6cb21dae