public inbox for openembedded-core@lists.openembedded.org
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Alexander Kanavin <alex.kanavin@gmail.com>
Cc: Frederic Martinsons <frederic.martinsons@gmail.com>,
	 openembedded-core@lists.openembedded.org,
	alex.kiernan@gmail.com
Subject: Re: [OE-core] [PATCH V6 5/6] meta-selftest: provide a recipe for zvariant
Date: Fri, 31 Mar 2023 14:26:49 +0100	[thread overview]
Message-ID: <c007fc29d99e2116d2fd53a9338d329559723102.camel@linuxfoundation.org> (raw)
In-Reply-To: <CANNYZj8syo4bNVz3OzwS-tbfPm-UPjFyZYy2cfSznqMLH5wGhg@mail.gmail.com>

On Fri, 2023-03-31 at 15:21 +0200, Alexander Kanavin wrote:
> On Fri, 31 Mar 2023 at 14:27, Richard Purdie
> <richard.purdie@linuxfoundation.org> wrote:
> 
> > We do have other reproducibility issues in rust and had to exclude some
> > packages from the test because of this. We do want to resolve those
> > issues though.
> 
> But aren't recipes in meta-selftest exempted from reproducibility requirement?

I suspect we can put an EXCLUDE_FROM_WORLD = "1" in there and then this
will "go away" but shouldn't our output be reproducible and isn't this
therefore actually a good test?

Cheers,

Richard


  reply	other threads:[~2023-03-31 13:26 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-31  5:45 [PATCH V6 0/6] frederic.martinsons
2023-03-31  5:45 ` [PATCH V6 1/6] cargo_common.bbclass: Support local github repos frederic.martinsons
2023-03-31  5:45 ` [PATCH V6 2/6] cargo_common.bbclass: add support of user in url for patch frederic.martinsons
2023-03-31  5:45 ` [PATCH V6 3/6] devtool: add support for multiple git url inside a cargo based recipe frederic.martinsons
2023-03-31  5:45 ` [PATCH V6 4/6] patch: support of git patches when the source uri contained subpath parameter frederic.martinsons
2023-03-31  5:45 ` [PATCH V6 5/6] meta-selftest: provide a recipe for zvariant frederic.martinsons
2023-03-31 12:27   ` [OE-core] " Richard Purdie
2023-03-31 13:21     ` Alexander Kanavin
2023-03-31 13:26       ` Richard Purdie [this message]
2023-03-31 13:50         ` Alexander Kanavin
2023-03-31 15:01           ` Frédéric Martinsons
2023-03-31 15:55             ` Alexander Kanavin
2023-03-31 16:11               ` Frédéric Martinsons
2023-03-31 16:34             ` Richard Purdie
2023-04-01  9:32               ` Frédéric Martinsons
2023-04-01 13:56                 ` Richard Purdie
2023-03-31  5:45 ` [PATCH V6 6/6] cargo-update-recipe-crates: force name overrides frederic.martinsons

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=c007fc29d99e2116d2fd53a9338d329559723102.camel@linuxfoundation.org \
    --to=richard.purdie@linuxfoundation.org \
    --cc=alex.kanavin@gmail.com \
    --cc=alex.kiernan@gmail.com \
    --cc=frederic.martinsons@gmail.com \
    --cc=openembedded-core@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox