From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from smtpng1.m.smailru.net (smtpng1.m.smailru.net [94.100.181.251]) (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 009E642EF5D for ; Sat, 20 Jun 2020 19:33:20 +0300 (MSK) References: <50a25fbae907f1b0d5406fb2e78d40d3e42a8a8d.1591029888.git.korablev@tarantool.org> <4e9d5184-1b3a-d4de-e040-a3edb6ca38cd@tarantool.org> <20200619123425.GB19725@tarantool.org> From: Vladislav Shpilevoy Message-ID: Date: Sat, 20 Jun 2020 18:33:19 +0200 MIME-Version: 1.0 In-Reply-To: <20200619123425.GB19725@tarantool.org> Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit Subject: Re: [Tarantool-patches] [PATCH v2] vinyl: restart read iterator in case of rolled back WAL List-Id: Tarantool development patches List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Nikita Pettik Cc: tarantool-patches@dev.tarantool.org >> Talking of the tests, I tried running multiple instances of the new >> test: >> >> python test-run.py gh-3395-read-prepared-un gh-3395-read-prepared-un gh-3395-read-prepared-un gh-3395-read-prepared-un gh-3395-read-prepared-un gh-3395-read-prepared-un >> >> And it fails sometimes. So it is flaky. Better fix it before push. > > I've added a tiny fix: > > diff --git a/test/vinyl/gh-3395-read-prepared-uncommitted.test.lua b/test/vinyl/gh-3395-read-prepared-uncommitted.test.lua > index 10b70dd85..70136ddff 100644 > --- a/test/vinyl/gh-3395-read-prepared-uncommitted.test.lua > +++ b/test/vinyl/gh-3395-read-prepared-uncommitted.test.lua > @@ -55,9 +55,7 @@ function read_prepared_with_delay(is_tx_faster_than_wal) > errinj.set("ERRINJ_RELAY_FASTER_THAN_TX", true) > end > errinj.set("ERRINJ_WAL_DELAY", false) > - if not is_tx_faster_than_wal then > - fiber.sleep(0.1) > - end > + fiber.sleep(0.1) > errinj.set("ERRINJ_VY_READ_PAGE_DELAY", false) > local res = c:get() > errinj.set("ERRINJ_WAL_WRITE", false) > > > Could you please check if it still fails on your machine? Now it works.