public inbox for openembedded-core@lists.openembedded.org
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: ross.burton@arm.com, Mikko Rapeli <mikko.rapeli@linaro.org>
Cc: "openembedded-core@lists.openembedded.org"
	<openembedded-core@lists.openembedded.org>
Subject: Re: [OE-core] [PATCH] oeqa/sdk: add out-of-tree kernel module building test
Date: Mon, 15 Jul 2024 14:13:20 +0100	[thread overview]
Message-ID: <f6af48a9af1107d8555767c64010779ea15d3105.camel@linuxfoundation.org> (raw)
In-Reply-To: <ADC09946-15C3-478B-A833-DDC3A595820F@arm.com>

On Mon, 2024-07-15 at 11:18 +0000, Ross Burton via
lists.openembedded.org wrote:
> On 15 Jul 2024, at 11:31, Mikko Rapeli <mikko.rapeli@linaro.org>
> wrote:
> > > +    def test_cryptodev(self):
> > > +        with tempfile.TemporaryDirectory(prefix="cryptodev",
> > > dir=self.tc.sdk_dir) as testdir:
> > > +            git_url =
> > > "https://github.com/cryptodev-linux/cryptodev-linux"
> > > +            # This is a knnown-good commit post-1.13 that builds
> > > with kernel 6.7+
> > > +            git_sha = "bb8bc7cf60d2c0b097c8b3b0e807f805b577a53f"
> > > +
> > > +            sourcedir = os.path.join(testdir, "cryptodev-linux")
> > > +            subprocess.check_output(["git", "clone", git_url,
> > > sourcedir], stderr=subprocess.STDOUT)
> > 
> > Is there any way to cache this, e.g. yocto build download cache?
> > 
> > Adding Internet downloads to test steps is a bad design IMO which
> > eventually
> > causes a lot of failures.
> 
> Yeah, I know.  Calling back into the bitbake fetcher is an option but
> non-trivial to be honest. I hope that cryptodev will make a new
> release at some point as their last release doesn’t actually work
> with anything you’d consider a recent kernel.
> 
> Changing the download code in oeqa to just use the fetcher logic
> would make sense, I’ll put it on the list of things to do.

Where we use tarballs in oeqa, there is code that just directly fishes
them out of DL_DIR. 

Locking becomes harder with git repos but it shouldn't be hard to use
the bitbake fetch API standalone from the metadata.

Cheers,

Richard




      parent reply	other threads:[~2024-07-15 13:13 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-12 18:43 [PATCH] oeqa/sdk: add out-of-tree kernel module building test Ross Burton
2024-07-15 10:31 ` [OE-core] " Mikko Rapeli
2024-07-15 11:18   ` Ross Burton
2024-07-15 11:30     ` Mikko Rapeli
     [not found]     ` <17E25F9219ACA60A.6120@lists.openembedded.org>
2024-07-15 11:35       ` Mikko Rapeli
2024-07-15 13:06         ` Ross Burton
2024-07-15 13:13     ` Richard Purdie [this message]

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=f6af48a9af1107d8555767c64010779ea15d3105.camel@linuxfoundation.org \
    --to=richard.purdie@linuxfoundation.org \
    --cc=mikko.rapeli@linaro.org \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=ross.burton@arm.com \
    /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