linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Randy Dunlap <rdunlap@infradead.org>
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>
Subject: Re: linux-next: Tree for Jul 12 (no Rust)
Date: Tue, 13 Jul 2021 13:20:42 -0700	[thread overview]
Message-ID: <c8349e27-4941-e639-9a26-b665b2fa6a68@infradead.org> (raw)
In-Reply-To: <CANiq72mDL+CA9CnhDG5Sij4ufVzGHrWvZ9eaWSSXQMDYbpL-6w@mail.gmail.com>

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.


  reply	other threads:[~2021-07-13 20:20 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-12  2:08 linux-next: Tree for Jul 12 Stephen Rothwell
2021-07-12 15:24 ` linux-next: Tree for Jul 12 (no Rust) Randy Dunlap
2021-07-13  1:10   ` Stephen Rothwell
2021-07-13  1:43     ` Randy Dunlap
2021-07-13  3:03       ` Randy Dunlap
2021-07-13  3:31         ` Randy Dunlap
2021-07-13 17:36           ` Miguel Ojeda
2021-07-13 20:20             ` Randy Dunlap [this message]
2021-07-13 20:31               ` Miguel Ojeda

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=c8349e27-4941-e639-9a26-b665b2fa6a68@infradead.org \
    --to=rdunlap@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=masahiroy@kernel.org \
    --cc=miguel.ojeda.sandonis@gmail.com \
    --cc=ojeda@kernel.org \
    --cc=sfr@canb.auug.org.au \
    --cc=sfr@rothwell.id.au \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).