From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from smtp33.i.mail.ru (smtp33.i.mail.ru [94.100.177.93]) (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 1FB6B469710 for ; Fri, 15 May 2020 17:51:57 +0300 (MSK) Date: Fri, 15 May 2020 17:51:56 +0300 From: Kirill Yukhin Message-ID: <20200515145156.dep7lidaxzlgeur2@tarantool.org> References: <2ad8677044f4a2eac3ec7ae3479dbebe09ea3f15.1589452096.git.avtikhon@tarantool.org> MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <2ad8677044f4a2eac3ec7ae3479dbebe09ea3f15.1589452096.git.avtikhon@tarantool.org> Subject: Re: [Tarantool-patches] [PATCH v1] gitlab-ci: disable perf tesing in schedulled runs List-Id: Tarantool development patches List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: "Alexander V. Tikhonov" Cc: Oleg Piskunov , tarantool-patches@dev.tarantool.org Hello, On 14 май 13:29, Alexander V. Tikhonov wrote: > Release branches should be regularly run using gitlab-ci pipeline > schedules: > https://gitlab.com/tarantool/tarantool/pipeline_schedules > It will help to detect flaky issues. But there is no need to rerun > too long running performance testing, to block it in schedules the > option 'schedules' in 'except:' field was set. > > Part of #4974 > --- > > Github: https://github.com/tarantool/tarantool/tree/avtikhon/schedule_except_perf > Issue: https://github.com/tarantool/tarantool/issues/4974 I've checked your patch into 1.10, 2.3, 2.4 and master. -- Regards, Kirill Yukhin