Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1mkf1a-0005YV-AJ for pgsql-bugs@arkaria.postgresql.org; Wed, 10 Nov 2021 04:15:50 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1mkf1Z-0003my-8r for pgsql-bugs@arkaria.postgresql.org; Wed, 10 Nov 2021 04:15:49 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1mkf1Z-0003mo-0s for pgsql-bugs@lists.postgresql.org; Wed, 10 Nov 2021 04:15:49 +0000 Received: from mail-qk1-x729.google.com ([2607:f8b0:4864:20::729]) by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1mkf1W-0000ch-Bo for pgsql-bugs@lists.postgresql.org; Wed, 10 Nov 2021 04:15:48 +0000 Received: by mail-qk1-x729.google.com with SMTP id j2so1291819qkl.7 for ; Tue, 09 Nov 2021 20:15:46 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=leadboat.com; s=google; h=date:from:to:cc:subject:message-id:references:mime-version :content-disposition:content-transfer-encoding:in-reply-to :user-agent; bh=NpxohAClZUrEgCue8ibrmFh7hmjSW65oy0F417PUq0I=; b=M+CMCI244vyI7I5YpnstJL7WnW7DjD/QwsyDkOY7pMCZar/LLX3Ifr/E9efFbLwhGS MBs0LeyR8ktuqgdHft10qF9WV+YnOkoTGsOpb0DQIgRHh02vQhQojeR8sOX0OwB5Vczd YBMgWp6+brk28nsX3291Ii8djt1cB097DEudQ= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:content-transfer-encoding :in-reply-to:user-agent; bh=NpxohAClZUrEgCue8ibrmFh7hmjSW65oy0F417PUq0I=; b=khjMkl0sQGqbYiFPJsA5uvaFaS4b/0ZoXNHYTrV0AIrpniTO/j9TJHcdRjpRlwRsZO Ws/pjuLdpywam9iQZ8jRVCPksZwtjIuoHfEC9k37F/jy2AhN9IwrO/gr6uJ6r/JaGQk6 /I5JNSE01G3SgtYpY6p7Q5Z8bxnpcANSIbdbPEiwqtS03L4shu21pGokYkm1ukSefYNv FUREjNnb6gMg7InH9IZ0PqWxg/a8TgqwH0EtsIjas3uCv8wFG7E7Mb6W20ydt8D1hAi9 /D06JVLfuZFjTJWG+8zdTX+jlWtmsir7I3U5e1+vKJuH462EUDiWFn6TDKmJcpIHvnKJ X7nw== X-Gm-Message-State: AOAM532e8fExsS+kRWiJOdQG0l4hvSGReQh9gEx35vRdnV1NN/GKOsqF z3deveVwfzQmGnXriKI7HfLdvA== X-Google-Smtp-Source: ABdhPJw/ko6iaRMAsjIt/4/ekToY1h+xZC8p+O+0Zzp+UShjVecQHXFrcDcxiSTR1rux8inBMhwPKg== X-Received: by 2002:a05:620a:2589:: with SMTP id x9mr10255760qko.152.1636517745426; Tue, 09 Nov 2021 20:15:45 -0800 (PST) Received: from rfd.leadboat.com ([2600:1702:a20:5750::46]) by smtp.gmail.com with ESMTPSA id bk7sm12983889qkb.72.2021.11.09.20.15.43 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 09 Nov 2021 20:15:44 -0800 (PST) Date: Tue, 9 Nov 2021 20:15:41 -0800 From: Noah Misch To: Andrey Borodin Cc: PostgreSQL mailing lists , Michael Paquier , Tom Lane , Peter Geoghegan , Andres Freund Subject: Re: conchuela timeouts since 2021-10-09 system upgrade Message-ID: <20211110041541.GA971565@rfd.leadboat.com> References: <593C6C66-F19E-412A-9896-F1F5B272424A@yandex-team.ru> <20210925201012.GC4134968@rfd.leadboat.com> <20211017151205.GA2384251@rfd.leadboat.com> <9BA43784-E4A7-4638-900C-FC9868C388FA@yandex-team.ru> <20211019030212.GB3403374@rfd.leadboat.com> <20211024050028.GA3310519@rfd.leadboat.com> <64835CF9-D9AA-49BF-A685-01C23B1023C1@yandex-team.ru> <20211024161942.GB3945842@rfd.leadboat.com> <640FA6DC-A998-4499-B3B4-2773685B8C56@yandex-team.ru> <20211029025600.GB298507@rfd.leadboat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <20211029025600.GB298507@rfd.leadboat.com> User-Agent: Mutt/1.5.24 (2015-08-30) List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On Thu, Oct 28, 2021 at 07:56:00PM -0700, Noah Misch wrote: > On Sun, Oct 24, 2021 at 09:03:27PM +0300, Andrey Borodin wrote: > > > 24 окт. 2021 г., в 19:19, Noah Misch написал(а): > > > These failures started on 2021-10-09, the day conchuela updated from DragonFly > > > v4.4.3-RELEASE to DragonFly v6.0.0-RELEASE. It smells like a kernel bug. > > > Since the theorized kernel bug seems not to affect > > > src/test/subscription/t/015_stream.pl, I wonder if we can borrow a workaround > > > from other tests. One thing in common with src/test/recovery/t/017_shm.pl and > > > the newest failure sites is that they don't write anything to the child stdin. > > > > If not, does passing the script via stdin, like "pgbench -f- > > > > > > I'll test it tomorrow, the refactoring does not seem trivial given we use many simultaneous scripts. > > Did that work? Commit 7f580aa should make this unnecessary for v12+ > contrib/amcheck tests, but older branches still need a fix, and 017_shm.pl > needs a fix in all branches. A backup plan is just to skip affected tests on > dragonfly 6+. Since the breakage has been limited to so few tests, I'm > optimistic that a better workaround will present itself. Is this still in your queue, or not? The conchuela breakage in src/test/recovery and v11+v10 src/bin/pgbench is a large source of buildfarm noise right now.