|
From: Nicholas N. <n.n...@gm...> - 2009-07-20 03:47:29
|
On Sat, Jul 18, 2009 at 4:09 AM, Rich Coe<Ric...@me...> wrote:
> Nightly build on macbook ( Darwin 9.6.0 i386 )
> Started at 2009-07-17 07:20:25 CDT
> Ended at 2009-07-17 07:38:26 CDT
> Results unchanged from 24 hours ago
>
> Checking out valgrind source tree ... done
> Configuring valgrind ... done
> Building valgrind ... done
> Running regression tests ... failed
>
> Regression test results follow
>
> == 319 tests, 16 stderr failures, 2 stdout failures, 0 post failures ==
> memcheck/tests/lsframe1 (stderr)
> memcheck/tests/lsframe2 (stderr)
> memcheck/tests/origin5-bz2 (stderr)
> memcheck/tests/stack_changes (stdout)
> memcheck/tests/stack_changes (stderr)
> memcheck/tests/varinfo3 (stderr)
> memcheck/tests/varinfo5 (stderr)
> memcheck/tests/vcpu_fnfns (stdout)
> memcheck/tests/xml1 (stderr)
> massif/tests/culling1 (stderr)
> massif/tests/culling2 (stderr)
> massif/tests/deep-B (stderr)
> massif/tests/deep-C (stderr)
> massif/tests/peak2 (stderr)
> massif/tests/realloc (stderr)
> none/tests/async-sigs (stderr)
> none/tests/faultstatus (stderr)
> none/tests/pth_blockedsig (stderr)
Ah, excellent. Thanks for setting this up. Would it be possible to
update the macbook.sendmail script to include the diffs for the failed
tests? Without that, it's very difficult for someone else to fix any
problems. From nightly/README:
- The third [argument] is the name of the file containing all the diffs from
failing tests. Depending on the test results you get, you could
inline this file into the email body, or attach it, or compress and
attach it, or even omit it. The right choice depends on how many
failures you typically get -- if you get few failures, inlining the
results make them easier to read; if you get many failures,
compressing might be a good idea to minimise the size of the emails.
Nick
|