From owner-freebsd-current@freebsd.org Sun Aug 16 15:17:43 2020 Return-Path: Delivered-To: freebsd-current@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 85F303BEFC0 for ; Sun, 16 Aug 2020 15:17:43 +0000 (UTC) (envelope-from "") Received: from mout01.posteo.de (mout01.posteo.de [185.67.36.141]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "*.posteo.de", Issuer "StartCom Class 3 Primary Intermediate Server CA" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 4BV1522MTjz4TYZ for ; Sun, 16 Aug 2020 15:17:42 +0000 (UTC) (envelope-from "") Received: from submission (posteo.de [89.146.220.130]) by mout01.posteo.de (Postfix) with ESMTPS id B8B3A160060 for ; Sun, 16 Aug 2020 17:17:39 +0200 (CEST) Received: from customer (localhost [127.0.0.1]) by submission (posteo.de) with ESMTPSA id 4BV14y4yG4z6tmV for ; Sun, 16 Aug 2020 17:17:38 +0200 (CEST) From: Walter von Entferndt To: freebsd-current@freebsd.org Subject: Re: CFT for vendor openzfs - week 5 reminder + memdisk images Date: Sun, 16 Aug 2020 17:16:38 +0200 Message-ID: <9004644.RH3biPoPvx@t450s.local.lan> In-Reply-To: References: MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1597591062; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=k0dFIBzBXLxJBxx5bXGFvwXdWAKUbT+aY8VMnsr097o=; b=ypVMWoWcFnTkMALe74gGnWZ/l9wd89+Je7XDWXTNXuA3pdqpsXlBmK35UPzhzjC5T2dBvO kCH6fhk7YMOvlC3VNdzYF4a4TJpOFLj9LlyRwO4zwzrD0WxTPBgWbIu2Ck0jezPppo1/m0 gB5OTNVLcydOxbOiV2g2vNd2dkweD2Bunr5GEHfAYB7gPVanNdkDgYe/VVuBUhY5uKqLUt mEDZSysFEjJaBTMRtRqsagdLwZsparRaQI4dfdi/Mtk+YXoXpLAtzgi6yCh1ZNNJSKQwVM S/H/DjY9meR3apYzX61pd37UWxj+JYvzd8Q/Kc9h8jU79zkGAz/3zssw/3CbEQ== ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1597591062; a=rsa-sha256; cv=none; b=yOrGuyKwJJ6kAPZM4vUyQ23Q+yf9hY/br6YUD9i1ZoIrnTsTzFst3PKIljLDOKjxGjfzfn ktn6RX+l47FU0cj5+GuqR4FJUh21T0U8yZi0viEaiROCKYTz5uVnBNC64+wOFAC80Ky1lR 0beilKIxX/04qosih3PPq4PlJFJvUkkGuycXfUvwfUPt25qF11Ki9tI21d1K9ji197tHng RiS1q7Zplla9aiT9pHp5QK6XNWpKiJM5a/VA0TI+184Q0m31HbyUdZnEtIUHjDPczHUsb8 E4j60Jg4xPEeQQms1Rb7AP4n+NS5YdnCC3Zl52fNr4TqEl7EcLdmvHtgVaNSIA== ARC-Authentication-Results: i=1; mx1.freebsd.org; dkim=none; spf=none (mx1.freebsd.org: domain of mout01.posteo.de has no SPF policy when checking 185.67.36.141) smtp.helo=mout01.posteo.de X-Rspamd-Queue-Id: 4BV1522MTjz4TYZ X-Spamd-Bar: - X-Spamd-Result: default: False [-1.78 / 15.00]; RCVD_TLS_ALL(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; ARC_NA(0.00)[]; FROM_HAS_DN(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; NEURAL_HAM_LONG(-0.91)[-0.911]; MIME_GOOD(-0.10)[text/plain]; TO_DN_NONE(0.00)[]; PREVIOUSLY_DELIVERED(0.00)[freebsd-current@freebsd.org]; RCPT_COUNT_ONE(0.00)[1]; RCVD_COUNT_THREE(0.00)[3]; ARC_SIGNED(0.00)[i=1]; RCVD_IN_DNSWL_MED(-0.20)[185.67.36.141:from]; NEURAL_HAM_SHORT(-0.47)[-0.472]; NEURAL_HAM_MEDIUM(-0.70)[-0.698]; R_SPF_NA(0.00)[no SPF record]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:8495, ipnet:185.67.36.0/23, country:DE]; FROM_NEQ_ENVFROM(0.00)[walter.von.entferndt@posteo.net,]; CTE_CASE(0.50)[]; DMARC_POLICY_SOFTFAIL(0.10)[posteo.net : No valid SPF, No valid DKIM,none] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.33 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 16 Aug 2020 15:17:43 -0000 At Sonntag, 16. August 2020, 14:00:00 CEST, Matthew Macy wrote: > Yes, this appears to have been going on for at least the last week. > The FreeBSD infrastructure directly available to developers appears to > be unreliable for serving large files. Individuals with accounts on > freefall have been able to scp the files. It's possible that we may > just end up sharing images more widely by way of releng generated > images after commit. I'll see if there's an alternative for the last > week of the CFT. Why not use torrent as a workaround? -- =|o) "Stell' Dir vor es geht und keiner kriegt's hin." (Wolfgang Neuss)