From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: akuster808 <akuster808@gmail.com>
Cc: "Witt, Randy E" <randy.e.witt@intel.com>,
openembedded-core <openembedded-core@lists.openembedded.org>
Subject: Re: Weekend build status (master, fido, dizzy and -next)
Date: Sun, 26 Jul 2015 22:08:38 +0100 [thread overview]
Message-ID: <1437944918.821.202.camel@linuxfoundation.org> (raw)
In-Reply-To: <55B53F00.8050902@gmail.com>
On Sun, 2015-07-26 at 13:11 -0700, akuster808 wrote:
> On 07/26/2015 09:14 AM, Richard Purdie wrote:
> > Dizzy - Last Build showed ? failures:
> > =====================================
> >
> > Managed to push most gcc5 fixes to the branch which has things building
> > much better than the first time.
> >
> > https://autobuilder.yoctoproject.org/main/builders/nightly-oe-selftest/builds/97/steps/Running%20oe-selftest/logs/stdio
> > two different selftest sanity failures
>
> Why does the log show 1.8+snapshot? I would have expected 1.7+.
That autobuilder appears to be running a buildtools-tarball which was
built using 1.8 and installed in /opt/xxx. The build does appear to be a
1.7 build and those paths are safe to ignore.
> > https://autobuilder.yoctoproject.org/main/builders/nightly-qa-systemd/builds/407/steps/Running%20Sanity%20Tests/logs/stdio
> > Systemd login prompt failure issue (Ross also has open bug for this in
> > master)
> >
> > https://autobuilder.yoctoproject.org/main/builders/nightly-non-gpl3/builds/413/steps/CheckForGPLv3/logs/stdio
> > GPLv3 check failing?
>
> Was this run for 1.7.2 ? I don't see any license changes in the 1.7.3
> patches.
Beth?
> I am confused by the logs. It references
> "TERMINFO_DIRS=/opt/poky/1.8+snapshot" and other places is references
> 'master'. is this representative of Dizzy?
See above, same issue, its from buildtools-tarball the system is using.
> >
> > https://autobuilder.yoctoproject.org/main/builders/nightly-mips64/builds/60/steps/Running%20Sanity%20Tests/logs/stdio
> > mips64 sanity test failed - do we support this on dizzy?
>
> Don't think so. It was not tested in the previews point releases either.
>
> >
> > https://autobuilder.yoctoproject.org/main/builders/nightly-arm64/builds/68
> > arm64 build failed - do we support this on dizzy? (machine doesn't exist
> > so no?)
>
> Arm64 is not support in Dizzy.
Agreed, Beth will disable these to make things look a little cleaner.
Which just leaves the other issues :/.
Cheers,
Richard
next prev parent reply other threads:[~2015-07-26 21:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-26 16:14 Weekend build status (master, fido, dizzy and -next) Richard Purdie
2015-07-26 19:54 ` Flanagan, Elizabeth
2015-07-26 20:11 ` akuster808
2015-07-26 20:42 ` Flanagan, Elizabeth
2015-07-26 21:08 ` Richard Purdie [this message]
2015-07-26 22:56 ` Flanagan, Elizabeth
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=1437944918.821.202.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=akuster808@gmail.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=randy.e.witt@intel.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