Bamboo handles test failure reports from Maven2/Surefire incorrectly, this should be easy to reproduce.

For one of my projects, I do a recursive build for a multi-module Maven2 build, lets say the build consists of modules A and B in that order. The actual Maven2 command is "mvn clean install" from the root of the reactor. The following sequence will produce wrong error reports:
1) Bamboo builds module A without errors, B fails with errors. This is reported correctly.
2) A new build of the same reactor starts.
2) Bamboo builds module A, this time with errors. Bamboo now, incorrectly reports errors in both module A and B, even though only tests in module A fail.

Bamboo should time-stamp the build-start and only include error reports if they are newer than the time-stamp.

The command "mvn clean install" will handle the reactor recursively, i.e.:
1) Delete all output from module A's target directory (clean).
2) Build module A (install).
3) Delete all output from module B (clean).
4) Build module B (install).

Whereas the functionality that Bamboo supplies should be similar to executing two sequential Maven commands, i.e.:
1) mvn clean (will recursively delete all output from the target directory) and
2) mvn install (builds all modules in the reactor recursively)