From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <alexander.turenko@tarantool.org>
Received: from smtp15.mail.ru (smtp15.mail.ru [94.100.176.133])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (No client certificate requested)
 by dev.tarantool.org (Postfix) with ESMTPS id 76C6D4696C3
 for <tarantool-patches@dev.tarantool.org>;
 Sat, 25 Apr 2020 10:24:26 +0300 (MSK)
Date: Sat, 25 Apr 2020 10:24:19 +0300
From: Alexander Turenko <alexander.turenko@tarantool.org>
Message-ID: <20200425072419.u2dz5sfxlooqaq4q@tkn_work_nb>
References: <cover.1587577457.git.avtikhon@tarantool.org>
 <103723afef82d73d9e8e3c250f646f2c97c3edfb.1587577457.git.avtikhon@tarantool.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
In-Reply-To: <103723afef82d73d9e8e3c250f646f2c97c3edfb.1587577457.git.avtikhon@tarantool.org>
Subject: Re: [Tarantool-patches] [PATCH v2 3/3] Skip failing test from
	out-of-source build
List-Id: Tarantool development patches <tarantool-patches.dev.tarantool.org>
List-Unsubscribe: <https://lists.tarantool.org/mailman/options/tarantool-patches>, 
 <mailto:tarantool-patches-request@dev.tarantool.org?subject=unsubscribe>
List-Archive: <https://lists.tarantool.org/pipermail/tarantool-patches/>
List-Post: <mailto:tarantool-patches@dev.tarantool.org>
List-Help: <mailto:tarantool-patches-request@dev.tarantool.org?subject=help>
List-Subscribe: <https://lists.tarantool.org/mailman/listinfo/tarantool-patches>, 
 <mailto:tarantool-patches-request@dev.tarantool.org?subject=subscribe>
To: "Alexander V. Tikhonov" <avtikhon@tarantool.org>
Cc: Oleg Piskunov <o.piskunov@tarantool.org>, tarantool-patches@dev.tarantool.org

On Wed, Apr 22, 2020 at 08:44:45PM +0300, Alexander V. Tikhonov wrote:
> Skipped failing test app-tap/http_client.test.lua

What is the reason? Why tarantool is different at all depending of a way
to build? Or it is something with testing system?

Please, provide some details. Or, if it is something in testing system
like 'X not going to be copied to Y', then, maybe, fix it right here?

> from out-of-source build. Left #4258 issue opened
> till it will be fixed.
> 
> Part of #4258