Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18;
MIME-Version: 1.0
References: <20210712120828.5c480cdc@canb.auug.org.au> <c47a7f0b-4b5a-30c3-ee1e-2973793a9534@infradead.org>
 <20210713111029.77bfb9bb@elm.ozlabs.ibm.com> <56341950-abd6-8a9c-42ca-7eb91c55cc90@infradead.org>
 <8ed74a96-7309-3370-4b8b-376bface7cc6@infradead.org> <47f394e5-c319-3b79-92ad-d33b0d96993e@infradead.org>
 <CANiq72mDL+CA9CnhDG5Sij4ufVzGHrWvZ9eaWSSXQMDYbpL-6w@mail.gmail.com> <c8349e27-4941-e639-9a26-b665b2fa6a68@infradead.org>
In-Reply-To: <c8349e27-4941-e639-9a26-b665b2fa6a68@infradead.org>
From:   Miguel Ojeda <miguel.ojeda.sandonis@gmail.com>
Date:   Tue, 13 Jul 2021 22:31:10 +0200
Message-ID: <CANiq72kHCwbBU5cebPaj32dOb9DspB_fLhw3tALcw2ssxjkCdA@mail.gmail.com>
Subject: Re: linux-next: Tree for Jul 12 (no Rust)
To:     Randy Dunlap <rdunlap@infradead.org>
Cc:     Stephen Rothwell <sfr@rothwell.id.au>,
        Stephen Rothwell <sfr@canb.auug.org.au>,
        Linux Next Mailing List <linux-next@vger.kernel.org>,
        Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
        Masahiro Yamada <masahiroy@kernel.org>,
        Miguel Ojeda <ojeda@kernel.org>
Content-Type: text/plain; charset="UTF-8"
Precedence: bulk

On Tue, Jul 13, 2021 at 10:20 PM Randy Dunlap <rdunlap@infradead.org> wrote:
>
> It was either a script bug (but I haven't seen this one before)
> or a user error (more likely).
> My daily linux-next builds are started by a cron job but the don't
> always start when they should (IMO), so I may have started it
> manually... but then the error that I saw would have only happened
> if 2 linux-next builds were started at almost the same time (one
> by cron, one manually by me) - I don't know if that happened or not.
>
> Today's linux-next builds didn't have any similar problem and I doubt
> that I can reconstruct what happened exactly.

I see -- it should be unlikely that someone else sees it then.

Thanks!

Cheers,
Miguel