On 2014-07-22 15:12, Joseph Fernandes wrote:
Hi All,
As with further investigation found the following,
1) Was the able to reproduce the issue, without running the complete
regression, just by running bug-1112559.t only on slave30(which is been
rebooted and a clean gluster setup).
On 07/22/2014 07:19 AM, Anders Blomdell wrote:
Could this be a time to propose that gluster understands port reservation a'la
systemd (LISTEN_FDS),
and make the test harness make sure that random ports do not collide with the
set of expected ports,
which will be beneficial when starting from
On 2014-07-22 16:44, Justin Clift wrote:
On 22/07/2014, at 3:28 PM, Joe Julian wrote:
On 07/22/2014 07:19 AM, Anders Blomdell wrote:
Could this be a time to propose that gluster understands port reservation
a'la systemd (LISTEN_FDS),
and make the test harness make sure that random ports do
