From: "Bondarev, Alex" <alexbnd@amazon•com>
To: Stephen Rothwell <sfr@canb•auug.org.au>
Cc: "linux-next@vger•kernel.org" <linux-next@vger•kernel.org>
Subject: Re: Linux-next compilation and build
Date: Thu, 26 Dec 2024 15:29:48 +0000 [thread overview]
Message-ID: <080CD985-138C-42CA-A46D-175FB7C694A5@amazon.com> (raw)
In-Reply-To: <20241224111924.14263694@canb.auug.org.au>
Sure thing, we'll see how we can automate this.
Any specific format we should adhere to? (of course we will include the tag that was used and architecture).
On 2024.12.23, 18:19, "Stephen Rothwell" <sfr@canb•auug.org.au <mailto:sfr@canb•auug.org.au>> wrote:
Hi Alex,
On Mon, 23 Dec 2024 18:20:50 +0000 "Bondarev, Alex" <alexbnd@amazon•com <mailto:alexbnd@amazon•com>> wrote:
>
> On Mon, Dec 23, 2024 at 04:16:03PM +0000, Bondarev, Alex wrote:
> > I'm part of a team in AWS that uses the linux-next branch with canonical's
> > ppa to test for build success.
> > git: git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
> > ppa: ppa:canonical-kernel-team/ppa
>
> > As a result of this daily test (we try the latest available at time of
> > testing), we have almost immediate knowledge of the "goodness" of the branch
> > (if the machine doesn't boot after update of if the compilation fails). We
> > are currently running build on aarch64 and x86_64 types.
> >
> > The question is should we notify via a mailing list or a single destination
> > about this failure? Will it improve the detection time for a bad merge?
Thanks for testing!
Notifications should be sent to linux-next@vger•kernel.org <mailto:linux-next@vger•kernel.org> and cc'd to
linux-kernel@vger•kernel.org <mailto:linux-kernel@vger•kernel.org> and any developers or maintainers that you
think may be involved with the code causing problems.
--
Cheers,
Stephen Rothwell
next prev parent reply other threads:[~2024-12-26 15:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4FF05C5D-F7C0-4212-9917-0D94DF3DCA60@contoso.com>
[not found] ` <vnymur42hlcdiodh2pyoikdc5646zceiuf6sizgde4jmeqd4xi@b7xt7wuq3aaz>
2024-12-23 18:20 ` FW: Linux-next compilation and build Bondarev, Alex
2024-12-24 0:19 ` Stephen Rothwell
2024-12-26 15:29 ` Bondarev, Alex [this message]
2025-01-05 3:34 ` Stephen Rothwell
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=080CD985-138C-42CA-A46D-175FB7C694A5@amazon.com \
--to=alexbnd@amazon$(echo .)com \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=sfr@canb$(echo .)auug.org.au \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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