I suspect kvmresults.py is doing what you want. It's default
behaviour is to ignore the previously generated OUTPUT/*.console.txt
and OUTPUT/*.console.diff files and instead perform the analysis using
the raw input files (the reference .console.txt, .pluto.log, and
.console.verbose.txt).
The options (see kvmresults.py --help):
--quick Use the previously generated '.console.txt' and
'.console.diff' files
--update Update the '.console.txt' and '.console.diff' files
can be used to change this behaviour (don't combine a running
testsuite with kvmresults.py --update).
However, I tend to use 'kvmresults.py --print diffs ...' (make
kvm-diffs) and even go as far as:
./testing/utils/kvmresults.py --print diffs
testing/pluto/basic-pluto-01 | patch -p1
Andrew
On Tue, 14 Aug 2018 at 17:09, D. Hugh Redelmeier <h...@mimosa.com> wrote:
>
> I sometimes make mistakes that cause a simple problem that shows up in a
> lot of these (you've seend that today).
>
> I would like to be able to edit the OUTPUT/*.verbose.txt files and the
> OUTPUT/*.pluto.log files and have the results analyzed again.
> I don't know how to do that now. I've spent a very few minutes
> looking a the scripts.
>
> testing/utils/sanitizer.sh seems to be current. I think I got it to
> work with the right parameters (but it is a little awkward to use from
> the command line).
>
> I suspect testing/utils/sanitize.sh is obsolete and perhaps should be
> ditched.
>
> Is testing/utils/re-sanitize.sh still current?
>
> I frequently use testing/utils/kvmresults.py testing/pluto/ for a
> summary. I'd love a "re-analyze" that was as convenient to use.
> _______________________________________________
> Swan-dev mailing list
> Swan-dev@lists.libreswan.org
> https://lists.libreswan.org/mailman/listinfo/swan-dev
_______________________________________________
Swan-dev mailing list
Swan-dev@lists.libreswan.org
https://lists.libreswan.org/mailman/listinfo/swan-dev
