[Python-checkins] r55022 - python/branches/release25-maint/Misc/build.sh (original) (raw)

neal.norwitz python-checkins at python.org
Mon Apr 30 01:56:23 CEST 2007

Author: neal.norwitz Date: Mon Apr 30 01:56:19 2007 New Revision: 55022

Modified: python/branches/release25-maint/Misc/build.sh Log: Update with the version that has been running for a while. Most of the changes are to support multiple versions (ie, trunk and 2.5). Also check for conflicts in the .tex file when a release is cut.

Modified: python/branches/release25-maint/Misc/build.sh

--- python/branches/release25-maint/Misc/build.sh (original) +++ python/branches/release25-maint/Misc/build.sh Mon Apr 30 01:56:19 2007 @@ -47,11 +47,12 @@ FAILURE_SUBJECT="Python Regression Test Failures" #FAILURE_MAILTO="YOUR_ACCOUNT at gmail.com" FAILURE_MAILTO="python-checkins at python.org" +#FAILURE_CC="optional--uncomment and set to desired address"

REMOTE_SYSTEM="neal at dinsdale.python.org" -REMOTE_DIR="/data/ftp.python.org/pub/docs.python.org/dev/" +REMOTE_DIR="/data/ftp.python.org/pub/docs.python.org/dev/2.5" RESULT_FILE="$DIR/build/index.html" -INSTALL_DIR="/tmp/python-test/local" +INSTALL_DIR="/tmp/python-test-2.5/local" RSYNC_OPTS="-aC -e ssh"

Always run the installed version of Python.

@@ -66,7 +67,7 @@

Note: test_XXX (none currently) really leak, but are disabled

so we don't send spam. Any test which really leaks should only

be listed here if there are also test cases under Lib/test/leakers.

-LEAKY_TESTS="test_(XXX)" # Currently no tests should report spurious leaks. +LEAKY_TESTS="test_(cmd_line|socket)"

Skip these tests altogether when looking for leaks. These tests

do not need to be stored above in LEAKY_TESTS too.

@@ -76,7 +77,7 @@ LEAKY_SKIPS="-x test_compiler test_logging"

Change this flag to "yes" for old releases to only update/build the docs.

-BUILD_DISABLED="no" +BUILD_DISABLED="yes"

utility functions

current_time() { @@ -91,7 +92,12 @@

mail_on_failure() { if [ "$NUM_FAILURES" != "0" ]; then

@@ -208,8 +214,19 @@ cd $DIR/Doc F="make-doc.out" start=current_time -make >& ../build/$F -err=$? +# Doc/commontex/boilerplate.tex is expected to always have an outstanding +# modification for the date. When a release is cut, a conflict occurs. +# This allows us to detect this problem and not try to build the docs +# which will definitely fail with a conflict. +CONFLICTED_FILE=commontex/boilerplate.tex +conflict_count=grep -c "<<<" $CONFLICTED_FILE +if [ $conflict_count != 0 ]; then

+else

+fi update_status "Making doc" "$F" $start if [ $err != 0 ]; then NUM_FAILURES=1

More information about the Python-checkins mailing list