On Mon, Feb 19, 2018 at 5:58 PM, Nithya Balachandran
wrote:
>
>
> On 19 February 2018 at 13:12, Atin Mukherjee wrote:
>
>>
>>
>> On Mon, Feb 19, 2018 at 8:53 AM, Nigel Babu wrote:
>>
>>> Hello,
>>>
>>> As you all most likely know, we
Hi,
I think I know the reason why tarball size is bigger, could it happen if
tar file has more than one core.
I triggered a build(https://review.gluster.org/19574 to validate all test
cases after enable brick mux) after update "exit_one_failure="no"" in
run-tests.sh
so build has executed
On Mon, Feb 19, 2018 at 5:58 PM, Nithya Balachandran
wrote:
>
>
> On 19 February 2018 at 13:12, Atin Mukherjee wrote:
>>
>>
>>
>> On Mon, Feb 19, 2018 at 8:53 AM, Nigel Babu wrote:
>>>
>>> Hello,
>>>
>>> As you all most likely know,
On 19 February 2018 at 13:12, Atin Mukherjee wrote:
>
>
> On Mon, Feb 19, 2018 at 8:53 AM, Nigel Babu wrote:
>
>> Hello,
>>
>> As you all most likely know, we store the tarball of the binaries and
>> core if there's a core during regression. Occasionally,