Fix valgrind tests.

[robertnishihara]

This comments out a test that has been consistently failing.

[AmplabJenkins]

Merged build finished. Test PASSed.

[AmplabJenkins]

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Ray-PRB/1976/
Test PASSed.

[AmplabJenkins]

Merged build finished. Test PASSed.

[AmplabJenkins]

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Ray-PRB/1983/
Test PASSed.

[AmplabJenkins]

Merged build finished. Test PASSed.

[AmplabJenkins]

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Ray-PRB/1986/
Test PASSed.

[AmplabJenkins]

Merged build finished. Test PASSed.

[AmplabJenkins]

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Ray-PRB/1987/
Test PASSed.

[AmplabJenkins]

Merged build finished. Test FAILed.

[AmplabJenkins]

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Ray-PRB/1982/
Test FAILed.

[AmplabJenkins]

Merged build finished. Test PASSed.

[AmplabJenkins]

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Ray-PRB/1988/
Test PASSed.

[robertnishihara]

This fixes most of the valgrind errors. There's two remaining problems.

Problem 1: The valgrind tests are still detecting an error.

==9401== 34 bytes in 1 blocks are possibly lost in loss record 4 of 8
==9401==    at 0x4C2B0E0: operator new(unsigned long) (in /usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so)
==9401==    by 0x510F248: std::string::_Rep::_S_create(unsigned long, unsigned long, std::allocator<char> const&) (in /usr/lib/x86_64-linux-gnu/libstdc++.so.6.0.19)
==9401==    by 0x5110970: char* std::string::_S_construct<char const*>(char const*, char const*, std::allocator<char> const&, std::forward_iterator_tag) (in /usr/lib/x86_64-linux-gnu/libstdc++.so.6.0.19)
==9401==    by 0x5110D87: std::basic_string<char, std::char_traits<char>, std::allocator<char> >::basic_string(char const*, std::allocator<char> const&) (in /usr/lib/x86_64-linux-gnu/libstdc++.so.6.0.19)
==9401==    by 0x439C2C: get_redis_shards(redisContext*, std::vector<std::string, std::allocator<std::string> >&, std::vector<int, std::allocator<int> >&) (redis.cc:154)
==9401==    by 0x405B90: object_reconstruction_test() (local_scheduler_tests.cc:190)
==9401==    by 0x409164: local_scheduler_tests() (local_scheduler_tests.cc:678)
==9401==    by 0x409B0C: greatest_run_suite(void (*)(), char const*) (local_scheduler_tests.cc:686)
==9401==    by 0x40A7BC: main (local_scheduler_tests.cc:691)

Problem 2: The problem is that Problem 1 isn't causing the valgrind tests to fail...

[robertnishihara]

Ok, it looks like problem 1 may be related to valgrind having trouble with std::string, and problem 2 may be related to the fact that the test script forks and valgrind errors in child processes may not cause the build to fail or something like that.