On Thu, 2023-01-19 at 08:55 -0500, Bruce Ashfield wrote:
> On Thu, Jan 19, 2023 at 4:57 AM Richard Purdie
> <[email protected]> wrote:
> > 
> > Hi Anuj/Bruce/Jan-Simon/Scott,
> > 
> > Please see the links below. This patch, pending for master triggers a
> > few warnings in a few layers as there are a handful of patches with no
> > Upstream-Status present in them.
> > 
> > I know this kind of thing is annoying but it is probably worth starting
> > to give the wider community the hint that they should document this,
> > and if they do document it, it might remind them to try and submit them
> > too. You're not the target audience but as layers being tested on the
> > autobuilder you get to lead by example! :)
> > 
> > If anyone doesn't want to tweak things to fix this, we can disable the
> > warnings for that specific test but I would prefer not to, I think this
> > is the right thing to encourage. The numbers of issues are low and
> > easily avoided one way or another.
> 
> I'd prefer the upstream-status check to be disabled for meta-virtualization.
> 
> This isn't something that I'm strictly enforcing, and not something that I
> want to start strictly enforcing.

I understand and will see what I can do to change the configurations, I
was hoping to avoid that.

Just as a heads up, there is an open action for the TSC to discuss
which QA checks shouldn't be bypassed for compatible layer status.

Cheers,

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

Reply via email to