From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from localhost (localhost [127.0.0.1]) by turing.freelists.org (Avenir Technologies Mail Multiplex) with ESMTP id C6CDA283B9 for ; Mon, 26 Aug 2019 12:54:49 -0400 (EDT) Received: from turing.freelists.org ([127.0.0.1]) by localhost (turing.freelists.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QkaPZCeWyOnZ for ; Mon, 26 Aug 2019 12:54:49 -0400 (EDT) Received: from smtpng2.m.smailru.net (smtpng2.m.smailru.net [94.100.179.3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by turing.freelists.org (Avenir Technologies Mail Multiplex) with ESMTPS id 34795282C6 for ; Mon, 26 Aug 2019 12:54:49 -0400 (EDT) Date: Mon, 26 Aug 2019 19:54:32 +0300 From: Alexander Turenko Subject: [tarantool-patches] Re: [PATCH v1] test: app/socket flaky fails at 1951 line Message-ID: <20190826165432.pgktm64nhukvhlrt@tkn_work_nb> References: <84e74bd123f4eb616a194d63c49ea871557d5a77.1566565478.git.avtikhon@tarantool.org> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <84e74bd123f4eb616a194d63c49ea871557d5a77.1566565478.git.avtikhon@tarantool.org> Sender: tarantool-patches-bounce@freelists.org Errors-to: tarantool-patches-bounce@freelists.org Reply-To: tarantool-patches@freelists.org List-Help: List-Unsubscribe: List-software: Ecartis version 1.0.0 List-Id: tarantool-patches List-Subscribe: List-Owner: List-post: List-Archive: To: "Alexander V. Tikhonov" Cc: Kirill Yukhin , tarantool-patches@freelists.org > wch:put("Fu") > c:send("354 Please type your message\n") > sc:close() > -c:receive("*l", "Line: ") > +-- avtikhon: Temporary blocked the following check to avoid of testing > +-- failures, due to issue is well known and under investigation at: > +-- https://github.com/tarantool/tarantool/issues/4426 > +c:receive("*l", "Line: ") and nil I would propose to run such tests after all parallel ones instead of disabling: https://github.com/tarantool/test-run/pull/188 Please, verify whether such approch works good. Then collect all tests that requires such machinery and mark them as fragile in one commit. WBR, Alexander Turenko.