cannot build multiple trees concurrently
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Galera |
Fix Released
|
Undecided
|
Unassigned | ||
1.x |
Fix Released
|
Medium
|
Teemu Ollakka | ||
2.x |
Fix Released
|
Medium
|
Stewart Smith |
Bug Description
This is a big showstopper for our test infrastructure.
Each machine can have multiple builds going on at once. These are in completely different trees. However, there seems to be a TCP port hard coded as part of the compile as we sometimes get this:
builder_
Running suite(s): write_set
100%: Checks: 8, Failures: 0, Errors: 0
Running suite(s): trx_handle
100%: Checks: 2, Failures: 0, Errors: 0
Running suite(s): service_thd
100%: Checks: 2, Failures: 0, Errors: 0
Running suite(s): ist
terminate called after throwing an instance of 'gu::Exception'
what(): failed to open ist listener to tcp://127.
at galera/
0%: Checks: 1, Failures: 0, Errors: 1
galera/
Total tests failed: 1
scons: *** [galera/
scons: building terminated because of errors.
Build step 'Use builders from another project' marked build as failure
[WARNINGS] Skipping publisher since build result is FAILURE
Recording test results
Finished: FAILURE
My suggested fix is to instead of hard coding the port, ask the OS to assign you one by binding to port 0 .
Related branches
- Alex Yurchenko: Approve
-
Diff: 187 lines (+50/-15)3 files modifiedgalerautils/src/gu_network.cpp (+14/-1)
galerautils/tests/gu_net_test.cpp (+34/-13)
gcomm/test/check_util.cpp (+2/-1)
Changed in galera: | |
status: | New → Fix Committed |
Changed in galera: | |
status: | Fix Committed → Fix Released |
fixed in r104