-
Notifications
You must be signed in to change notification settings - Fork 77
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: Pulse Stage should emit the first available element #105
Labels
Comments
Full logs: here |
I assume this was one of the timing issues, closing |
Hmm I think this was actually after the timeouts were widened... but not sure, let's just reopen if/when it happens again 👍 |
Okey :) sorry if was too eager to close |
Thanks, my bad! |
I guess either this one or #109 can be closed as duplicate. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
[info] PulseSpecAutoFusingOff:
[info] Pulse Stage
[info] - should signal demand once every interval (957 milliseconds)
[info] - should keep backpressure if there is no demand from downstream (565 milliseconds)
[info] An initially-opened Pulse Stage
[info] - should emit the first available element *** FAILED *** (174 milliseconds)
[info] A timeout occurred waiting for a future to complete. Queried 7 times, sleeping 15 milliseconds between each query. (PulseSpec.scala:63)
[info] org.scalatest.concurrent.Futures$FutureConcept$$anon$1:
[info] at org.scalatest.concurrent.Futures$FutureConcept.tryTryAgain$1(Futures.scala:538)
The text was updated successfully, but these errors were encountered: