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 1nIZNC-00081P-V7 for pgsql-hackers@arkaria.postgresql.org; Fri, 11 Feb 2022 17:06:18 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1nIZNB-0002Uv-Bw for pgsql-hackers@arkaria.postgresql.org; Fri, 11 Feb 2022 17:06:17 +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 1nIZNB-0002Um-1c for pgsql-hackers@lists.postgresql.org; Fri, 11 Feb 2022 17:06:17 +0000 Received: from mail-wm1-x32e.google.com ([2a00:1450:4864:20::32e]) by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1nIZN8-0007Ky-2A for pgsql-hackers@lists.postgresql.org; Fri, 11 Feb 2022 17:06:15 +0000 Received: by mail-wm1-x32e.google.com with SMTP id k127-20020a1ca185000000b0037bc4be8713so7633292wme.3 for ; Fri, 11 Feb 2022 09:06:13 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=enterprisedb.com; s=google; h=message-id:date:mime-version:user-agent:subject:content-language:to :references:from:in-reply-to:content-transfer-encoding; bh=mePN+pgz8FUM521a1dDMX4aTf+Qk0X2hu/02TPpryBs=; b=jBHSGLI8E1aKkpw2NNjOLCcvy7i7SSl5xUdXBvt+ua55d/7xtcXlyjg/yzylZFJ+a7 R4xdDR/g/QvL8DV4OHc5Svp4dGe02Jb9/Y415Lv4wlFPTsOZ7d++0DLz5w2bGHmo24EJ 5QO2kzmr/Uudbj8wAM3To1ty2zFh76ODgYmyu0++V04Mr950eQQ5Elr9hn6eBkKLRiBc RWaDAuJ6vozIwcC+ZFgElf6b1QIwyMnSHZxascuAt43usKo4W4v4r6zXWpH+9xpkeh8t le+WlYTWwMLUKngE3nBULTPctI8eQFtjmn2Qo6eXNAkQO8RF9Hdlv/rAvkN5Jv+RCHn6 MRcg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:message-id:date:mime-version:user-agent:subject :content-language:to:references:from:in-reply-to :content-transfer-encoding; bh=mePN+pgz8FUM521a1dDMX4aTf+Qk0X2hu/02TPpryBs=; b=Ms089rAmKsdEV+cqBXRE54uATBYKqcVgXh64FVGeZXSjkwpZTgU/HNm+0jyKoL7B01 qjnftel8PallObGWxt+L8X7Szv/E0tiewrKhp/AA+nQ7Wu7GFbWAGTZC8S4J8m/PdkFD Mt3qCk4lFK8xXEb1HzosZ2bKZBTyqw+W31V+xrPZeblDs4Q+jUPAZjuP8HDLUATuczDN b3YekTCHuWygB9+coE7s7tAOkuFCfAHGB40IhtTysDGhJnxAbhzVrlC6h96iIZw9IVOb sJk1ONbxe2kR1JI7IUsNkgsM+xfir4i8LlwrV8Ogdr+So/p81GPWLuUa8XQiEKlIhh+m +Clg== X-Gm-Message-State: AOAM531Yw1D+/EgyRFDaesegDauuEUZRFWeEtGhmvQoEuzCC/Od3VOD+ AlwcQto+gX1UCqwMUk/LSEzdGRcWfjWRlGTvq8+iRszYUR5IQkKzDiwcXCl+jyL13JyNs+E1MEj xlY7UfY9XGmcj+//fVrXhd1XORSIlrmd2ievv9P2Buq68QxQS/j9h5C8k/YVmuGwN5xWLa6gi9B R81PABoR3OWJf7iEIdzVEAUEFCOn6aG4zqT7UsUb4SsCU9QDvJ8kleVYn0hdDP X-Google-Smtp-Source: ABdhPJzTXEeB5l/EDfQVAgLn+X02lTuzR2O1UafZPTRa9K/hHBNgSIcbho7MOG088ueN5MIFLKRAgg== X-Received: by 2002:a05:600c:4204:: with SMTP id x4mr997129wmh.123.1644599172507; Fri, 11 Feb 2022 09:06:12 -0800 (PST) Received: from [10.137.0.18] (static-84-42-175-93.net.upcbroadband.cz. [84.42.175.93]) by smtp.gmail.com with ESMTPSA id q2sm21127704wrw.14.2022.02.11.09.06.11 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Fri, 11 Feb 2022 09:06:12 -0800 (PST) Message-ID: Date: Fri, 11 Feb 2022 18:06:10 +0100 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101 Thunderbird/91.5.0 Subject: Re: the build farm is ok, but not the hippopotamus (or the jay) Content-Language: en-US To: Robert Haas , PostgreSQL Hackers , info@cspug.cz References: From: Tomas Vondra In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-CLOUD-SEC-AV-Info: enterprisedb,google_mail,monitor X-CLOUD-SEC-AV-Sent: true X-Gm-Spam: 0 X-Gm-Phishy: 0 List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On 2/11/22 16:16, Robert Haas wrote: > Hi, > > I was looking over the buildfarm results yesterday and this morning, > and things seem to be mostly green, but not entirely. 'hippopotamus' > was failing yesterday with strange LDAP-related errors, and is now > complaining about pgsql-Git-Dirty, which I assume means that someone > is doing something funny on that machine manually. 'jay' has the same > maintainer and is also showing some failures. > Yes, those are "my" machines. I've been upgrading the OS on them, and this is likely a fallout from that. Sorry about the noise. regards -- Tomas Vondra EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company