[Swan-dev] [Swan-commit] Changes to ref refs/heads/master

Andrew Cagney andrew.cagney at gmail.com
Tue May 26 00:48:24 EEST 2015

The additional checks are:

            check_console_log_for '^CORE FOUND'
            check_console_log_for SEGFAULT
            check_console_log_for GPFAULT
            check_pluto_log_for 'ASSERTION FAILED'
            check_pluto_log_for 'EXPECTATION FAILED'
            # this blats CORE into all the .diff files; better than nothing
            for i in OUTPUT/core* ; do
                if [ -f "$i" ] ; then
                    echo "# CORE: $i"
                    echo "$i " >> OUTPUT/${host}.console.tmp

they were lifted from "grep_4_known_errors" in swantest.
pluto-testlist-scan.sh also does similar tests.

Are any of these expected?


(I had a test get an assertion-failed during exit so it didn't show up in
the console log's diff)

On 25 May 2015 at 17:25, Paul Wouters <paul at nohats.ca> wrote:

> On Mon, 25 May 2015, Andrew Cagney wrote:
>  commit b6b982ab03c5e15c87f4ce0ccedae7a687ccc403
>> Author: Andrew Cagney <cagney at gnu.org>
>> Date:   Mon May 25 14:44:58 2015 -0400
>>    testing: check console and pluto logs for error messages
>>    And put them into the .diff file so failures can be spotted.
> I'm not sure I like this. There are a few tests that specifically
> look for certain errors by grepping their /tmp/pluto.log files.
> I'm afraid this will lead to false positives and more writing of
> sanitizers.
> Paul
> _______________________________________________
> Swan-dev mailing list
> Swan-dev at lists.libreswan.org
> https://lists.libreswan.org/mailman/listinfo/swan-dev
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.libreswan.org/pipermail/swan-dev/attachments/20150525/a539f8e3/attachment.html>

More information about the Swan-dev mailing list