<div dir="ltr"><div><div><div><div>Just fyi,<br><br></div>I've done some merging into re-sanitize.sh:<br><br></div>- it leaves empty diffs around, somewhat annoying but useful - another way to verify things are working<br></div>- exits non-zero if it thinks the test failed<br></div>- checks for more failure conditions<br><div><div><div><br>after more testing we can look at it replacing sanitize.sh<br></div></div></div></div><div class="gmail_extra"><br><div class="gmail_quote">On 20 March 2015 at 13:56, Andrew Cagney <span dir="ltr"><<a href="mailto:andrew.cagney@gmail.com" target="_blank">andrew.cagney@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div>(I was hoping re-sanitize.sh was a script to update the reference output, little did I know)<br><br></div><div>It seems we've ended up with several different ways of checking a test result:<br><br></div><div>sanitize.sh<br> - run from swantest<br> - leaves empty diffs when a test passes :-(<br> - doesn't check for crashes and assert failures :-(<br><br></div><div>re-sanitize.sh<br> - run from pluto-testlist-scan.sh (nice script)<br> - doesn't leave empty diffs :-)<br> - doesn't check for crashes and assert failures :-(<br><br></div><div>swantest<br> - checks for for crashes and assert failures<br><br></div><div>Does anyone see a problem with me cherry-picking the best bits:<br><br></div><div>- does the sanitize<br></div><div>- doesn't leave empty diffs<br></div><div>- does check for core files and assertion failures (those messages can be put into the diff)<br></div><div>- and exits with 1 if the test doesn't appear to have passed<br><br></div><div>perhaps called postmortem.sh<span class="HOEnZb"><font color="#888888"><br></font></span></div><span class="HOEnZb"><font color="#888888"><div><br></div><div>Andrew<br></div></font></span></div>
</blockquote></div><br></div>