[Swan-dev] sanitize.sh vs re-sanitize.sh (vs swantest.sh)

[Andrew Cagney]

Just fyi,

I've done some merging into re-sanitize.sh:

- it leaves empty diffs around, somewhat annoying but useful - another way
to verify things are working
- exits non-zero if it thinks the test failed
- checks for more failure conditions

after more testing we can look at it replacing sanitize.sh

On 20 March 2015 at 13:56, Andrew Cagney <andrew.cagney at gmail.com> wrote:

> (I was hoping re-sanitize.sh was a script to update the reference output,
> little did I know)
>
> It seems we've ended up with several different ways of checking a test
> result:
>
> sanitize.sh
>  - run from swantest
>  - leaves empty diffs when a test passes :-(
>  - doesn't check for crashes and assert failures :-(
>
> re-sanitize.sh
>  - run from pluto-testlist-scan.sh (nice script)
>  - doesn't leave empty diffs :-)
>  - doesn't check for crashes and assert failures :-(
>
> swantest
>  - checks for for crashes and assert failures
>
> Does anyone see a problem with me cherry-picking the best bits:
>
> - does the sanitize
> - doesn't leave empty diffs
> - does check for core files and assertion failures (those messages can be
> put into the diff)
> - and exits with 1 if the test doesn't appear to have passed
>
> perhaps called postmortem.sh
>
> Andrew
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.libreswan.org/pipermail/swan-dev/attachments/20150525/5d952c2a/attachment.html>