-
Notifications
You must be signed in to change notification settings - Fork 60
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: CRDTActorOwnedTests.test_actorOwned_theLastWrittenOnUpdateCallbackWins #14
Comments
FYI @yim-lee Likely we may get some failures now that we moved to new CI, perhaps timing issues? 🤔 |
One possibility is that the test starts modifying the I think the owning actor should stay in "not ready" state until it's registered. Currently the owner has no way of knowing when that happens. Let me add logic to allow that to be done and update tests. This might be the problem here:
We don't wait for the |
Unlikely #16 would help. Both |
Does not reproduce on mac, I think it may be a timing issue... SOMEHOW. Agree that #16 does not inherently solve it. I was able to reproduce it twice now in docker:
Sadly without logs; I will keep it running for a while with logs now; Notes:
Will try to get us a tracelog |
and added tracelog for the local messages repro, no logs, takes 3 seconds
correct execution with tracelog
|
Reproduced with tracelog:
So yeah, it is as you said, the write happens before register; This is worrying and that should be fixed, as we are "owned" we should guarantee ordering of those two. |
…ateCallbackWins (#21) Motivation: The aforementioned test fails intermittently. See #14. Modifications: There is an existing issue with `.ask`. Use `.tell` instead 1) as a workaround; 2) since we don't need the result anyway. Also made some minor improvements to code docs. Result: No more flaky test hopefully!
…ateCallbackWins (#21) Motivation: The aforementioned test fails intermittently. See #14. Modifications: There is an existing issue with `.ask`. Use `.tell` instead 1) as a workaround; 2) since we don't need the result anyway. Also made some minor improvements to code docs. Result: No more flaky test hopefully!
Failed in validation
https://ci.swiftserver.group/job/swift-distributed-actors-swift50-p1rb/6/consoleFull
The text was updated successfully, but these errors were encountered: