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
Reconnect is used (why)? #46
Milestone
Comments
Gerold103
added a commit
to tarantool/tarantool
that referenced
this issue
Dec 3, 2019
The problem was in that the test uses the global trigger box.session.on_disconnect() to set a global variable by one connection. But test-run can do multiple connects/reconnects to the same instance. That led to multiple invocations of box.session.on_disconnect(), which could override the global variable in unexpected ways and moments. The patch makes only one session execute that trigger. Probably related to tarantool/test-run#46 Follow up #4627
Gerold103
added a commit
to tarantool/tarantool
that referenced
this issue
Dec 5, 2019
The problem was in that the test uses the global trigger box.session.on_disconnect() to set a global variable by one connection. But test-run can do multiple connects/reconnects to the same instance. That led to multiple invocations of box.session.on_disconnect(), which could override the global variable in unexpected ways and moments. The patch makes only one session execute that trigger. Probably related to tarantool/test-run#46 Follow up #4627
Totktonada
pushed a commit
to tarantool/tarantool
that referenced
this issue
Dec 5, 2019
The problem was in that the test uses the global trigger box.session.on_disconnect() to set a global variable by one connection. But test-run can do multiple connects/reconnects to the same instance. That led to multiple invocations of box.session.on_disconnect(), which could override the global variable in unexpected ways and moments. The patch makes only one session execute that trigger. Probably related to tarantool/test-run#46 Follow up #4627 Reviewed-by: Alexander Turenko <alexander.turenko@tarantool.org>
Totktonada
pushed a commit
to tarantool/tarantool
that referenced
this issue
Dec 5, 2019
The problem was in that the test uses the global trigger box.session.on_disconnect() to set a global variable by one connection. But test-run can do multiple connects/reconnects to the same instance. That led to multiple invocations of box.session.on_disconnect(), which could override the global variable in unexpected ways and moments. The patch makes only one session execute that trigger. Probably related to tarantool/test-run#46 Follow up #4627 Reviewed-by: Alexander Turenko <alexander.turenko@tarantool.org> (cherry picked from commit 9643fdc)
Totktonada
pushed a commit
to tarantool/tarantool
that referenced
this issue
Dec 5, 2019
The problem was in that the test uses the global trigger box.session.on_disconnect() to set a global variable by one connection. But test-run can do multiple connects/reconnects to the same instance. That led to multiple invocations of box.session.on_disconnect(), which could override the global variable in unexpected ways and moments. The patch makes only one session execute that trigger. Probably related to tarantool/test-run#46 Follow up #4627 Reviewed-by: Alexander Turenko <alexander.turenko@tarantool.org> (cherry picked from commit 9643fdc)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Can't test transactions if
switch
command calls reconnect.test-run/lib/preprocessor.py
Line 311 in 8e86a60
test-run/lib/preprocessor.py
Line 323 in 8e86a60
The text was updated successfully, but these errors were encountered: