From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: openembedded-architecture
<openembedded-architecture@lists.openembedded.org>,
bitbake-devel <bitbake-devel@lists.openembedded.org>
Subject: Re: Python 3 for Bitbake
Date: Sun, 22 May 2016 08:58:57 +0100 [thread overview]
Message-ID: <1463903937.9570.12.camel@linuxfoundation.org> (raw)
In-Reply-To: <1462826340.21831.151.camel@linuxfoundation.org>
Where are we at?
The python3 branches in bitbake, OE-Core and poky are looking fairly
good from a build perspective. The run overnight on the autobuilder had
the following issues:
ppc specific sanity test failure:
https://autobuilder.yoctoproject.org/main/builders/nightly-ppc/builds/7
99
https:
//autobuilder.yoctoproject.org/main/builders/nightly-ppc-lsb/builds/770
weird intermittent multilib failure:
https:/
/autobuilder.yoctoproject.org/main/builders/nightly-multilib/builds/795
4 test failures in oe-selftest:
https://autobuilder.yoctoproject.org/main/builders/nightly-oe-selftest/
builds/517
which given the scope of the changes isn't so bad.
I have merged some of the pieces which are 2.7 safe into master. We've
had some issues with buildtools-tarball and the python3 it contains but
I think we're nearly there in resolving that. I don't believe toaster i
quite there yet either but getting close.
The question is therefore how much more work to do before those
branches are ready for merging? They do need a little more cosmetic
cleanup but I think things are very close.
I would like to get them merged sooner than later since they are quite
a nightmare to maintain.
Cheers,
Richard
prev parent reply other threads:[~2016-05-22 7:59 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-04 8:56 Python 3 for Bitbake Richard Purdie
2016-05-04 21:19 ` Christopher Larson
2016-05-04 21:29 ` [Openembedded-architecture] " Mark Hatle
2016-05-04 21:34 ` Burton, Ross
2016-05-05 5:10 ` Tim Orling
2016-05-06 8:40 ` Burton, Ross
2016-05-05 12:13 ` Philip Balister
2016-05-05 15:13 ` Mark Hatle
2016-05-05 15:18 ` Christopher Larson
2016-05-05 15:50 ` Otavio Salvador
2016-05-05 17:29 ` Jan-Simon Möller
2016-05-05 17:47 ` Otavio Salvador
2016-05-05 17:50 ` akuster
2016-05-09 20:39 ` Richard Purdie
2016-05-22 7:58 ` Richard Purdie [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=1463903937.9570.12.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=bitbake-devel@lists.openembedded.org \
--cc=openembedded-architecture@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