From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from [87.239.111.99] (localhost [127.0.0.1]) by dev.tarantool.org (Postfix) with ESMTP id 50656BB27EA; Fri, 14 Jun 2024 16:55:58 +0300 (MSK) DKIM-Filter: OpenDKIM Filter v2.11.0 dev.tarantool.org 50656BB27EA DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=tarantool.org; s=dev; t=1718373358; bh=XkOl+tDu7lw63bkbB93VoBNCDpur7AbtkWexkafCJpY=; h=Date:To:Cc:References:In-Reply-To:Subject:List-Id: List-Unsubscribe:List-Archive:List-Post:List-Help:List-Subscribe: From:Reply-To:From; b=i/wm7Lg2SAxjRM7qDikYwiW6Tyoy71U376FvAcqhQOUQZhIhcaUbwugr0IOkorvRg 3Ljw2UgRNAxKsZ2UZ0orwHukSx2jkWr7XXCkYr96+H5Gyf9LpbZNNTEurKfvvpNJ/n XBmn3yINGpHcp2RRF4AEXNBY4ZUdktu3hpt1xl2g= Received: from smtp59.i.mail.ru (smtp59.i.mail.ru [95.163.41.97]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by dev.tarantool.org (Postfix) with ESMTPS id 4A668BB27EA for ; Fri, 14 Jun 2024 16:55:57 +0300 (MSK) DKIM-Filter: OpenDKIM Filter v2.11.0 dev.tarantool.org 4A668BB27EA Received: by smtp59.i.mail.ru with esmtpa (envelope-from ) id 1sI7PI-00000006KUw-0OAW; Fri, 14 Jun 2024 16:55:56 +0300 Content-Type: multipart/alternative; boundary="------------4UKLogZFNzFeUm8xzbZLUvYQ" Message-ID: Date: Fri, 14 Jun 2024 16:55:55 +0300 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Content-Language: en-US To: Maxim Kokryashkin , Sergey Kaplun Cc: Sergey Bronnikov , tarantool-patches@dev.tarantool.org References: <6777a43e3012332d04493f93d6afe7fb4156af1b.1712841312.git.sergeyb@tarantool.org> In-Reply-To: X-Mailru-Src: smtp X-4EC0790: 10 X-7564579A: B8F34718100C35BD X-77F55803: 4F1203BC0FB41BD9AC8CA0B4439200FAC9ED020CEABC603EBFE2E3CBD10956AC00894C459B0CD1B9B1F9AEE5C2D9DAF6A593836A7F99035DE2684E7CC9143834208D6C111855FAF31E35E39F85F323EC X-7FA49CB5: FF5795518A3D127A4AD6D5ED66289B5278DA827A17800CE74AE62C7A8488879AEA1F7E6F0F101C67BD4B6F7A4D31EC0BCC500DACC3FED6E28638F802B75D45FF8AA50765F7900637D24CDE3D695BBBC6EA1F7E6F0F101C6723150C8DA25C47586E58E00D9D99D84E1BDDB23E98D2D38B043BF0FB74779F36A92CBB90B123F118F84CFA7891A069878E315D26C611F7FFA471835C12D1D9774AD6D5ED66289B5278DA827A17800CE767883B903EA3BAEA9FA2833FD35BB23D2EF20D2F80756B5F868A13BD56FB6657A471835C12D1D977725E5C173C3A84C3CF36E64A7E3F8E58117882F4460429728AD0CFFFB425014E868A13BD56FB6657D81D268191BDAD3DC09775C1D3CA48CFFD8C409E70A4B323BA3038C0950A5D36C8A9BA7A39EFB766D91E3A1F190DE8FDBA3038C0950A5D36D5E8D9A59859A8B6EEAEF4E9976DC6BE76E601842F6C81A1F004C906525384303E02D724532EE2C3F43C7A68FF6260569E8FC8737B5C2249EC8D19AE6D49635B68655334FD4449CB9ECD01F8117BC8BEAAAE862A0553A39223F8577A6DFFEA7C1156E5889A6D309143847C11F186F3C59DAA53EE0834AAEE X-C1DE0DAB: 0D63561A33F958A5C98C3C2FE2922CC85002B1117B3ED696B2A182980EF56AC41A1B8FE1FED62FE8823CB91A9FED034534781492E4B8EEAD17AEC49845D0B908 X-C8649E89: 1C3962B70DF3F0ADE00A9FD3E00BEEDF3FED46C3ACD6F73ED3581295AF09D3DF87807E0823442EA2ED31085941D9CD0AF7F820E7B07EA4CFE0838E700D400E2CCA7023D33C83B12D379BA7BAEDC33E1350A719089EBDDFAC49C71475D3C80931BC11D93875BCBCAC70A926A59D5EA1D4EFF61D1633E05298AEA55ECE841634B0C226CC413062362A913E6812662D5F2AB9AF64DB4688768036DF5FE9C0001AF333F2C28C22F508233FCF178C6DD14203 X-D57D3AED: 3ZO7eAau8CL7WIMRKs4sN3D3tLDjz0dLbV79QFUyzQ2Ujvy7cMT6pYYqY16iZVKkSc3dCLJ7zSJH7+u4VD18S7Vl4ZUrpaVfd2+vE6kuoey4m4VkSEu530nj6fImhcD4MUrOEAnl0W826KZ9Q+tr5ycPtXkTV4k65bRjmOUUP8cvGozZ33TWg5HZplvhhXbhDGzqmQDTd6OAevLeAnq3Ra9uf7zvY2zzsIhlcp/Y7m53TZgf2aB4JOg4gkr2biojqIk+/laaskCt54pN1lkMRA== X-Mailru-Sender: 520A125C2F17F0B1E52FEF5D219D6140B1F9AEE5C2D9DAF6A593836A7F99035DE29C8CB5EBEAFC860152A3D17938EB451EB5A0BCEC6A560B3DDE9B364B0DF289BE2DA36745F2EEB5CEBA01FB949A1F1EEAB4BC95F72C04283CDA0F3B3F5B9367 X-Mras: Ok Subject: Re: [Tarantool-patches] [PATCH luajit 1/4][v2] ci: add a workflow for testing with AVX512 X-BeenThere: tarantool-patches@dev.tarantool.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: Tarantool development patches List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , From: Sergey Bronnikov via Tarantool-patches Reply-To: Sergey Bronnikov Errors-To: tarantool-patches-bounces@dev.tarantool.org Sender: "Tarantool-patches" This is a multi-part message in MIME format. --------------4UKLogZFNzFeUm8xzbZLUvYQ Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit On 05.05.2024 15:29, Maxim Kokryashkin wrote: > Hi! > On Thu, Apr 18, 2024 at 11:24:42AM UTC, Sergey Kaplun wrote: >> Hi, Sergey >> >> On 16.04.24, Sergey Bronnikov wrote: >>> Hi, Sergey >>> >>> On 12.04.2024 13:27, Sergey Kaplun wrote: >> >> >>>>> diff --git a/.github/actions/setup-linux/action.yml b/.github/actions/setup-linux/action.yml >>>>> index f0171b83..19bdcfa2 100644 >>>>> --- a/.github/actions/setup-linux/action.yml >>>>> +++ b/.github/actions/setup-linux/action.yml >>>>> @@ -17,3 +17,15 @@ runs: >>>>> apt -y update >>>>> apt -y install cmake gcc make ninja-build perl >>>>> shell: bash >>>>> + - name: Detect a presence of AVX512 >>>> I suppose it shouldn't be a part of setup-linux action, >>> It was requested by Max. >> And what is the rationale for it? >> Why don't use this detection during steps in our workflow? >> >> Hence, we avoid this unnecesary step for other jobs. > I've suggested to move that to a separate action, not to the > setup-linux. Do you have objections to move this steps to workflow? > > --------------4UKLogZFNzFeUm8xzbZLUvYQ Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit


On 05.05.2024 15:29, Maxim Kokryashkin wrote:
Hi!
On Thu, Apr 18, 2024 at 11:24:42AM UTC, Sergey Kaplun wrote:

Hi, Sergey

On 16.04.24, Sergey Bronnikov wrote:

Hi, Sergey

On 12.04.2024 13:27, Sergey Kaplun wrote:

<snipped>


diff --git a/.github/actions/setup-linux/action.yml b/.github/actions/setup-linux/action.yml
index f0171b83..19bdcfa2 100644
--- a/.github/actions/setup-linux/action.yml
+++ b/.github/actions/setup-linux/action.yml
@@ -17,3 +17,15 @@ runs:
          apt -y update
          apt -y install cmake gcc make ninja-build perl
        shell: bash
+    - name: Detect a presence of AVX512

I suppose it shouldn't be a part of setup-linux action,

It was requested by Max.

And what is the rationale for it?
Why don't use this detection during steps in our workflow?

Hence, we avoid this unnecesary step for other jobs.

I've suggested to move that to a separate action, not to the
setup-linux.
Do you have objections to move this steps to workflow?

<snipped>
--------------4UKLogZFNzFeUm8xzbZLUvYQ--