From: Stefan Herbrechtsmeier <stefan.herbrechtsmeier-oss@weidmueller.com>
To: Luca Ceresoli <luca.ceresoli@bootlin.com>,
Lukas Funke <lukas.funke@weidmueller.com>
Cc: openembedded-core@lists.openembedded.org,
Stefan Herbrechtsmeier <stefan.herbrechtsmeier@weidmueller.com>
Subject: Re: [OE-core] [PATCH 1/5] recipetool-create: add ensure_native_cmd function
Date: Wed, 11 May 2022 08:54:37 +0200 [thread overview]
Message-ID: <b5aee412-5db4-9aac-4422-79e667bfc773@weidmueller.com> (raw)
In-Reply-To: <20220509234659.74b95a2c@melee>
Hi Luca,
Lukas will check the logs and fix the problem.
Regards
Stefan
Am 09.05.2022 um 23:46 schrieb Luca Ceresoli:
> Hello Stefan,
>
> Il giorno Fri, 6 May 2022 08:59:13 +0200
> "Stefan Herbrechtsmeier" <stefan.herbrechtsmeier-oss@weidmueller.com>
> ha scritto:
>
>> From: Lukas Funke <lukas.funke@weidmueller.com>
>>
>> Signed-off-by: Lukas Funke <lukas.funke@weidmueller.com>
>> Signed-off-by: Stefan Herbrechtsmeier
>> <stefan.herbrechtsmeier@weidmueller.com>
>
> Testing builds with your series trigger many build failures related to
> recipetool. Can you check these logs?
>
> https://autobuilder.yoctoproject.org/typhoon/#/builders/79/builds/3557/steps/15/logs/stdio
> https://autobuilder.yoctoproject.org/typhoon/#/builders/80/builds/3506/steps/14/logs/stdio
> https://autobuilder.yoctoproject.org/typhoon/#/builders/86/builds/3527/steps/14/logs/stdio
> https://autobuilder.yoctoproject.org/typhoon/#/builders/87/builds/3566/steps/14/logs/stdio
>
>
>
prev parent reply other threads:[~2022-05-11 6:55 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-06 6:59 [PATCH 1/5] recipetool-create: add ensure_native_cmd function Stefan Herbrechtsmeier
2022-05-06 6:59 ` [PATCH 2/5] create_npm: reuse ensure_native_cmd from create.py Stefan Herbrechtsmeier
2022-05-06 6:59 ` [PATCH 3/5] poky-meta: add go vendor class for offline builds Stefan Herbrechtsmeier
2022-05-11 20:42 ` [OE-core] " Mark Asselstine
2022-05-06 6:59 ` [PATCH 4/5] recipetool: add go recipe generator Stefan Herbrechtsmeier
2022-05-06 7:15 ` [OE-core] " Alexander Kanavin
2022-05-11 20:37 ` Mark Asselstine
2022-05-06 6:59 ` [PATCH 5/5] oe-selftest: add go recipe create selftest Stefan Herbrechtsmeier
2022-05-06 7:16 ` [OE-core] " Alexander Kanavin
2022-05-11 20:08 ` Mark Asselstine
2022-05-06 7:09 ` [OE-core] [PATCH 1/5] recipetool-create: add ensure_native_cmd function Alexander Kanavin
2022-05-11 19:45 ` Mark Asselstine
2022-05-11 19:47 ` Mark Asselstine
2022-05-09 21:46 ` Luca Ceresoli
2022-05-11 6:54 ` Stefan Herbrechtsmeier [this message]
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=b5aee412-5db4-9aac-4422-79e667bfc773@weidmueller.com \
--to=stefan.herbrechtsmeier-oss@weidmueller.com \
--cc=luca.ceresoli@bootlin.com \
--cc=lukas.funke@weidmueller.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=stefan.herbrechtsmeier@weidmueller.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