travis: switch to other Boost PPA and test 1.53 and 1.55
stupidity...
travis: even more stupid...
travis: different repos for different versions

:-/
travis: enable APT caching and make tests more verbose
tests: advec: using different matcher
tests: stupid namespaces...
tests: on MPI run do not execute GTest::run() on all ranks

it is sufficient to run the tests only on the master node
tests: using another matcher

maybe this helps...
tests: mpi-fix for GTest

each MPI task should return the same test result; otherwise it might
happen that the test passed on rank 0 but one of the minor ranks finally
wins the race on returning from main
Merge branch 'development' into feature/travis-different-boost

Conflicts:
	.travis.yml
tests: further tweaking MPI advec test

errors of all ranks are checked and in case any rank fails, all will
fail;
Merge pull request #65 from torbjoernk/feature/travis-different-boost

travis: switch to other Boost PPA and test 1.53 and 1.55
Merge branch 'development' into release/v0.2.0

this is a backmerge of PR #65

* development:
  tests: further tweaking MPI advec test
  tests: mpi-fix for GTest
  tests: using another matcher
  tests: on MPI run do not execute GTest::run() on all ranks
  tests: stupid namespaces...
  tests: advec: using different matcher
  travis: enable APT caching and make tests more verbose
  travis: different repos for different versions
  travis: even more stupid...
  stupidity...
  travis: switch to other Boost PPA and test 1.53 and 1.55
sweeper: incorporate @memmett's remarks

see https://github.com/Parallel-in-Time/PFASST/pull/77#discussion-diff-16250875
Merge pull request #77 from torbjoernk/feature/sweeper-tweaks

LG
cmake: add option for GCC profiling

using `-ggdb3` and `-gp` with GCC enables verbose debugging and
profiling abilities useful for further analysis; also the tests will get
compiled with `-ftest-coverage` if both CMake variables
(`pfasst_BUILD_TESTS` and `pfasst_WITH_GCC_PROF`) are enabled and you
are compiling with GCC
cmake and tests: enable and provide test coverage analysis

Using lcov and genhtml and a little shell script we are now able to
generate test coverage results with a single command (assuming one has a
build available with GCC)
Merge pull request #78 from torbjoernk/feature/profiler-support

Sweet!
fix for aggegrated coverage results

I've faild to use lcov correctly so it did not aggegrate all tests