From: Richard Leitner <richard.leitner@skidata.com>
To: Andrei Gherzan <andrei@gherzan.com>
Cc: openembedded <openembedded-devel@lists.openembedded.org>
Subject: Re: [oe] [meta-java][PATCH 1/3] classpath: Use an include file for x11 feature check
Date: Tue, 23 Aug 2022 06:31:43 +0200 [thread overview]
Message-ID: <YwRYL6yEEusxD0gn@skidata.com> (raw)
In-Reply-To: <894c6ed7-e7cb-4434-b132-861ba83a913d@www.fastmail.com>
On Mon, Aug 22, 2022 at 10:28:34AM +0100, Andrei Gherzan wrote:
> On Mon, 22 Aug 2022, at 09:15, Richard Leitner wrote:
> >
> > Unfortunately the testing infrastructure is not public available :(
>
> Got it. That's fine. I'll just keep an eye on the repo.
>
> >
> > But ideas/offers where to host a public test runner are highly
> > appreciated ;-)
>
> What is the current testing plan for the layer?
It's basically running the image tests for arm, armv7, arm64, x86,
x86_64 and ppc with the mejate and mejate-musl distribution.
I can prepare and share a repository containing those kas and gitlab-ci
configurations if that's interesting to you?
regards;rl
> Andrei
next prev parent reply other threads:[~2022-08-23 4:31 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-17 11:43 [meta-java][PATCH 1/3] classpath: Use an include file for x11 feature check Andrei Gherzan
2022-08-17 11:43 ` [meta-java][PATCH 2/3] libmatthew: Include features check from classpath Andrei Gherzan
2022-08-17 11:43 ` [meta-java][PATCH 3/3] dbus-java: " Andrei Gherzan
2022-08-22 7:38 ` [oe] [meta-java][PATCH 1/3] classpath: Use an include file for x11 feature check Richard Leitner
2022-08-22 7:46 ` Andrei Gherzan
2022-08-22 8:15 ` Richard Leitner
2022-08-22 9:28 ` Andrei Gherzan
2022-08-23 4:31 ` Richard Leitner [this message]
2022-08-24 16:29 ` Andrei Gherzan
2022-08-30 9:31 ` Andrei Gherzan
2022-08-30 15:10 ` Richard Leitner
2022-08-30 16:04 ` Andrei Gherzan
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=YwRYL6yEEusxD0gn@skidata.com \
--to=richard.leitner@skidata.com \
--cc=andrei@gherzan.com \
--cc=openembedded-devel@lists.openembedded.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.