From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: "joshua.lock" <joshua.lock@collabora.co.uk>,
openembedded-core <openembedded-core@lists.openembedded.org>
Subject: fido status
Date: Sun, 28 Jun 2015 11:14:40 +0100 [thread overview]
Message-ID: <1435486480.10583.85.camel@linuxfoundation.org> (raw)
I just wanted to let people know what is going on with Fido.
Joshua has had a branch in testing for a while. The autobuilder gave
mixed feedback for it. Partly, there was a problem since we'd introduced
a new autobuilder (Fedora 22) and this introduced some problems with
subversion-native and gcc5. Partly there were also networking issues on
the autobuilders related to runqemu.
Thanks to some help from Michael, we've tracked down and sorted the
networking issue (we hope!). I therefore took the decision to merge
Joshua's fido-next branch myself, now, with the addition of the
subversion fixes to the fido branch.
I've triggered another build which is underway at the moment and I'm
confident the result should be reasonable. What I am expecting is
failures for oe-selftest and for nightly-aarm64 and nightly-mips64.
There are fixes just merged into master which resolve issues in all
three areas, I'm hoping we can queue up a fido-next with those in and
get fido building green quickly. Those issues are less of an issue given
we know what the issues are and they are testing issues, not 'real'
bugs.
Cheers,
Richard
next reply other threads:[~2015-06-28 10:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-28 10:14 Richard Purdie [this message]
2015-06-29 10:19 ` fido status Joshua Lock
2015-06-29 20:25 ` Andre McCurdy
2015-06-30 15:07 ` Joshua Lock
2015-06-30 19:06 ` Andre McCurdy
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=1435486480.10583.85.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=joshua.lock@collabora.co.uk \
--cc=openembedded-core@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