In the NoPrefetchGetMore test, it is currently possible for the main thread to enter the network interface when it is already acting as the network. This causes a deadlock in the test. This occurs when we run hasReadyRequests before the destruction of the NetworkGuard in this lambda, which exits the network.
NoPrefetch test in TaskExecutorCursorTest can deadlock
ExportXML Word Printable JSON
- Assignee:
-
Ben Shteinfeld
- Reporter:
-
Ben Shteinfeld
- Votes:
-
0 Vote for this issue - Watchers:
-
4 Start watching this issue
- Created:
- Updated:
- Resolved: