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 <[email protected]> Archives: http://www.wireshark.org/lists/wireshark-dev Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev mailto:[email protected]?subject=unsubscribe
