AmqpConnectorsTest.publishFanoutAndConsume

[2m]

[info] Test akka.stream.alpakka.amqp.AmqpConnectorsTest.publishFanoutAndConsume started
[error] Test akka.stream.alpakka.amqp.AmqpConnectorsTest.publishFanoutAndConsume failed: java.util.concurrent.TimeoutException: null, took 10.468 sec
[error]     at java.util.concurrent.CompletableFuture.timedGet(CompletableFuture.java:1771)
[error]     at java.util.concurrent.CompletableFuture.get(CompletableFuture.java:1915)
[error]     at scala.concurrent.java8.FuturesConvertersImpl$CF.scala$concurrent$java8$FuturesConvertersImpl$CF$$super$get(FutureConvertersImpl.scala:84)
[error]     at scala.concurrent.java8.FuturesConvertersImpl$CF$$anonfun$get$2.apply(FutureConvertersImpl.scala:84)
[error]     at scala.concurrent.BlockContext$DefaultBlockContext$.blockOn(BlockContext.scala:53)
[error]     at scala.concurrent.package$.blocking(package.scala:123)
[error]     at scala.concurrent.java8.FuturesConvertersImpl$CF.get(FutureConvertersImpl.scala:84)
[error]     at akka.stream.alpakka.amqp.AmqpConnectorsTest.publishFanoutAndConsume(AmqpConnectorsTest.java:141)
[error]     ...
[info] Test run finished: 1 failed, 0 ignored, 2 total, 10.785s

https://travis-ci.org/akka/alpakka/builds/173177910

[johanandren]

(should we have a failed label here like in Akka to keep these separated from actual confirmed bugs?)

[ktoso]

yeah, porting entire tag structure from akka would make sense IMO.