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: PersistentActorSpec #22052

Closed
patriknw opened this issue Dec 21, 2016 · 0 comments
Closed

failed: PersistentActorSpec #22052

patriknw opened this issue Dec 21, 2016 · 0 comments
Labels
failed Tickets that indicate a CI failure, likely a flakey test
Milestone

Comments

@patriknw
Copy link
Member

patriknw commented Dec 21, 2016

https://jenkins.akka.io:8498/job/akka-multi-node-nightly/4478

[ERROR] [12/21/2016 06:33:18.731] [PersistenceSpec-akka.actor.default-dispatcher-9] [akka://PersistenceSpec/user/$sb] boom (akka.persistence.TestException)
[WARN] [12/21/2016 06:33:18.732] [PersistenceSpec-akka.actor.default-dispatcher-5] [akka://PersistenceSpec/user/$sb] received dead letter from Actor[akka://PersistenceSpec/system/akka.persistence.snapshot-store.local#-1812017407]: LoadSnapshotResult(None,9223372036854775807)
[info] - must be able to persist events that happen during recovery *** FAILED *** (10 milliseconds)
[info]   java.lang.AssertionError: assertion failed: expected List(a-1, a-2, rc-1, rc-2), found List(a-1, a-2, rc-1, rc-2, rc-3)
[info]   at scala.Predef$.assert(Predef.scala:170)
[info]   at akka.testkit.TestKitBase$class.expectMsg_internal(TestKit.scala:388)
[info]   at akka.testkit.TestKitBase$class.expectMsg(TestKit.scala:364)
[info]   at akka.testkit.TestKit.expectMsg(TestKit.scala:814)
[info]   at akka.persistence.PersistentActorSpec$$anonfun$1$$anonfun$apply$mcV$sp$44.apply(PersistentActorSpec.scala:1157)
[info]   at akka.persistence.PersistentActorSpec$$anonfun$1$$anonfun$apply$mcV$sp$44.apply(PersistentActorSpec.scala:1154)
@patriknw patriknw added 1 - triaged Tickets that are safe to pick up for contributing in terms of likeliness of being accepted failed Tickets that indicate a CI failure, likely a flakey test labels Dec 21, 2016
@patriknw patriknw added 3 - in progress Someone is working on this ticket and removed 1 - triaged Tickets that are safe to pick up for contributing in terms of likeliness of being accepted labels Jan 9, 2017
@patriknw patriknw added this to the 2.5.0 milestone Jan 9, 2017
@patriknw patriknw modified the milestones: 2.5-M1, 2.5.0 Jan 24, 2017
patriknw pushed a commit that referenced this issue Feb 21, 2017
@patriknw patriknw modified the milestones: 2.4.18, 2.5.0 Feb 21, 2017
patriknw pushed a commit that referenced this issue Feb 21, 2017
patriknw added a commit that referenced this issue Feb 22, 2017
customise test for race between GetState and persistAsync handler #22052 (for validation)
@patriknw patriknw removed the 3 - in progress Someone is working on this ticket label Feb 22, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
failed Tickets that indicate a CI failure, likely a flakey test
Projects
None yet
Development

No branches or pull requests

1 participant