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: Pulse Stage should emit the first available element #105

Open
manonthegithub opened this issue Jul 12, 2017 · 7 comments
Open

FAILED: Pulse Stage should emit the first available element #105

manonthegithub opened this issue Jul 12, 2017 · 7 comments
Labels

Comments

@manonthegithub
Copy link
Contributor

[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)

@manonthegithub
Copy link
Contributor Author

Full logs: here

@ktoso
Copy link
Member

ktoso commented Jul 14, 2017

I assume this was one of the timing issues, closing

@ktoso ktoso closed this as completed Jul 14, 2017
@raboof
Copy link
Member

raboof commented Jul 14, 2017

Hmm I think this was actually after the timeouts were widened... but not sure, let's just reopen if/when it happens again 👍

@ktoso
Copy link
Member

ktoso commented Jul 14, 2017

Okey :) sorry if was too eager to close

@manonthegithub
Copy link
Contributor Author

This issue is still reproducing: logs here,
but the #109 duplicates this

@ktoso ktoso reopened this Jul 14, 2017
@ktoso
Copy link
Member

ktoso commented Jul 14, 2017

Thanks, my bad!

@manonthegithub
Copy link
Contributor Author

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
Labels
Projects
None yet
Development

No branches or pull requests

3 participants