-
Notifications
You must be signed in to change notification settings - Fork 12
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
use non-default ports for clickhouse #13
Conversation
9fd491e
to
b612bb6
Compare
b612bb6
to
af37cfa
Compare
af37cfa
to
ae1d946
Compare
ae1d946
to
1f9a530
Compare
13501c3
to
5b3c0ff
Compare
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.
I like the approach of assigning ports to make tests parallel! I suggest we make a text file listing all of those assignments (like "nil/tests/cometa: 9002; nil/tests/journald_forwarder: 9001"), so that if you need a port for a new test, you don't have to search through all the tests.
Even with fixes I get
I don't understand how we can fix ThreadSanitizer... |
5b3c0ff
to
74c8b68
Compare
74c8b68
to
56b86db
Compare
As it was suggested in review.
Ok. Done c50ae4d |
Seems it helps to prevent following issue: ``` 2025-01-27T20:18:44.9644193Z nil> ThreadSanitizer: failed to restore address 0x100675c0eb0 2025-01-27T20:18:44.9644532Z nil> FAIL github.com/NilFoundation/nil/nil/services/synccommittee/prover/tracer 70.749s 2025-01-27T20:18:44.9644974Z nil> ok github.com/NilFoundation/nil/nil/services/synccommittee/prover/tracer/internal/mpttracer 1.228s ``` I don't understand that is a reason of such failure but seems it helps in case we decrease memory pressure during the test.
use non-default ports for clickhouse
Two tests (cometa + journald_forwarder) conflicted because of Clickhouse. This patch fixes it.