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 AEF9E2C793 for ; Fri, 19 Apr 2019 07:46:55 -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 vELznAEIptxF for ; Fri, 19 Apr 2019 07:46:55 -0400 (EDT) Received: from smtp32.i.mail.ru (smtp32.i.mail.ru [94.100.177.92]) (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 6C8CD2C784 for ; Fri, 19 Apr 2019 07:46:55 -0400 (EDT) Date: Fri, 19 Apr 2019 14:46:53 +0300 From: Kirill Yukhin Subject: [tarantool-patches] Re: [PATCH] Set format for spaces with sysview engine Message-ID: <20190419114653.htzk2rilljqi75io@tarantool.org> References: <20190417081320.xwcf3ogkvrspgdu3@tarantool.org> <68ec9d10-4fa6-4997-54bd-4a80b1ca79ce@tarantool.org> <20190418081630.yfe5hi7w2m3bu5lh@tarantool.org> <77d5c2c1-8a26-990c-0fc0-dc40d56f64ae@tarantool.org> <20190418111411.hl4okehi6adv6pvi@tarantool.org> <20190418120840.667b7m5iqtjl2r42@tarantool.org> <5783e513-19e4-182b-941b-9070a7266c92@tarantool.org> <20190418132522.cfpocghcjmjtcpe3@tarantool.org> <20190418141804.GB7924@chai> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <20190418141804.GB7924@chai> 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: tarantool-patches@freelists.org Cc: Vladislav Shpilevoy On 18 Apr 17:18, Konstantin Osipov wrote: > * Kirill Yukhin [19/04/18 17:12]: > > How ofter do you scan list of regression tests? I bet - never. > > But you very often try to extract 2-3 lines of failed case. > > If you work with the test suite as an active maintainer you work > with the files all the time. Otherwise your tests just rot. I see no arguments here, sorry. Of course one work with files all the time, but what's the point? Please, be more specific: which exact problems you won't be able to solve w/ such an approach? Or which of your regular actions will become complicated? After you collected those problems, you might want to compare them w/ clear pros: 1. more testing parallelism 2. simple case extraction: one file, one issue, no surfing aroung thousands of lines. -- Regards, Kirill Yukhin