| | 121 | == Refreshing the slave build == |
| | 122 | |
| | 123 | For reasons of efficiency the slave build (which can be performed multiple times each day) is done as an update build. |
| | 124 | Certain types of commits are known to be likely to cause issues with update builds, including : |
| | 125 | * changes to DataModel classes |
| | 126 | |
| | 127 | In order to freshen up the build you can try rebuilding after removing various directories, in progressively increasing levels of cleanliness : |
| | 128 | * {{{rm -rf NuWa-trunk/dybgaudi/DybRelease/$CMTCONFIG}}} |
| | 129 | * {{{rm -rf NuWa-trunk/dybgaudi/InstallArea}}} |
| | 130 | * {{{rm -rf NuWa-trunk/dybgaudi/* ; svn up NuWa-trunk/dybgaudi}}} |
| | 131 | |
| | 132 | To trigger a slave build after the removal, invalidate the last build on the node in question using the web interface (BUILD_ADMIN privilege required) |
| | 133 | |
| | 134 | == Monitoring the slave node == |
| | 135 | |
| | 136 | After many failures on a slave, it is wise to check running processes {{{ps aux}}}, it can happen that many tens of stuck nuwa.py processes can kill your node. |
| | 137 | Clean up with |
| | 138 | {{{pgrep -f nuwa.py ; pkill -f nuwa.py}}} |
