Re: [Valgrind-developers] Regression tests

[Florian K. <br...@ac...>]

On 10/03/2011 01:30 PM, Julian Seward wrote:
> 
> disable4 didn't run to completion on 32 bit targets.  It should
> do now (post r12086).
> 

Thanks. It also passes on my old s390x box.

>>
>> =================================================
>> ./valgrind-new/helgrind/tests/hg05_race2.stderr.diff
>> =================================================
>> --- hg05_race2.stderr.exp	2011-10-02 03:16:05.865487001 +0100
>> +++ hg05_race2.stderr.out	2011-10-02 03:24:46.251181409 +0100
>> @@ -1,4 +1,6 @@
>>
>> +warning: evaluate_Dwarf3_Expr: unhandled DW_OP_ 0x........
>> +warning: evaluate_Dwarf3_Expr: unhandled DW_OP_ 0x........
> 
> Oh, right.  So this is the Dwarf3 var info reader complaining that it
> doesn't understand something created by the gcc 4.6.x in F15.
> 

Yes. What is curious is that the test passed on 09/30 and failed on
10/01? Assuming the compiler and libraries did not change on that system
and svn has no changes in that area, it should pass.

>> What would be really good is to modify the nightly scripts so they show
>> what valgrind revision is actually tested and also some detail about the
>> environment. See the z900 nightly build for an example.
> 
> Yes, I noticed the s390x runs have much better info at the top.
> What needs to happen to make all the runs have the same info?
> Is it something that can be done by editing the scripts in 
> trunk/nightly/ ?
> 

Integration into bin/nightly shouldn't be a problem.
Currently, this is done in nightly/conf/z900.sendmail
Would these queries work on Darwin:

glibc_version="`/lib/libc.so.* | head -1`"
uname_stuff="`uname -mrs`"
vendor_stuff="`cat /etc/issue.net | head -1`"

  Florian