After you reversed the argument order it looks like now it's only
being run *with* tree
http://buildbot.wireshark.org/trunk/builders/Clang-Code-Analysis/builds/1875/steps/valgrind-wireshark/logs/stdio
Maybe it's worth running that step of the bot with "-2" so that both
argument strings are non-null (that would also improve our coverage
slightly for reassembly issues etc). I'm still not sure why it would
be skipping the null string though, as it certainly doesn't when
running it by hand.
Evan
On Wed, Apr 17, 2013 at 1:17 PM, Gerald Combs <gerald@xxxxxxxxxxxxx> wrote:
> On 4/13/13 11:55 AM, Evan Huus wrote:
>> I was poking through buildbot output when I noticed that the new
>> valgrind steps don't ever appear to be running with tree for some
>> reason.
>>
>> For example:
>> http://buildbot.wireshark.org/trunk/builders/Clang-Code-Analysis/builds/1869/steps/valgrind-wireshark/logs/stdio
>>
>> The header lists:
>>> with args: "" "-T"
>> which is the default and suggests that each file should be run with
>> and without tree. However if you look at the output for individual
>> files, the output is:
>>> : () OK
>> instead of the expected
>>> : () (-T) OK
>>
>> The script works fine locally, so I'm not sure what's going on. A
>> subtle difference between shell versions perhaps?
>
> The script works fine when run by hand on the build machine as well. I'm
> not sure why "-T" is being skipped.
> ___________________________________________________________________________
> Sent via: Wireshark-dev mailing list <wireshark-dev@xxxxxxxxxxxxx>
> Archives: http://www.wireshark.org/lists/wireshark-dev
> Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev
> mailto:wireshark-dev-request@xxxxxxxxxxxxx?subject=unsubscribe
