Hello,

if one future fails in a combined future a large message with stacktrace is spit out via java.util.logging. This is inconvenient.

Aug 17, 2015 7:12:44 PM com.google.common.util.concurrent.Futures$CombinedFuture setExceptionAndMaybeLog 
SEVERE: input future failed

We know of lots cases where this behaviour cannot or shuold not be avoided (for instance, jobs failing because of timeouts).

The exception is propagated and handled correctly by the combined future so we have other means to find out what's wrong and handle the case gracefully (it has to be done anyway).

I can think of a few workarounds, which may even need to be applied in grops, which are equally pesky:

• Working it around by java.util.logging at the system level is not practical as it requires manual changes at the OS/environment level.
• Working it around by java.util.logging programmatically is very inconvenient because it needs to be done before starting each test, or requires all test to be derived from a common "wrapper".
• Working it around by java.util.logging via command line is also very inconvenient because it needs to be done for each test execution environment (either surefire or Eclipse JUnit runner).
• Working it around at the code level by wrapping the input futures with a fallback (or similar) for the known cases requires lots of coding. Also breaks the downstream error handling.
• Working it around by bridging JUL to Slf4j tanks performance.

Can this be avoided? Forking and rebuilding from source just to comment out a logging line is a bit overkill.