On Mon, Jul 15, 2024 at 02:30:52PM +0300, Mikko Rapeli via 
lists.openembedded.org wrote:
> On Mon, Jul 15, 2024 at 11:18:30AM +0000, Ross Burton wrote:
> > On 15 Jul 2024, at 11:31, Mikko Rapeli <[email protected]> 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.
> 
> How about changing cryptodev-linux recipe to provice a package with the 
> needed source code,
> install that package to an image, and then express the dependency to package 
> in
> the oeqa test?

And by image I mean the SDK under test.

Cheers,

-Mikko
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#201914): 
https://lists.openembedded.org/g/openembedded-core/message/201914
Mute This Topic: https://lists.openembedded.org/mt/107188034/21656
Group Owner: [email protected]
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[[email protected]]
-=-=-=-=-=-=-=-=-=-=-=-

Reply via email to