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 27AF26ECCC; Thu, 15 Oct 2026 10:13:25 +0300 (MSK) DKIM-Filter: OpenDKIM Filter v2.11.0 dev.tarantool.org 27AF26ECCC DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=tarantool.org; s=dev; t=1792048405; bh=3dBj3G7RvalwnvJ7+L6bB576+xyMaU4aNMyZIn2vA4k=; h=Date:To:References:In-Reply-To:Subject:List-Id:List-Unsubscribe: List-Archive:List-Post:List-Help:List-Subscribe:From:Reply-To:Cc: From; b=wFuHFyQ4qFZ8EO/Oe2Qq/t2cewzWJ3C26z+ucUiypLBIx2VEKT1iWzkr0BtTT7TI8 VSWawQJb9mKzYvQPA8mOq0RcjOKSGk2GoGHs6e8tZdVNCUiavR7pBd8B7Wcieo/GS5 ayvlvlWblo6lePe/SmSo1ARjxCbzNqdBf7pIuJ14= Received: from send150.i.mail.ru (send150.i.mail.ru [89.221.237.245]) (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 EF1536ECCC for ; Thu, 15 Oct 2026 10:13:23 +0300 (MSK) DKIM-Filter: OpenDKIM Filter v2.11.0 dev.tarantool.org EF1536ECCC Received: by exim-smtp-84d6fb566c-g6vwg with esmtpa (envelope-from ) id 1xHFeU-00000000Ri7-3jT1; Thu, 15 Oct 2026 10:13:23 +0300 Date: Thu, 15 Oct 2026 10:13:01 +0300 To: Alexander Turenko Message-ID: References: <1791982697.240786681@f763.i.mail.ru> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <1791982697.240786681@f763.i.mail.ru> X-Mailru-Src: smtp X-4EC0790: 10 X-7564579A: B8F34718100C35BD X-77F55803: 4F1203BC0FB41BD99EAF3395699E207583DFEF69283EDD4005B63114A44AD341182A05F5380850406C6EB25D76E3CF653DE06ABAFEAF670588ABAB80448918C7608DD9D2B758CC29EEF59CA297A41560 X-7FA49CB5: FF5795518A3D127A4AD6D5ED66289B5278DA827A17800CE7AB524098FB2F2222EA1F7E6F0F101C67BD4B6F7A4D31EC0BCC500DACC3FED6E28638F802B75D45FF8AA50765F79006370CE92FB8C11ED3D88638F802B75D45FF914D58D5BE9E6BC1A93B80C6DEB9DEE97C6FB206A91F05B20250807D0795A6502E070BE324C7D3C4C7855BE635B4304EF6B57BC7E64490611E7FA7ABCAF51C92176DF2183F8FC7C0D9442B0B5983000E8941B15DA834481F9449624AB7ADAF372E808ACE2090B5E14AD6D5ED66289B5259CC434672EE63711DD303D21008E298D5E8D9A59859A8B6B372FE9A2E580EFC725E5C173C3A84C37C6C241D9975906435872C767BF85DA2F004C90652538430E4A6367B16DE6309 X-C1DE0DAB: 0D63561A33F958A50F97F7B8774F3A0D5002B1117B3ED6966E9F36CB430288C6F09842853758E9E5823CB91A9FED034534781492E4B8EEAD643C8550F8485502BDAD6C7F3747799A X-C8649E89: 1C3962B70DF3F0AD73CAD6646DEDE1918E10F71CB4DF9F96AB70F9BE574AE9C625B6776AC983F447FC0B9F89525902EE6F57B2FD27647F25E66C117BDB76D6592865F30546BE7DAB794C2EB1A36306A4B3CA871BB32EAD738E2E02AF02189A4A381B627E47985A0FB8341EE9D5BE9A0A9852E458005FC70FE5A82661FEC513AEA903419AED55D5DA6536EB022892E5344C41F94D744909CECFA6C6B0C050A61A8CAF69B82BA93681CD72808BE417F3B9E0E7457915DAA85F X-D57D3AED: 3ZO7eAau8CL7WIMRKs4sN3D3tLDjz0dLbV79QFUyzQ2Ujvy7cMT6pYYqY16iZVKkSc3dCLJ7zSJH7+u4VD18S7Vl4ZUrpaVfd2+vE6kuoey4m4VkSEu53w8ahmwBjZKM/YPHZyZHvz5uv+WouB9+ObcCpyrx6l7KImUglyhkEat/+ysWwi0gdhEs0JGjl6ggRWTy1haxBpVdbIX1nthFXOcIETfglQORZ0zpDET4Zrk3igikrdHlWHJ+A6ObdAL13KofJT2Itw4= X-Mailru-Sender: 689FA8AB762F73937C9FA53A4753B31351C36F5F9C5F9B40AC5B36679935A90566D6FBDC6682F338E49D44BB4BD9522A059A1ED8796F048DB274557F927329BE89D5A3BC2B10C37545BD1C3CC395C826B4A721A3011E896F X-Mras: Ok Subject: Re: [Tarantool-patches] [PATCH 2/2] ci: run ARM64 jobs on GitHub-hosted runners 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 Kaplun via Tarantool-patches Reply-To: Sergey Kaplun Cc: tarantool-patches@dev.tarantool.org Errors-To: tarantool-patches-bounces@dev.tarantool.org Sender: "Tarantool-patches" On 14.10.26, Alexander Turenko wrote: > > > after the patch we will use github runners and it is worth set a timeout > > > for jobs, > > > > > > otherwise we might run out of time on the runners (AFAIK it is limited > > > there). > > > > Agree here. IINM, the default is 6 hours [1], which is too much for our > > tests. > > The longest job is Valgrind job, which is running about 12 minutes. > > I suppose the limit of 30 minutes is reasonable. > > > > > > > > [1]: https://docs.github.com/en/actions/reference/workflows-and-actions/workflow-syntax#jobsjob_idtimeout-minutes > > I agree that it is good to have job timeouts. > > I’d let the maintainers to set appropriate timeouts. > Personally, I neither use the jobs nor know details about them. > And I don’t think that it becomes more urgent when we switch > from 6 parallel runners to 60 (I’d say the opposite). > > WBR, Alexander Turenko OK, lets do it in the separate patch. -- Best regards, Sergey Kaplun