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;
Subject: Re: linux-next: Tree for Jul 12 (no Rust)
To:     Miguel Ojeda <miguel.ojeda.sandonis@gmail.com>
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>
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>
From:   Randy Dunlap <rdunlap@infradead.org>
Message-ID: <c8349e27-4941-e639-9a26-b665b2fa6a68@infradead.org>
Date:   Tue, 13 Jul 2021 13:20:42 -0700
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101
 Thunderbird/78.11.0
MIME-Version: 1.0
In-Reply-To: <CANiq72mDL+CA9CnhDG5Sij4ufVzGHrWvZ9eaWSSXQMDYbpL-6w@mail.gmail.com>
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Precedence: bulk

On 7/13/21 10:36 AM, Miguel Ojeda wrote:
> Hi Randy,
> 
> On Tue, Jul 13, 2021 at 5:31 AM Randy Dunlap <rdunlap@infradead.org> wrote:
>>
>> OK, I found some 'patch' failures in my download logs, so something
>> in my scripts didn't do its job.
>>
>> Thanks for bringing it up!
> 
> Thanks for looking -- if I can help with something on my side on the
> Rust tree, please let me know.
> 
> Also, if you found what went wrong (e.g. the end result after `patch`
> failed applying something), it would be nice to know, in case this
> comes up again.

Hi Miguel,

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.

Thanks.