Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "Platform-releng-troubleshooting"
m |
m |
||
| Line 22: | Line 22: | ||
# Missing dependancies due to erroneous map file submission. Check that the map file refers to a version of a project that exists in the repo. | # Missing dependancies due to erroneous map file submission. Check that the map file refers to a version of a project that exists in the repo. | ||
| − | # Missing dependancies due to errors in Manifest or missing dependancies in manifest. In the both cases, the error sent to the releng list will look something like | + | # Missing dependancies due to errors in Manifest or missing dependancies in manifest. In the both cases, the error sent to the releng list will look something like http://dev.eclipse.org/mhonarc/lists/platform-releng-dev/msg09778.html |
| − | http://dev.eclipse.org/mhonarc/lists/platform-releng-dev/msg09778.html | + | |
# Dependancies expressed in manifest and feature don't match. This means that the p2 director cannot resolve the dependencies for the product it is trying to build. The resultant zips for that platform are 0 size. For instance, see bug [https://bugs.eclipse.org/bugs/show_bug.cgi?id=258489 | bug 258489]. Also, you can see the .log files that the directory built by following the <i>Release Engineering build logs</i> link off the <i>Test results</i> build page. | # Dependancies expressed in manifest and feature don't match. This means that the p2 director cannot resolve the dependencies for the product it is trying to build. The resultant zips for that platform are 0 size. For instance, see bug [https://bugs.eclipse.org/bugs/show_bug.cgi?id=258489 | bug 258489]. Also, you can see the .log files that the directory built by following the <i>Release Engineering build logs</i> link off the <i>Test results</i> build page. | ||
# Failed to fetch an orbit bundle - build failed with http timeout. Update the map so that bundle is fetched from a local mirror such as http://fullmoon.ottawa.ibm.com | # Failed to fetch an orbit bundle - build failed with http timeout. Update the map so that bundle is fetched from a local mirror such as http://fullmoon.ottawa.ibm.com | ||
Revision as of 17:10, 11 December 2008
Basic build troubleshooting
The builds run from cron on our build machine as follows
integration builds
0 8 * * 2 cd /builds; /home/users/releng/buildTools/eclipse34/runIBuild
subsequuent integration build without perf tests is run like this if a rebuild is requested (cd /builds; /home/users/releng/buildTools/eclipse34/runIBuild-skipPerf)
nightly builds 10 0 * * 1,2,3,5,6 cd /builds; /home/users/releng/buildTools/eclipse34/runNBuild-skipPerf 10 0 * * 4,0 cd /builds; /home/users/releng/buildTools/eclipse34/runNBuild
maintenance builds 0 8 * * 3 cd /builds; /home/users/releng/buildTools/eclipse33x/runMBuild
Basic build troubleshooting
Common Reasons for build failures
- Missing dependancies due to erroneous map file submission. Check that the map file refers to a version of a project that exists in the repo.
- Missing dependancies due to errors in Manifest or missing dependancies in manifest. In the both cases, the error sent to the releng list will look something like http://dev.eclipse.org/mhonarc/lists/platform-releng-dev/msg09778.html
- Dependancies expressed in manifest and feature don't match. This means that the p2 director cannot resolve the dependencies for the product it is trying to build. The resultant zips for that platform are 0 size. For instance, see bug | bug 258489. Also, you can see the .log files that the directory built by following the Release Engineering build logs link off the Test results build page.
- Failed to fetch an orbit bundle - build failed with http timeout. Update the map so that bundle is fetched from a local mirror such as http://fullmoon.ottawa.ibm.com