-
Notifications
You must be signed in to change notification settings - Fork 277
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
Prevent tests failing if they can't get access to a port #2137
Labels
Comments
appetrosyan
added
iroha2-dev
The re-implementation of a BFT hyperledger in RUST
Tests
labels
Apr 22, 2022
ales-tsurko
added a commit
to ales-tsurko/iroha
that referenced
this issue
Jun 7, 2022
Signed-off-by: Ales Tsurko <[email protected]>
ales-tsurko
added a commit
to ales-tsurko/iroha
that referenced
this issue
Jun 7, 2022
Signed-off-by: Ales Tsurko <[email protected]>
ales-tsurko
added a commit
to ales-tsurko/iroha
that referenced
this issue
Jun 13, 2022
Signed-off-by: Ales Tsurko <[email protected]>
ales-tsurko
added a commit
to ales-tsurko/iroha
that referenced
this issue
Jun 15, 2022
Signed-off-by: Ales Tsurko <[email protected]>
ales-tsurko
added a commit
to ales-tsurko/iroha
that referenced
this issue
Jun 15, 2022
… data_model) Signed-off-by: Ales Tsurko <[email protected]>
ales-tsurko
added a commit
to ales-tsurko/iroha
that referenced
this issue
Jun 20, 2022
Signed-off-by: Ales Tsurko <[email protected]>
ales-tsurko
added a commit
to ales-tsurko/iroha
that referenced
this issue
Jun 20, 2022
… data_model) Signed-off-by: Ales Tsurko <[email protected]>
ales-tsurko
added a commit
to ales-tsurko/iroha
that referenced
this issue
Jun 22, 2022
Signed-off-by: Ales Tsurko <[email protected]>
ales-tsurko
added a commit
to ales-tsurko/iroha
that referenced
this issue
Jun 22, 2022
… data_model) Signed-off-by: Ales Tsurko <[email protected]>
ales-tsurko
added a commit
to ales-tsurko/iroha
that referenced
this issue
Jun 22, 2022
…t crate Signed-off-by: Ales Tsurko <[email protected]>
ales-tsurko
added a commit
to ales-tsurko/iroha
that referenced
this issue
Jun 22, 2022
Signed-off-by: Ales Tsurko <[email protected]>
ales-tsurko
added a commit
to ales-tsurko/iroha
that referenced
this issue
Jun 22, 2022
Signed-off-by: Ales Tsurko <[email protected]>
ales-tsurko
added a commit
to ales-tsurko/iroha
that referenced
this issue
Jun 22, 2022
… data_model) Signed-off-by: Ales Tsurko <[email protected]>
ales-tsurko
added a commit
to ales-tsurko/iroha
that referenced
this issue
Jun 22, 2022
…t crate Signed-off-by: Ales Tsurko <[email protected]>
ales-tsurko
added a commit
to ales-tsurko/iroha
that referenced
this issue
Jun 22, 2022
Signed-off-by: Ales Tsurko <[email protected]>
ales-tsurko
added a commit
to ales-tsurko/iroha
that referenced
this issue
Jun 24, 2022
Signed-off-by: Ales Tsurko <[email protected]>
appetrosyan
pushed a commit
that referenced
this issue
Jun 24, 2022
BAStos525
pushed a commit
to BAStos525/soramitsu-iroha
that referenced
this issue
Jul 8, 2022
…yperledger-iroha#2363) Signed-off-by: BAStos525 <[email protected]>
5 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Our current solution of randomly mapping ports at run-time is not the best, because of how it can fail on restricted systems, but also fails to work corretly on e.g. nextest (#2136).
My preferred solution would be to actively handle the OS error and re-assign the port in case of failure, so that random failed port assignments don't bring down the entire test harness.
The text was updated successfully, but these errors were encountered: