Weekend build status (master, fido, dizzy and -next)
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
Quoted 54 lines · Richard Purdie
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 issuesDespite 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 pushedhttps://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 pushedhttps://autobuilder.yoctoproject.org/main/builders/nightly-mips/builds/413/steps/Running%20Sanity%20Tests/logs/stdio
mips sanity test failure, unknown causehttps://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 testshttps://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 masterDizzy - 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
Quoted 7 lines
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+
Quoted 3 lines
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.
Quoted 3 lines
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.
Quoted 9 lines
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 :(.
Quoted 9 lines
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
Signature · 3 lines
Elizabeth Flanagan Yocto Project Build and Release
Quoted 45 lines · Richard Purdie
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 issuesDespite 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 pushedhttps://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 pushedhttps://autobuilder.yoctoproject.org/main/builders/nightly-mips/builds/413/steps/Running%20Sanity%20Tests/logs/stdio
mips sanity test failure, unknown causehttps://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 testshttps://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
Quoted 8 lines
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+.
Quoted 7 lines
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?
Quoted 3 lines
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.
Quoted 4 lines
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
Quoted 18 lines
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
Quoted 82 lines · On 26 July 2015 at 21:11, akuster808 <[email protected]> wrote:
Quoted 61 lines · Richard Purdie
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 issuesDespite 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 pushedhttps://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 pushedhttps://autobuilder.yoctoproject.org/main/builders/nightly-mips/builds/413/steps/Running%20Sanity%20Tests/logs/stdio
mips sanity test failure, unknown causehttps://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 testshttps://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 masterDizzy - Last Build showed ? failures:
=====================================Quoted 6 lines
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 failuresWhy does the log show 1.8+snapshot? I would have expected 1.7+.
Quoted 7 lines
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)
Quoted 7 lines
Quoted 2 lines
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.
Quoted 3 lines
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.
Quoted 38 lines
Quoted 5 lines
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.
Quoted 4 lines
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
Quoted 19 lines
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
Signature · 3 lines
Elizabeth Flanagan Yocto Project Build and Release
Quoted 11 lines · On Sun, 2015-07-26 at 13:11 -0700, akuster808 wrote:
Quoted 8 lines · Richard Purdie
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 failuresWhy 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.
Quoted 9 lines
Quoted 6 lines
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?
Quoted 3 lines
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.
Quoted 4 lines
Quoted 3 lines
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?
Quoted 8 lines
Don't think so. It was not tested in the previews point releases either.
Quoted 4 lines
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
Quoted 21 lines · Richard Purdie
Quoted 11 lines · On Sun, 2015-07-26 at 13:11 -0700, akuster808 wrote:
Quoted 8 lines · Richard Purdie
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 failuresWhy 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.Quoted 4 lines
Quoted 4 lines
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)
Quoted 7 lines
Quoted 5 lines
Quoted 2 lines
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
Quoted 27 lines
Quoted 4 lines
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.
Quoted 4 lines
Quoted 3 lines
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?Quoted 8 lines
Don't think so. It was not tested in the previews point releases either.
Quoted 4 lines
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
Signature · 3 lines
Elizabeth Flanagan Yocto Project Build and Release