-
Notifications
You must be signed in to change notification settings - Fork 13
Update and extend tests for connection_acquisition_timeout
setting.
#474
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
Conversation
Tests did not encompass routing drivers
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The port change in TestMaxConnectionPoolSize
can make javascript pipeline unstable. 🔥 🚒
Also added a comment to avoid future changes to touch the port.
* `sessionConnectionTimeoutMs` * `updateRoutingTableTimeoutMs`
tests/stub/driver_parameters/test_update_routing_table_timeout_ms.py
Outdated
Show resolved
Hide resolved
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
⏲️ 💥
f62a2ae
to
db41dec
Compare
Merging on red: JS flakiness (timed out), Python is expected to fail (see PR description + UTC fix pending) |
Backport of #474 and #404 [ADR 006](https://github.com/neo-technology/drivers-adr/blob/main/adrs/006-acquisition-timeouts.md) * Update and extend tests for `connection_acquisition_timeout` setting. Tests did not encompass routing drivers * Add new timeout driver config options * `sessionConnectionTimeoutMs` * `updateRoutingTableTimeoutMs` * Add new feature flag * `API_CONNECTION_ACQUISITION_TIMEOUT = Feature:API:ConnectionAcquisitionTimeout"`
Tests did not encompass routing drivers
Python is expected to fail until this pr is merged
This PR adds tests for ADR 006 (internal link).