Hello.
I have recently implemented to new features.
1. If library testing fails due to FFI, for example
absence of foreign library, we now automatically
recognize these failures and mark them in the reports
by "ffi" hint. This helps analyzing diff between
two quicklisp releases we tested: if new failures
are caused by FFI they are most likely due to
testing on different machine where certain foreign
libraries are absent, rather than a regression in CL code.
2. When I analyze test results I can enter notes
about failures I have studied into a notes database.
When reports are printed, notes are printed in the table
cell for each matching result. This allows to share
the information with other consumers of the reports
and simplifies my work, as I should not keep this information
in head.
The notes DB currently filled like this:
(defparameter *note-db*
(fill-notes `((lib-world "quicklisp 2013-08-13"
(libname :com.informatimago
(failure-p t "author informed"))
(libname :asdf-dependency-grovel
(system-name "asdf-dependency-grovel"
(failure-p t "needs ASDF 3")))
(libname :xcvb
(failure-p t
(lisp ("acl-9.0a-win-x86" "ccl-1.8-f95-win-x64" "ccl-1.8-f95-win-x86" "sbcl-1.0.57.0.debian-linux-x64")
"needs ASDF 3")))
(libname :exscribe
(failure-p t
"needs ASDF 3"))
(libname (:periods :cambl)
(failure-p t
,(lp-ticket "1229050")))))))
Here each note matches to a set of results.
For example we specify that on "quicklisp 2013-08-13"
all failures of exscribeare because to exscribe
requires ASDf 3. This specification applies results
from all OSes and lisp implementations.
Some reports with notes:
http://common-lisp.net/project/cl-test-grid/ql/quicklisp-2013-08-13-diff2.html
http://common-lisp.net/project/cl-test-grid/library/exscribe.html
Best regards,
- Anton