forked from liquidmetal-dev/flintlock
-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Try to fix EventService test failures
I was not able to reproduce the issue on my machine (why would I), first I did a bit of cleanup to reduce the nested definitions. It's a bit easier to follow now. Added extra logging about contexts, so we can know which one throws the `code = Canceled desc = context canceled` error. Created a PR on my fork and restarted the test job 4 times, none of them failed. I assume the real fix is break after `subscriber.cancel()`. I'm not 100% convinced, but potentially when we close the context and next time checking for `eventCh` or `eventErrCh`, theoretically both of them are closed when the next loop starts, but we are talking very short CPU cycles, so anything can happen. Related to liquidmetal-dev#115 Intentionally not marking wth `Fixes #`.
- Loading branch information
Showing
1 changed file
with
56 additions
and
42 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters