Authentication-Results: mail-b.sr.ht; dkim=pass header.d=cmpwn.com header.i=@cmpwn.com
Received: from out0.migadu.com (out0.migadu.com [94.23.1.103])
	by mail-b.sr.ht (Postfix) with ESMTPS id D6A8311EF38
	for <~sircmpwn/sr.ht-discuss@lists.sr.ht>; Mon,  5 Apr 2021 22:31:37 +0000 (UTC)
MIME-Version: 1.0
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cmpwn.com; s=key1;
	t=1617661896;
	h=from:from:reply-to:subject:subject:date:date:message-id:message-id:
	 to:to:cc:cc:mime-version:mime-version:content-type:content-type:
	 content-transfer-encoding:content-transfer-encoding:
	 in-reply-to:in-reply-to:references:references;
	bh=AvR21gYpTwkb9Ge7DzK4PQdnh8CC+Q9dhOe8t9Qe5zI=;
	b=R9NxVb06/JMd54ZbbhFP7vGicr9wn9X6rzGR90y4xXSyzjkYiYw/Jr5+jPSQ0fAgT1OCXx
	xKtR59ZjGOTHLfy9WvLhtfaDLVyKscCL3HozWR56wZDd5mULGH7KxxPuAR9r+qiZ8ZiBh4
	+7N4aOvDCaOAEwtPGVYV5CEYAnXOBDZF5Fn14lZaEggkj+0lqDTxpKLooCZ9BiPN2IKLyP
	T9toNSce4Z7yv4wrWB/K2teWa96WuGDiDHO27GUmPp1C5kYhPHuuQqtBdmL2fjfBAfZdKd
	Q/t1AkZSwIJWKNUUpJhOzAGqkxVvMtoxxKfxz8uPW6Ex4+H9QcqX5in1bbUiGQ==
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset=UTF-8
Date: Mon, 05 Apr 2021 18:31:34 -0400
Message-Id: <CAG5A76NEP9E.1OV8MCM7O2WVM@taiga>
Cc: <~sircmpwn/sr.ht-discuss@lists.sr.ht>
Subject: Re: [builds.sr.ht] Resubmitted builds are not associated with
 original build's project
X-Report-Abuse: Please report any abuse attempt to abuse@migadu.com and include these headers.
From: "Drew DeVault" <sir@cmpwn.com>
To: "Devan Carpenter" <mail@dvn.me>, =?utf-8?q?Ecmel_Berk_Canl=C4=B1er?=
 <me@ecmelberk.com>
References: <34f77392-19fa-5104-736f-10293d857642@ecmelberk.com>
 <CAFSQFE3NRPZ.WR89A2RXMNDE@taiga>
 <b9bb10a1-b85b-d07f-acfe-f3c2dc2783d1@ecmelberk.com>
 <20210405221545.vhbvbjnrlonbsu2u@iyo>
In-Reply-To: <20210405221545.vhbvbjnrlonbsu2u@iyo>
X-Migadu-Flow: FLOW_OUT
X-Migadu-Auth-User: sir@cmpwn.com

On Mon Apr 5, 2021 at 6:15 PM EDT, Devan Carpenter wrote:
> It makes sense because of situations exactly like what Ecmel ran into.
> The *external environment* was the source of the error, not something in
> their repo. Re-running the build _is_ the proper fix in this case.

That your build's results can be affected by external factors is a sign
that your build is insufficiently hermetic. A similar error would be
non-determinism. In either case, it is a problem that should be
corrected, and so long as the problem exists, the failing build status
is quite an apt signal that such a problem is indeed present.