Status of release candidate: bernard-1.0rc1
Summary
=======
This weekend, we generated a release candidate for bernard based on the bernard branch of master at commit:e08dc5aaaeba61e332caab4a3df5750df6b49ac1
and for BSPs based on the bernard branch of meta-intel at commit:16f47f04a2baaeaf9b5a9b381fc7a3c7755d6ff6
Issues seen:
===========
Build Infrastructure issues:
----------------------------
- We had an issue with builder02 running out of disk space, so some of the build copying was done post-build. This did not effect the build and was dealt with manually after cleaning up the partition.
- There is an issue with how package-index is being run. I will need to sync up with Jessica to verify how this should be incorporated into the build.
- The sanity tests on builder02 failed because builder02 was unable to resolve "localhost". This has been corrected and the sanity tests re-run incrementally:
http://autobuilder.pokylinux.org:8010/builders/nightly-internal-sanity/builds/3
- The tarball generation buildstep is not branch aware. This will be fixed this week. In the meantime it was run manually.
Sanity Test Issues:
----------------------------
- zypper-search failed on qemux-x86_64 on poky-image-lsb and poky-image-sato
Build Issues:
----------------------------
- BSPs did not complete successfully. There were some issue in the actual build mostly centering around:
- Failing to do_kernel_checkout
- Unpack issues around svn://svn.o-hand.com/repos
- Beagleboard failed doing runstrip on uboot during do_populate_sysroot
Build statistic:
----------------------------
Using RP__'s machine as a baseline, our current build stats for poky-image-sato is:
real 109m52.400s
user 393m58.840s
sys 59m25.380s
Build statistics for nightly-external are available at:
http://autobuilder.pokylinux.org/nightly/20110226-1/buildstats/buildstats/
Open Defects:
----------------------------
As of right now we have:
76 total open defects targeted for 1.0
Critical: 0
High: 14
Medium: 53
Low: 7
Undetermined: 2
Thanks for all those who helped with this weekends RC generation, especially sgw and RP__
------------------
Elizabeth Flanagan
Yocto Project
Release Engineer
Elizabeth Flanagan wrote on 2011-02-28:
Quoted 14 lines
Summary
=======This weekend, we generated a release candidate for bernard based on the bernard branch of master at commit:
e08dc5aaaeba61e332caab4a3df5750df6b49ac1and for BSPs based on the bernard branch of meta-intel at commit:
16f47f04a2baaeaf9b5a9b381fc7a3c7755d6ff6Issues seen:
===========
Quoted 8 lines
Build Infrastructure issues:
----------------------------- We had an issue with builder02 running out of disk space, so some of the build copying was done post-build. This did not effect the build and was dealt with manually after cleaning up the partition.
- There is an issue with how package-index is being run. I will need to sync up with Jessica to verify how this should be incorporated into the build.
I think it'd better to run "bitbake package-index" after the "bitbake meta-toolchain-sdk", using the same configuration as meta-toolchain-sdk. It will generate repository index files under the directories relevant to meta-toolchain-sdk tarball generations in ${TMPDIR}/deploy/ipk.
Quoted 59 lines
- The sanity tests on builder02 failed because builder02 was unable to resolve "localhost". This has been corrected and the sanity tests re-run
incrementally:http://autobuilder.pokylinux.org:8010/builders/nightly-internal-sanity
/builds/3- The tarball generation buildstep is not branch aware. This will be fixed this week.
In the meantime it was run manually.Sanity Test Issues:
----------------------------- zypper-search failed on qemux-x86_64 on poky-image-lsb and poky-image-sato
Build Issues:
----------------------------- BSPs did not complete successfully. There were some issue in the actual build mostly centering around:
- Failing todo_kernel_checkout
- Unpack issues around svn://svn.o-hand.com/repos
- Beagleboard failed doing runstrip on uboot duringdo_populate_sysrootBuild statistic:
----------------------------Using RP__'s machine as a baseline, our current build stats for poky-image-sato is:
real 109m52.400s
user 393m58.840s
sys 59m25.380sBuild statistics for nightly-external are available at:
http://autobuilder.pokylinux.org/nightly/20110226-1/buildstats/buildst
ats/Open Defects:
----------------------------As of right now we have:
76 total open defects targeted for 1.0Critical: 0
High: 14
Medium: 53
Low: 7
Undetermined: 2Thanks for all those who helped with this weekends RC generation, especially sgw and
RP__
Quoted 8 lines
------------------
Elizabeth Flanagan
Yocto Project
Release Engineer
_______________________________________________
yocto mailing list
[email protected]
https://lists.yoctoproject.org/listinfo/yocto
Best Regards,
Lianhao
Quoted 34 lines · Elizabeth Flanagan
Summary
=======This weekend, we generated a release candidate for bernard based on the bernard branch of master at commit:
e08dc5aaaeba61e332caab4a3df5750df6b49ac1and for BSPs based on the bernard branch of meta-intel at commit:
16f47f04a2baaeaf9b5a9b381fc7a3c7755d6ff6Issues seen:
===========Build Infrastructure issues:
----------------------------- We had an issue with builder02 running out of disk space, so some of the build copying was done post-build. This did not effect the build and was dealt with manually after cleaning up the partition.
- There is an issue with how package-index is being run. I will need to sync up with Jessica to verify how this should be incorporated into the build.
- The sanity tests on builder02 failed because builder02 was unable to resolve "localhost". This has been corrected and the sanity tests re-run incrementally:
http://autobuilder.pokylinux.org:8010/builders/nightly-internal-sanity/builds/3- The tarball generation buildstep is not branch aware. This will be fixed this week. In the meantime it was run manually.
Sanity Test Issues:
----------------------------
Quoted 8 lines
- zypper-search failed on qemux-x86_64 on poky-image-lsb and poky-image-sato
Build Issues:
----------------------------- BSPs did not complete successfully. There were some issue in the actual build mostly centering around:
- Failing todo_kernel_checkout
There are a couple problems with the jasperforest BSP. First, the SRCREVs need updating, which I just submitted a patch for.
Even after that, though, there seems to be a problem with the kernel repo the fetcher is getting. Even after clearing it out of git2, the kernel repo that gets fetched into git2 and the build doesn't have the jasperforest branch. A manual local clone of linux-yocto-2.6.37 does contain the branch, though, and pointing the build to the local clone finds the branch and builds(*) ok.
(*) until it gets to compiling perf - at that point it fails since the branch doesn't yet have the perf compile fix moved from master.
Tom
Quoted 41 lines
- Unpack issues around svn://svn.o-hand.com/repos
- Beagleboard failed doing runstrip on uboot during
do_populate_sysrootBuild statistic:
----------------------------Using RP__'s machine as a baseline, our current build stats for poky-image-sato is:
real 109m52.400s
user 393m58.840s
sys 59m25.380sBuild statistics for nightly-external are available at:
http://autobuilder.pokylinux.org/nightly/20110226-1/buildstats/buildstats/
Open Defects:
----------------------------As of right now we have:
76 total open defects targeted for 1.0Critical: 0
High: 14
Medium: 53
Low: 7
Undetermined: 2Thanks for all those who helped with this weekends RC generation, especially sgw and
RP__------------------
Elizabeth Flanagan
Yocto Project
Release Engineer
_______________________________________________
yocto mailing list
[email protected]
https://lists.yoctoproject.org/listinfo/yocto
Quoted 54 lines · Tom Zanussi
Quoted 34 lines · Elizabeth Flanagan
Summary
=======This weekend, we generated a release candidate for bernard based on the bernard branch of master at commit:
e08dc5aaaeba61e332caab4a3df5750df6b49ac1and for BSPs based on the bernard branch of meta-intel at commit:
16f47f04a2baaeaf9b5a9b381fc7a3c7755d6ff6Issues seen:
===========Build Infrastructure issues:
----------------------------- We had an issue with builder02 running out of disk space, so some of the build copying was done post-build. This did not effect the build and was dealt with manually after cleaning up the partition.
- There is an issue with how package-index is being run. I will need to sync up with Jessica to verify how this should be incorporated into the build.
- The sanity tests on builder02 failed because builder02 was unable to resolve "localhost". This has been corrected and the sanity tests re-run incrementally:
http://autobuilder.pokylinux.org:8010/builders/nightly-internal-sanity/builds/3- The tarball generation buildstep is not branch aware. This will be fixed this week. In the meantime it was run manually.
Sanity Test Issues:
----------------------------Quoted 8 lines
- zypper-search failed on qemux-x86_64 on poky-image-lsb and poky-image-sato
Build Issues:
----------------------------- BSPs did not complete successfully. There were some issue in the actual build mostly centering around:
- Failing todo_kernel_checkoutThere are a couple problems with the jasperforest BSP. First, the SRCREVs need updating, which I just submitted a patch for.
Even after that, though, there seems to be a problem with the kernel repo the fetcher is getting. Even after clearing it out of git2, the kernel repo that gets fetched into git2 and the build doesn't have the jasperforest branch. A manual local clone of linux-yocto-2.6.37 does contain the branch, though, and pointing the build to the local clone finds the branch and
builds(*)ok.
Quoted 3 lines
(*) until it gets to compiling perf - at that point it fails since the branch doesn't yet have the perf compile fix moved from master.
The jasperforest branch just got updated, and I just submitted a SRCREV update to use that, which takes care of the perf compile error.
I still see the problem with the the fetcher not getting the current linux-yocto-2.6.37, so it looks like either a problem with the fetcher or some stale cache lodged somewhere.
An interesting related thing is that I also see it with the 2.6.37 crownbay branch - a local clone works fine, but in the repo fetched into git2 and the build the crownbay branch is missing, but in that case even though the branch doesn't appear, its commits are actually in the repo e.g. git log <commitid> shows the commits there.
Tom
Quoted 44 lines
Tom
Quoted 41 lines
- Unpack issues around svn://svn.o-hand.com/repos
- Beagleboard failed doing runstrip on uboot during
do_populate_sysrootBuild statistic:
----------------------------Using RP__'s machine as a baseline, our current build stats for poky-image-sato is:
real 109m52.400s
user 393m58.840s
sys 59m25.380sBuild statistics for nightly-external are available at:
http://autobuilder.pokylinux.org/nightly/20110226-1/buildstats/buildstats/
Open Defects:
----------------------------As of right now we have:
76 total open defects targeted for 1.0Critical: 0
High: 14
Medium: 53
Low: 7
Undetermined: 2Thanks for all those who helped with this weekends RC generation, especially sgw and
RP__------------------
Elizabeth Flanagan
Yocto Project
Release Engineer
_______________________________________________
yocto mailing list
[email protected]
https://lists.yoctoproject.org/listinfo/yocto
Quoted 59 lines · Tom Zanussi
Quoted 54 lines · Tom Zanussi
Quoted 34 lines · Elizabeth Flanagan
Summary
=======This weekend, we generated a release candidate for bernard based on the bernard branch of master at commit:
e08dc5aaaeba61e332caab4a3df5750df6b49ac1and for BSPs based on the bernard branch of meta-intel at commit:
16f47f04a2baaeaf9b5a9b381fc7a3c7755d6ff6Issues seen:
===========Build Infrastructure issues:
----------------------------- We had an issue with builder02 running out of disk space, so some of the build copying was done post-build. This did not effect the build and was dealt with manually after cleaning up the partition.
- There is an issue with how package-index is being run. I will need to sync up with Jessica to verify how this should be incorporated into the build.
- The sanity tests on builder02 failed because builder02 was unable to resolve "localhost". This has been corrected and the sanity tests re-run incrementally:
http://autobuilder.pokylinux.org:8010/builders/nightly-internal-sanity/builds/3- The tarball generation buildstep is not branch aware. This will be fixed this week. In the meantime it was run manually.
Sanity Test Issues:
----------------------------Quoted 8 lines
- zypper-search failed on qemux-x86_64 on poky-image-lsb and poky-image-sato
Build Issues:
----------------------------- BSPs did not complete successfully. There were some issue in the actual build mostly centering around:
- Failing todo_kernel_checkoutThere are a couple problems with the jasperforest BSP. First, the SRCREVs need updating, which I just submitted a patch for.
Even after that, though, there seems to be a problem with the kernel repo the fetcher is getting. Even after clearing it out of git2, the kernel repo that gets fetched into git2 and the build doesn't have the jasperforest branch. A manual local clone of linux-yocto-2.6.37 does contain the branch, though, and pointing the build to the local clone finds the branch and
builds(*)ok.Quoted 3 lines
(*) until it gets to compiling perf - at that point it fails since the branch doesn't yet have the perf compile fix moved from master.
Quoted 7 lines
The jasperforest branch just got updated, and I just submitted a SRCREV update to use that, which takes care of the perf compile error.
I still see the problem with the the fetcher not getting the current linux-yocto-2.6.37, so it looks like either a problem with the fetcher or some stale cache lodged somewhere.
Yeah, it looks like stale cache.
http://autobuilder.yoctoproject.org/sources/git2_git.pokylinux.org.linux-yocto-2.6.37.tar.gz
doesn't have local branches for yocto/standard/common-pc-64/jasperforest or yocto/standard/crownbay.
Tom
Quoted 53 lines
An interesting related thing is that I also see it with the 2.6.37 crownbay branch - a local clone works fine, but in the repo fetched into git2 and the build the crownbay branch is missing, but in that case even though the branch doesn't appear, its commits are actually in the repo e.g. git log <commitid> shows the commits there.
Tom
Quoted 44 lines
Tom
Quoted 41 lines
- Unpack issues around svn://svn.o-hand.com/repos
- Beagleboard failed doing runstrip on uboot during
do_populate_sysrootBuild statistic:
----------------------------Using RP__'s machine as a baseline, our current build stats for poky-image-sato is:
real 109m52.400s
user 393m58.840s
sys 59m25.380sBuild statistics for nightly-external are available at:
http://autobuilder.pokylinux.org/nightly/20110226-1/buildstats/buildstats/
Open Defects:
----------------------------As of right now we have:
76 total open defects targeted for 1.0Critical: 0
High: 14
Medium: 53
Low: 7
Undetermined: 2Thanks for all those who helped with this weekends RC generation, especially sgw and
RP__------------------
Elizabeth Flanagan
Yocto Project
Release Engineer
_______________________________________________
yocto mailing list
[email protected]
https://lists.yoctoproject.org/listinfo/yocto