forked from fl00r/go-tarantool-1.6
-
Notifications
You must be signed in to change notification settings - Fork 58
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
test: flaky crud/TestCrudGenerateData #288
Comments
I have such error on CI:
|
|
|
The reason is replicaset configuration on the same port as
local uri = 'guest@127.0.0.1:3013'
local cfg = {
bucket_count = 300,
sharding = {
[box.info().cluster.uuid] = {
replicas = {
[box.info().uuid] = {
uri = uri,
name = 'storage',
master = true,
},
},
},
},
}
|
oleg-jukovec
added a commit
that referenced
this issue
May 13, 2023
oleg-jukovec
added a commit
that referenced
this issue
May 13, 2023
An instance was listening on a testing port until the configuration was complete. At the end of the configuration, the port was reopened. As a result, we saw connection loss in tests. Closes #288
oleg-jukovec
added a commit
that referenced
this issue
May 15, 2023
oleg-jukovec
added a commit
that referenced
this issue
May 15, 2023
An instance was listening on a testing port until the configuration was complete. At the end of the configuration, the port was reopened. As a result, we saw connection loss in tests. Closes #288
This was referenced May 15, 2023
oleg-jukovec
added a commit
that referenced
this issue
May 17, 2023
oleg-jukovec
added a commit
that referenced
this issue
May 17, 2023
An instance was listening on a testing port until the configuration was complete. At the end of the configuration, the port was reopened. As a result, we saw connection loss in tests. Closes #288
oleg-jukovec
added a commit
that referenced
this issue
May 18, 2023
oleg-jukovec
added a commit
that referenced
this issue
May 18, 2023
An instance was listening on a testing port until the configuration was complete. At the end of the configuration, the port was reopened. As a result, we saw connection loss in tests. Closes #288
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
log.txt
The text was updated successfully, but these errors were encountered: