openembedded-devel.lists.openembedded.org archive mirror
 help / color / mirror / Atom feed
From: Martin Jansa <martin.jansa@gmail.com>
To: Khem Raj <raj.khem@gmail.com>
Cc: koansoftware@gmail.com,
	Marco Cavallini <m.cavallini@koansoftware.com>,
	openembeded-devel <openembedded-devel@lists.openembedded.org>
Subject: Re: [oe] [meta-networking][PATCH v2] bluepy_git.bb: Added recipe for BluePy Python interface to Bluetooth LE on Linux (v2)
Date: Wed, 20 Oct 2021 19:02:16 +0200	[thread overview]
Message-ID: <CA+chaQft+XOybLLsvm5T130VwVn2fsXT-_a+eVh1F08tnAECCw@mail.gmail.com> (raw)
In-Reply-To: <CAMKF1soX6d8g6fyxB4NNhfmEECfbqE0+r2Xixn_Yxi2PmNQGuA@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1900 bytes --]

FWIW: I'm seeing the same error now.

Marco: is the user you're building under having UID 1000? Try under
different UID to reproduce this.

On Wed, Oct 20, 2021 at 4:11 PM Khem Raj <raj.khem@gmail.com> wrote:

>
>
> On Wed, Oct 20, 2021 at 5:07 AM Marco <koansoftware@gmail.com> wrote:
>
>> On 20/10/21 13:45, Khem Raj wrote:
>> > fails during install now on musl/x86 arm/glibc
>> >
>> > https://errors.yoctoproject.org/Errors/Details/613446/
>> > https://errors.yoctoproject.org/Errors/Details/613456/
>> >
>>
>> Hi Khem,
>> I diligently followed the instructions on the site
>> https://www.openembedded.org/wiki/How_to_submit_a_patch_to_OpenEmbedded
>>
>> To correct the errors you reported to me previously, I installed the
>> 'master' version of Poky + Openembedded and recompiled everything
>> without errors and I re-sent the v2 patch.
>>
>> At this point I no longer know what the requirements are for submitting
>> a patch.
>> Do you need to pass any series of tests?
>> Which one?
>> How do I reproduce them locally?
>
>
> We have few Jenkins nodes where world builds are run and it takes quite a
> bit for those to finish
>
> I also have a Comcast internal node and one
>
> Then we do have a job at yocto auto builder too and it’s failing on some
> of them but not all
>
> Eg it’s also failing on yocto ab which builds for qemux86-64/glibc
>
>
>
>>
>> Thank you
>> --
>> Marco
>>
>
> -=-=-=-=-=-=-=-=-=-=-=-
> Links: You receive all messages sent to this group.
> View/Reply Online (#93482):
> https://lists.openembedded.org/g/openembedded-devel/message/93482
> Mute This Topic: https://lists.openembedded.org/mt/86439385/3617156
> Group Owner: openembedded-devel+owner@lists.openembedded.org
> Unsubscribe: https://lists.openembedded.org/g/openembedded-devel/unsub [
> Martin.Jansa@gmail.com]
> -=-=-=-=-=-=-=-=-=-=-=-
>
>

[-- Attachment #2: Type: text/html, Size: 3694 bytes --]

  reply	other threads:[~2021-10-20 17:02 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-19 13:19 [meta-networking][PATCH v2] bluepy_git.bb: Added recipe for BluePy Python interface to Bluetooth LE on Linux (v2) Marco Cavallini
2021-10-20 11:45 ` [oe] " Khem Raj
2021-10-20 12:07   ` Marco
2021-10-20 14:10     ` Khem Raj
2021-10-20 17:02       ` Martin Jansa [this message]
     [not found]       ` <16AFCBDEF9895FF9.31449@lists.openembedded.org>
2021-10-20 17:05         ` Martin Jansa
2021-10-20 17:07           ` Martin Jansa
2021-10-20 17:23             ` Khem Raj

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=CA+chaQft+XOybLLsvm5T130VwVn2fsXT-_a+eVh1F08tnAECCw@mail.gmail.com \
    --to=martin.jansa@gmail.com \
    --cc=koansoftware@gmail.com \
    --cc=m.cavallini@koansoftware.com \
    --cc=openembedded-devel@lists.openembedded.org \
    --cc=raj.khem@gmail.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;
as well as URLs for NNTP newsgroup(s).