From: Martin Jansa <martin.jansa@gmail.com>
To: Richard Purdie <richard.purdie@linuxfoundation.org>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH][RESEND 0/6] YOCTO #12937 - Consistent naming scheme for deployed artifacts
Date: Thu, 17 Oct 2019 19:50:33 +0200 [thread overview]
Message-ID: <20191017175033.GA1499@jama> (raw)
In-Reply-To: <ffe6a140ee4cf36bb7ce8fd2f460bcd7e0a86f05.camel@linuxfoundation.org>
[-- Attachment #1: Type: text/plain, Size: 1754 bytes --]
On Sun, Oct 13, 2019 at 02:44:30PM +0100, Richard Purdie wrote:
> On Sat, 2019-10-12 at 13:03 +0000, Martin Jansa wrote:
> > The following changes since commit
> > 59938780e7e776d87146002ea939b185f8704408:
> >
> > build-appliance-image: Update to master head revision (2019-10-09
> > 22:28:44 +0100)
> >
> > are available in the Git repository at:
> >
> > git://git.openembedded.org/openembedded-core-contrib
> > jansa/artifacts
> >
> > http://cgit.openembedded.org/openembedded-core-contrib/log/?h=jansa/artifacts
> >
> > Martin Jansa (6):
> > image-artifact-names: introduce new bbclass and move some variables
> > into it
> > bitbake.conf, kernel*.bbclass: include IMAGE_VERSION_SUFFIX only in
> > the _LINK_NAME variables and change it to hard link
> > kernel-artifact-names.bbclass: use PR instead of PKGR in
> > KERNEL_ARTIFACT_NAME
> > kernel.bbclass: imageType without {}
> > kernel.bbclass: drop unnecessary package_get_auto_pr for do_install
> > *-artifact-names: include version only in the artifact links
>
> I tried this on the autobuilder and it seems to break several things:
>
> https://autobuilder.yoctoproject.org/typhoon/#/builders/83/builds/423
>
> Looks like do_bootimg fails, as well as the testimage oeqa code being
> unable to find the testdata json files.
I've successfully built this with nodistro and qemux86-64 before sending
the pull request, now I've built core-image-sato-sdk-ptest with poky and
genericx86-64 as well, so I'm still trying to figure out what
autobuilder does differently to break it like this.
> There could well be further issues beyond that but its hard to tell.
--
Martin 'JaMa' Jansa jabber: Martin.Jansa@gmail.com
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 201 bytes --]
prev parent reply other threads:[~2019-10-17 17:50 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-12 13:03 [PATCH][RESEND 0/6] YOCTO #12937 - Consistent naming scheme for deployed artifacts Martin Jansa
2019-10-12 13:03 ` [PATCH][RESEND 1/6] image-artifact-names: introduce new bbclass and move some variables into it Martin Jansa
2019-10-12 13:03 ` [PATCH][RESEND 2/6] bitbake.conf, kernel*.bbclass: include IMAGE_VERSION_SUFFIX only in the _LINK_NAME variables and change it to hard link Martin Jansa
2019-10-12 13:03 ` [PATCH][RESEND 3/6] kernel-artifact-names.bbclass: use PR instead of PKGR in KERNEL_ARTIFACT_NAME Martin Jansa
2019-10-12 13:03 ` [PATCH][RESEND 4/6] kernel.bbclass: imageType without {} Martin Jansa
2019-10-12 13:03 ` [PATCH][RESEND 5/6] kernel.bbclass: drop unnecessary package_get_auto_pr for do_install Martin Jansa
2019-10-12 13:03 ` [PATCH][RESEND 6/6] *-artifact-names: include version only in the artifact links Martin Jansa
2019-10-12 13:32 ` ✗ patchtest: failure for YOCTO #12937 - Consistent naming scheme for deployed artifacts (rev3) Patchwork
2019-10-13 13:44 ` [PATCH][RESEND 0/6] YOCTO #12937 - Consistent naming scheme for deployed artifacts Richard Purdie
2019-10-17 17:50 ` Martin Jansa [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=20191017175033.GA1499@jama \
--to=martin.jansa@gmail.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=richard.purdie@linuxfoundation.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