See if we can isolate valgrind issues on travis

Building individual tests should  make issues become more clear

.travis.yml

@@ -111,7 +111,7 @@ script:
  - if [ $VALGRIND != "0" ]; then TEST_TYPE="--valgrind="$PREFIXTEST"" ; fi
  #- if [ "$UNIT_TESTS" != "0" ]; then $PREFIXTEST $PREFIXPATH/boost_afio_test -s $UNIT_TESTS; fi
 # Not sure if we can pass the valgrind flags into the unit tests, but so far it hasnt crashed :)
- - b2 libs/afio/test $DEBUGBUILD link=shared toolset=$CC$GCCVER $TEST_TYPE --test-all $FLAGS ;
+ - b2 libs/afio/test $DEBUGBUILD link=shared toolset=$CC$GCCVER $TEST_TYPE --test-each $FLAGS ;
 
 #if we want to use the built in bjam test runner we can get test output this way
 # - cat bin.v2/libs/afio/test/main.test/*/*/main.output #may need to specify path better on valgrind tests