Below is the list of changes that have just been committed into a local
5.0 repository of kent. When kent does a push these changes will
be propagated to the main repository and, within 24 hours after the
push, to the public repository.
For information on how to access the public repository
see http://dev.mysql.com/doc/mysql/en/installing-source-tree.html
ChangeSet
1.2025 05/10/25 03:00:09 kent@stripped +2 -0
Merge mysql.com:/Users/kent/mysql/bk/mysql-4.0-build-thread
into mysql.com:/Users/kent/mysql/bk/mysql-5.0
mysql-test/mysql-test-run.sh
1.278 05/10/25 03:00:04 kent@stripped +3 -1
Makefile.am
1.80 05/10/25 02:57:48 kent@stripped +13 -17
# This is a BitKeeper patch. What follows are the unified diffs for the
# set of deltas contained in the patch. The rest of the patch, the part
# that BitKeeper cares about, is below these diffs.
# User: kent
# Host: c-634072d5.010-2112-6f72651.cust.bredbandsbolaget.se
# Root: /Users/kent/mysql/bk/mysql-5.0/RESYNC
--- 1.79/Makefile.am 2005-09-28 15:44:24 +02:00
+++ 1.80/Makefile.am 2005-10-25 02:57:48 +02:00
@@ -97,36 +97,35 @@
support-files/build-tags
.PHONY: init-db bin-dist
-# Test installation. Ports are configurable from the environment.
-
-MYSQL_TEST_MANAGER_PORT = 9305
-MYSQL_TEST_MASTER_PORT = 9306
-MYSQL_TEST_SLAVE_PORT = 9308
-MYSQL_TEST_NDB_PORT = 9350
-MYSQL_TEST_RUN_ARGS = --manager-port=$(MYSQL_TEST_MANAGER_PORT) \
- --master_port=$(MYSQL_TEST_MASTER_PORT) \
- --slave_port=$(MYSQL_TEST_SLAVE_PORT) \
- --ndbcluster_port=$(MYSQL_TEST_NDB_PORT)
+# Target 'test' will run the regression test suite using the built server.
+#
+# If you are running in a shared environment, users can avoid clashing
+# port numbers by setting individual small numbers 1-100 to the
+# environment variable MTR_BUILD_THREAD. The script "mysql-test-run"
+# will then calculate the various port numbers it needs from this,
+# making sure each user use different ports.
test:
cd mysql-test ; \
- ./mysql-test-run $(MYSQL_TEST_RUN_ARGS) && \
- ./mysql-test-run $(MYSQL_TEST_RUN_ARGS) --ps-protocol
+ ./mysql-test-run && \
+ ./mysql-test-run --ps-protocol
test-force:
- cd mysql-test ; \
- ./mysql-test-run $(MYSQL_TEST_RUN_ARGS) --force ; \
- ./mysql-test-run $(MYSQL_TEST_RUN_ARGS) --ps-protocol --force
+ cd mysql-test; \
+ ./mysql-test-run --force ; \
+ ./mysql-test-run --ps-protocol --force
+# We are testing a new Perl version of the test script
test-pl:
- cd mysql-test ; \
- ./mysql-test-run.pl $(MYSQL_TEST_RUN_ARGS) && \
- ./mysql-test-run.pl $(MYSQL_TEST_RUN_ARGS) --ps-protocol
+ cd mysql-test; \
+ ./mysql-test-run.pl && \
+ ./mysql-test-run.pl --ps-protocol
test-force-pl:
- cd mysql-test ; \
- ./mysql-test-run.pl $(MYSQL_TEST_RUN_ARGS) --force ; \
- ./mysql-test-run.pl $(MYSQL_TEST_RUN_ARGS) --ps-protocol --force
+ cd mysql-test; \
+ ./mysql-test-run.pl --force ; \
+ ./mysql-test-run.pl --ps-protocol --force
# Don't update the files from bitkeeper
%::SCCS/s.%
+
--- 1.277/mysql-test/mysql-test-run.sh 2005-10-18 22:46:37 +02:00
+++ 1.278/mysql-test/mysql-test-run.sh 2005-10-25 03:00:04 +02:00
@@ -216,6 +216,25 @@
MYSQL_MANAGER_PW_FILE=$MYSQL_TEST_DIR/var/tmp/manager.pwd
MYSQL_MANAGER_LOG=$MYSQL_TEST_DIR/var/log/manager.log
MYSQL_MANAGER_USER=root
+
+#
+# To make it easier for different devs to work on the same host,
+# an environment variable can be used to control all ports. A small
+# number is to be used, 0 - 16 or similar.
+#
+if [ -n "$MTR_BUILD_THREAD" ] ; then
+ MASTER_MYPORT=`expr $MTR_BUILD_THREAD '*' 40 + 8120`
+ MYSQL_MANAGER_PORT=`expr $MASTER_MYPORT + 2`
+ SLAVE_MYPORT=`expr $MASTER_MYPORT + 16`
+ NDBCLUSTER_PORT=`expr $MASTER_MYPORT + 24`
+
+ echo "Using MTR_BUILD_THREAD = $MTR_BUILD_THREAD"
+ echo "Using MASTER_MYPORT = $MASTER_MYPORT"
+ echo "Using MYSQL_MANAGER_PORT = $MYSQL_MANAGER_PORT"
+ echo "Using SLAVE_MYPORT = $SLAVE_MYPORT"
+ echo "Using NDBCLUSTER_PORT = $NDBCLUSTER_PORT"
+fi
+
NO_SLAVE=0
USER_TEST=
FAILED_CASES=
| Thread |
|---|
| • bk commit into 5.0 tree (kent:1.2025) | kent | 25 Oct |