Notice: This Wiki is now read only and edits are no longer 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 5: | Line 5: | ||
<code> | <code> | ||
integration builds | integration builds | ||
| − | 0 8 * * 2 cd /builds; /home/users/releng/buildTools/ | + | 0 8 * * 2 cd /builds; /home/users/releng/buildTools/eclipse36/runIBuild |
subsequent integration build without perf tests is run like this if a rebuild is requested (cd /builds; /home/users/releng/buildTools/eclipse34/runIBuild-skipPerf) | subsequent 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 | nightly builds | ||
| − | 10 0 * * 1,2,3,5,6 cd /builds; /home/users/releng/buildTools/ | + | 10 0 * * 1,2,3,5,6 cd /builds; /home/users/releng/buildTools/eclipse36/runNBuild-skipPerf |
| − | 10 0 * * 4,0 cd /builds; /home/users/releng/buildTools/ | + | 10 0 * * 4,0 cd /builds; /home/users/releng/buildTools/eclipse36/runNBuild |
maintenance builds | maintenance builds | ||
| − | 0 8 * * 3 cd /builds; /home/users/releng/buildTools/ | + | 0 8 * * 3 cd /builds; /home/users/releng/buildTools/eclipse35x/runMBuild |
</code> | </code> | ||
Revision as of 15:39, 24 August 2009
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/eclipse36/runIBuild
subsequent 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/eclipse36/runNBuild-skipPerf 10 0 * * 4,0 cd /builds; /home/users/releng/buildTools/eclipse36/runNBuild
maintenance builds 0 8 * * 3 cd /builds; /home/users/releng/buildTools/eclipse35x/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
Missing test results
- The test results page of the build isn't updated until all the test results have completed. To see what machines are currently being used for tests look the the following directory. There will be marker files that correspond to the machine operating system and build number.
-bash-3.00$ ls /home/users/releng/buildTools/markers/*.marker eclipse-macosx-M20090824-0800.marker eclipse-rhelws5-6.0-M20090824-0800.marker eclipse-rhelws5-M20090824-0800.marker eclipse-rhelws5-perf-M20090824-0800.marker eclipse-sled10-perf-M20090824-0800.marker eclipse-win32xp-6.0-M20090824-0800.marker eclipse-win32xp-M20090824-0800.marker eclipse-win32xp-perf-M20090824-0800.marker
If you cat the marker files you can see the hostname of the machine that corresponds to the marker file
-bash-3.00$ cat /home/users/releng/buildTools/markers/*.marker 0=lb6mac 0=ejlnx2 0=ejlnx1 0=eplnx2 0=eplnx1 0=ejwin2 0=ejwin1 0=epwin2
The windows machines run tests via rsh. The linux and mac machines run tests via ssh. The windows machines need to be rebooted every so often. The old build artifacts are cleaned automatically by cron jobs.