* Weekend build status (master, fido, dizzy and -next)
@ 2015-07-26 16:14 Richard Purdie
2015-07-26 19:54 ` Flanagan, Elizabeth
2015-07-26 20:11 ` akuster808
0 siblings, 2 replies; 6+ messages in thread
From: Richard Purdie @ 2015-07-26 16:14 UTC (permalink / raw)
To: openembedded-core; +Cc: Witt, Randy E
Over the weekend I've tried to establish where we're at with the various
branches. I've run builds of master, fido and dizzy. I have fixed
various things:
* dizzy gcc5 backports
* mysterious updated-rc.d license file missing failure
* linux-yocto 4.1 perf issues
Despite these, sadly the builds were not very successful :(.
Master - Last build showed 4 failures:
======================================
https://autobuilder.yoctoproject.org/main/builders/build-appliance/builds/402/steps/BuildImages/logs/stdio
nativesdk-update-rc.d missing, fix pushed
https://autobuilder.yoctoproject.org/main/builders/nightly-intel-gpl/builds/400/steps/BuildImages/logs/stdio
https://autobuilder.yoctoproject.org/main/builders/nightly-intel-gpl/builds/400/steps/BuildImages_1/logs/stdio
meta-intel linux-yocto issue (fix pending merging)
nativesdk-update-rc.d missing, fix pushed
https://autobuilder.yoctoproject.org/main/builders/nightly-mips/builds/413/steps/Running%20Sanity%20Tests/logs/stdio
mips sanity test failure, unknown cause
https://autobuilder.yoctoproject.org/main/builders/nightly-oe-selftest/builds/96/steps/Running%20oe-selftest/logs/stdio
3 failures from runqemu issues (Paul working on this)
2 failures from meta-intel linux-yocto issues (fix pending merging)
Fido - Last build showed 5 failures:
====================================
https://autobuilder.yoctoproject.org/main/builders/nightly-arm/builds/409/steps/Running%20Sanity%20Tests/logs/stdio
qemuarm kernel panic during sanity tests
https://autobuilder.yoctoproject.org/main/builders/nightly-deb/builds/394/steps/BuildImages/logs/stdio
https://autobuilder.yoctoproject.org/main/builders/nightly-deb-non-deb/builds/68/steps/BuildImages/logs/stdio
looks like http://git.yoctoproject.org/cgit.cgi/poky/commit/?id=ba07a69f3dc8fb798e372130bf665d059fed9d42, backport needed?
https://autobuilder.yoctoproject.org/main/builders/nightly-oe-selftest/builds/94/steps/Running%20oe-selftest/logs/stdio
"Only one copy of bitbake should be run against a build directory" -
Bitbake shutdown race. Fix in master but risky backport, torn on this.
https://autobuilder.yoctoproject.org/main/builders/nightly-qa-systemd/builds/405/steps/Running%20Sanity%20Tests/logs/stdio
xorg/vnc systemd issue - Ross has open bug for master
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
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?
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?
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?)
grub-efi gcc5 issue:
http://errors.yoctoproject.org/Errors/Details/13781/
[build is still ongoing so this is not a complete list]
So all things considered we're not in a good way for the point releases
or M2 :(.
With regard to master-next, my experimental SDK toolchain fixes are
causing issues on armeabi and x32. Whenever I add in Chris' recipetool
changes, the selftest gives odd results too :(. Build is also ongoing.
Cheers,
Richard
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: Weekend build status (master, fido, dizzy and -next)
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
1 sibling, 0 replies; 6+ messages in thread
From: Flanagan, Elizabeth @ 2015-07-26 19:54 UTC (permalink / raw)
To: Richard Purdie; +Cc: Witt, Randy E, openembedded-core
On 26 July 2015 at 17:14, Richard Purdie
<richard.purdie@linuxfoundation.org> wrote:
> Over the weekend I've tried to establish where we're at with the various
> branches. I've run builds of master, fido and dizzy. I have fixed
> various things:
>
> * dizzy gcc5 backports
> * mysterious updated-rc.d license file missing failure
> * linux-yocto 4.1 perf issues
>
> Despite these, sadly the builds were not very successful :(.
>
> Master - Last build showed 4 failures:
> ======================================
>
> https://autobuilder.yoctoproject.org/main/builders/build-appliance/builds/402/steps/BuildImages/logs/stdio
> nativesdk-update-rc.d missing, fix pushed
>
> https://autobuilder.yoctoproject.org/main/builders/nightly-intel-gpl/builds/400/steps/BuildImages/logs/stdio
> https://autobuilder.yoctoproject.org/main/builders/nightly-intel-gpl/builds/400/steps/BuildImages_1/logs/stdio
> meta-intel linux-yocto issue (fix pending merging)
> nativesdk-update-rc.d missing, fix pushed
>
> https://autobuilder.yoctoproject.org/main/builders/nightly-mips/builds/413/steps/Running%20Sanity%20Tests/logs/stdio
> mips sanity test failure, unknown cause
>
> https://autobuilder.yoctoproject.org/main/builders/nightly-oe-selftest/builds/96/steps/Running%20oe-selftest/logs/stdio
> 3 failures from runqemu issues (Paul working on this)
> 2 failures from meta-intel linux-yocto issues (fix pending merging)
>
> Fido - Last build showed 5 failures:
> ====================================
>
> https://autobuilder.yoctoproject.org/main/builders/nightly-arm/builds/409/steps/Running%20Sanity%20Tests/logs/stdio
> qemuarm kernel panic during sanity tests
>
> https://autobuilder.yoctoproject.org/main/builders/nightly-deb/builds/394/steps/BuildImages/logs/stdio
> https://autobuilder.yoctoproject.org/main/builders/nightly-deb-non-deb/builds/68/steps/BuildImages/logs/stdio
> looks like http://git.yoctoproject.org/cgit.cgi/poky/commit/?id=ba07a69f3dc8fb798e372130bf665d059fed9d42, backport needed?
>
> https://autobuilder.yoctoproject.org/main/builders/nightly-oe-selftest/builds/94/steps/Running%20oe-selftest/logs/stdio
> "Only one copy of bitbake should be run against a build directory" -
> Bitbake shutdown race. Fix in master but risky backport, torn on this.
>
> https://autobuilder.yoctoproject.org/main/builders/nightly-qa-systemd/builds/405/steps/Running%20Sanity%20Tests/logs/stdio
> xorg/vnc systemd issue - Ross has open bug for master
>
> 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
>
> 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?
>
This shows that we have GPLv3+ within the license.manifest which is a
problem. I'll take a look at this tomorrow as it's concerning that
GPLv3 packages are getting in.
LICENSE: GPLv3+ BSD-2-Clause
LICENSE: GPLv2 LGPLv3
LICENSE: GPLv3+
> 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?
>
No, I don't believe so. I'll toss a skip patch into the AB to make
sure we don't hit this again.
> 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?)
Same, don't believe this is in dizzy. Just fido and master.
>
> grub-efi gcc5 issue:
> http://errors.yoctoproject.org/Errors/Details/13781/
>
> [build is still ongoing so this is not a complete list]
>
> So all things considered we're not in a good way for the point releases
> or M2 :(.
>
> With regard to master-next, my experimental SDK toolchain fixes are
> causing issues on armeabi and x32. Whenever I add in Chris' recipetool
> changes, the selftest gives odd results too :(. Build is also ongoing.
>
> Cheers,
>
> Richard
>
>
-b
--
Elizabeth Flanagan
Yocto Project
Build and Release
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: Weekend build status (master, fido, dizzy and -next)
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
1 sibling, 2 replies; 6+ messages in thread
From: akuster808 @ 2015-07-26 20:11 UTC (permalink / raw)
To: Richard Purdie, openembedded-core; +Cc: Witt, Randy E
On 07/26/2015 09:14 AM, Richard Purdie wrote:
> Over the weekend I've tried to establish where we're at with the various
> branches. I've run builds of master, fido and dizzy. I have fixed
> various things:
>
> * dizzy gcc5 backports
> * mysterious updated-rc.d license file missing failure
> * linux-yocto 4.1 perf issues
>
> Despite these, sadly the builds were not very successful :(.
>
> Master - Last build showed 4 failures:
> ======================================
>
> https://autobuilder.yoctoproject.org/main/builders/build-appliance/builds/402/steps/BuildImages/logs/stdio
> nativesdk-update-rc.d missing, fix pushed
>
> https://autobuilder.yoctoproject.org/main/builders/nightly-intel-gpl/builds/400/steps/BuildImages/logs/stdio
> https://autobuilder.yoctoproject.org/main/builders/nightly-intel-gpl/builds/400/steps/BuildImages_1/logs/stdio
> meta-intel linux-yocto issue (fix pending merging)
> nativesdk-update-rc.d missing, fix pushed
>
> https://autobuilder.yoctoproject.org/main/builders/nightly-mips/builds/413/steps/Running%20Sanity%20Tests/logs/stdio
> mips sanity test failure, unknown cause
>
> https://autobuilder.yoctoproject.org/main/builders/nightly-oe-selftest/builds/96/steps/Running%20oe-selftest/logs/stdio
> 3 failures from runqemu issues (Paul working on this)
> 2 failures from meta-intel linux-yocto issues (fix pending merging)
>
> Fido - Last build showed 5 failures:
> ====================================
>
> https://autobuilder.yoctoproject.org/main/builders/nightly-arm/builds/409/steps/Running%20Sanity%20Tests/logs/stdio
> qemuarm kernel panic during sanity tests
>
> https://autobuilder.yoctoproject.org/main/builders/nightly-deb/builds/394/steps/BuildImages/logs/stdio
> https://autobuilder.yoctoproject.org/main/builders/nightly-deb-non-deb/builds/68/steps/BuildImages/logs/stdio
> looks like http://git.yoctoproject.org/cgit.cgi/poky/commit/?id=ba07a69f3dc8fb798e372130bf665d059fed9d42, backport needed?
>
> https://autobuilder.yoctoproject.org/main/builders/nightly-oe-selftest/builds/94/steps/Running%20oe-selftest/logs/stdio
> "Only one copy of bitbake should be run against a build directory" -
> Bitbake shutdown race. Fix in master but risky backport, torn on this.
>
> https://autobuilder.yoctoproject.org/main/builders/nightly-qa-systemd/builds/405/steps/Running%20Sanity%20Tests/logs/stdio
> xorg/vnc systemd issue - Ross has open bug for master
>
> 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+.
>
> 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.
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?
>
> 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.
- Armin
>
> grub-efi gcc5 issue:
> http://errors.yoctoproject.org/Errors/Details/13781/
>
> [build is still ongoing so this is not a complete list]
>
> So all things considered we're not in a good way for the point releases
> or M2 :(.
>
> With regard to master-next, my experimental SDK toolchain fixes are
> causing issues on armeabi and x32. Whenever I add in Chris' recipetool
> changes, the selftest gives odd results too :(. Build is also ongoing.
>
> Cheers,
>
> Richard
>
>
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: Weekend build status (master, fido, dizzy and -next)
2015-07-26 20:11 ` akuster808
@ 2015-07-26 20:42 ` Flanagan, Elizabeth
2015-07-26 21:08 ` Richard Purdie
1 sibling, 0 replies; 6+ messages in thread
From: Flanagan, Elizabeth @ 2015-07-26 20:42 UTC (permalink / raw)
To: akuster808; +Cc: Witt, Randy E, openembedded-core
On 26 July 2015 at 21:11, akuster808 <akuster808@gmail.com> wrote:
>
>
> On 07/26/2015 09:14 AM, Richard Purdie wrote:
>>
>> Over the weekend I've tried to establish where we're at with the various
>> branches. I've run builds of master, fido and dizzy. I have fixed
>> various things:
>>
>> * dizzy gcc5 backports
>> * mysterious updated-rc.d license file missing failure
>> * linux-yocto 4.1 perf issues
>>
>> Despite these, sadly the builds were not very successful :(.
>>
>> Master - Last build showed 4 failures:
>> ======================================
>>
>>
>> https://autobuilder.yoctoproject.org/main/builders/build-appliance/builds/402/steps/BuildImages/logs/stdio
>> nativesdk-update-rc.d missing, fix pushed
>>
>>
>> https://autobuilder.yoctoproject.org/main/builders/nightly-intel-gpl/builds/400/steps/BuildImages/logs/stdio
>>
>> https://autobuilder.yoctoproject.org/main/builders/nightly-intel-gpl/builds/400/steps/BuildImages_1/logs/stdio
>> meta-intel linux-yocto issue (fix pending merging)
>> nativesdk-update-rc.d missing, fix pushed
>>
>>
>> https://autobuilder.yoctoproject.org/main/builders/nightly-mips/builds/413/steps/Running%20Sanity%20Tests/logs/stdio
>> mips sanity test failure, unknown cause
>>
>>
>> https://autobuilder.yoctoproject.org/main/builders/nightly-oe-selftest/builds/96/steps/Running%20oe-selftest/logs/stdio
>> 3 failures from runqemu issues (Paul working on this)
>> 2 failures from meta-intel linux-yocto issues (fix pending merging)
>>
>> Fido - Last build showed 5 failures:
>> ====================================
>>
>>
>> https://autobuilder.yoctoproject.org/main/builders/nightly-arm/builds/409/steps/Running%20Sanity%20Tests/logs/stdio
>> qemuarm kernel panic during sanity tests
>>
>>
>> https://autobuilder.yoctoproject.org/main/builders/nightly-deb/builds/394/steps/BuildImages/logs/stdio
>>
>> https://autobuilder.yoctoproject.org/main/builders/nightly-deb-non-deb/builds/68/steps/BuildImages/logs/stdio
>> looks like
>> http://git.yoctoproject.org/cgit.cgi/poky/commit/?id=ba07a69f3dc8fb798e372130bf665d059fed9d42,
>> backport needed?
>>
>>
>> https://autobuilder.yoctoproject.org/main/builders/nightly-oe-selftest/builds/94/steps/Running%20oe-selftest/logs/stdio
>> "Only one copy of bitbake should be run against a build directory" -
>> Bitbake shutdown race. Fix in master but risky backport, torn on this.
>>
>>
>> https://autobuilder.yoctoproject.org/main/builders/nightly-qa-systemd/builds/405/steps/Running%20Sanity%20Tests/logs/stdio
>> xorg/vnc systemd issue - Ross has open bug for master
>>
>> 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+.
>
>
>>
>>
>> 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.
>
No, the check was not run. My guess is that it was broken in 1.7.2.
> 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?
We use the buildtools tarball on the builders. That is probably where
that is coming from.
>
>>
>>
>> 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.
>
> - Armin
>>
>>
>> grub-efi gcc5 issue:
>> http://errors.yoctoproject.org/Errors/Details/13781/
>>
>> [build is still ongoing so this is not a complete list]
>>
>> So all things considered we're not in a good way for the point releases
>> or M2 :(.
>>
>> With regard to master-next, my experimental SDK toolchain fixes are
>> causing issues on armeabi and x32. Whenever I add in Chris' recipetool
>> changes, the selftest gives odd results too :(. Build is also ongoing.
>>
>> Cheers,
>>
>> Richard
>>
>>
>
--
Elizabeth Flanagan
Yocto Project
Build and Release
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: Weekend build status (master, fido, dizzy and -next)
2015-07-26 20:11 ` akuster808
2015-07-26 20:42 ` Flanagan, Elizabeth
@ 2015-07-26 21:08 ` Richard Purdie
2015-07-26 22:56 ` Flanagan, Elizabeth
1 sibling, 1 reply; 6+ messages in thread
From: Richard Purdie @ 2015-07-26 21:08 UTC (permalink / raw)
To: akuster808; +Cc: Witt, Randy E, openembedded-core
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
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: Weekend build status (master, fido, dizzy and -next)
2015-07-26 21:08 ` Richard Purdie
@ 2015-07-26 22:56 ` Flanagan, Elizabeth
0 siblings, 0 replies; 6+ messages in thread
From: Flanagan, Elizabeth @ 2015-07-26 22:56 UTC (permalink / raw)
To: Richard Purdie; +Cc: Witt, Randy E, openembedded-core
On 26 July 2015 at 22:08, Richard Purdie
<richard.purdie@linuxfoundation.org> wrote:
> 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?
The nightly-non-gpl3 target was run for 1.7.2. However the
"CheckForGPLv3" build step is new and is there to catch exactly this.
So something is wrong with the non-gplv3 builds for 1.7.x that this
caught.
-b
>
>> 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
>
--
Elizabeth Flanagan
Yocto Project
Build and Release
^ permalink raw reply [flat|nested] 6+ messages in thread
end of thread, other threads:[~2015-07-26 22:56 UTC | newest]
Thread overview: 6+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
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
2015-07-26 22:56 ` Flanagan, Elizabeth
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.