From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: 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 dev.tarantool.org (Postfix) with ESMTPS id 1E5E44765E0 for ; Tue, 22 Dec 2020 02:21:28 +0300 (MSK) From: Oleg Koshovetc Message-ID: <97201353-fc4d-df72-e92c-261cc76107fc@tarantool.org> Date: Tue, 22 Dec 2020 02:20:37 +0300 MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8"; format="flowed" Content-Transfer-Encoding: 8bit Content-Language: en-US Subject: [Tarantool-patches] [PATCH] tpch: use normal perf image instead of patched one List-Id: Tarantool development patches List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Alexander Tikhonov , tsafin@tarantool.org Cc: tarantool-patches@dev.tarantool.org TPCH benchmark used to be launched with numerous patches applied to tarantool's source code. Not only it does not bench actual tarantool, it also adds extra complications in benchmarking process. Recently we got pipeline failed only because of tpch benchmark as it would fail to launch because it failed to apply all of the needed patches. Instead of fixing the patches we'd better get rid of that patching in the first place. ---  .gitlab-ci.yml | 2 +-  1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/.gitlab-ci.yml b/.gitlab-ci.yml index 208ab24..935a27b 100644 --- a/.gitlab-ci.yml +++ b/.gitlab-ci.yml @@ -328,7 +328,7 @@ perf_tpch:    <<: *perf_docker_test_definition    tags:      - docker_sh2_perf -  image: ${IMAGE_PERF_BUILT}_tpch +  image: ${IMAGE_PERF_BUILT}    variables:      <<: *perf_vars_definition      BENCH: 'tpch' -- 2.7.4