Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Failed: ClientServerSpec: The low-level HTTP infrastructure should timeouts should support server timeouts should close connection with idle client after idleTimeout #3235

Open
johanandren opened this issue Jun 11, 2020 · 2 comments
Labels
failed Tickets that indicate a Jenkins failure

Comments

@johanandren
Copy link
Member

https://jenkins.akka.io:8498/job/akka-http-nightly-release-10.1/AKKA_VERSION=master,Node=akka-http-nightly-node,SCALA_VERSION=2.12.10,jdk=AdoptOpenJDK%208/919/testReport/junit/akka.http.scaladsl/ClientServerSpec/The_low_level_HTTP_infrastructure_should_timeouts_should_support_server_timeouts_should_close_connection_with_idle_client_after_idleTimeout/

Futures timed out after [2 seconds]
	at scala.concurrent.impl.Promise$DefaultPromise.ready(Promise.scala:259)
	at scala.concurrent.impl.Promise$DefaultPromise.result(Promise.scala:263)
	at scala.concurrent.Await$.$anonfun$result$1(package.scala:220)
	at scala.concurrent.BlockContext$DefaultBlockContext$.blockOn(BlockContext.scala:57)
	at scala.concurrent.Await$.result(package.scala:146)
	at akka.http.scaladsl.ClientServerSpec.$anonfun$new$26(ClientServerSpec.scala:260)
@johanandren johanandren added the failed Tickets that indicate a Jenkins failure label Jun 11, 2020
@jrudolph jrudolph changed the title ClientServerSpec: The low-level HTTP infrastructure should timeouts should support server timeouts should close connection with idle client after idleTimeout Failed: ClientServerSpec: The low-level HTTP infrastructure should timeouts should support server timeouts should close connection with idle client after idleTimeout Jun 15, 2020
@jrudolph
Copy link
Member

Here, the client seemed to be too slow to send the request in the 300ms before the idle timeout triggered. So, it triggered even before the request was received and not only afterwards as asserted.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
failed Tickets that indicate a Jenkins failure
Projects
None yet
Development

No branches or pull requests

2 participants