summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorSkip Montanaro <skip@pobox.com>2003-05-06 16:17:27 (GMT)
committerSkip Montanaro <skip@pobox.com>2003-05-06 16:17:27 (GMT)
commitc9803ab855f7c96278952627dec44899b78d109a (patch)
tree916a39850a6a913b9a09afce77984a2c2ceb643e
parent1a56665e39e4ee3cb29519a1cb58f2ab077622f1 (diff)
downloadcpython-c9803ab855f7c96278952627dec44899b78d109a.zip
cpython-c9803ab855f7c96278952627dec44899b78d109a.tar.gz
cpython-c9803ab855f7c96278952627dec44899b78d109a.tar.bz2
add Guido's reasoning behind running all tests twice
-rw-r--r--Makefile.pre.in7
1 files changed, 7 insertions, 0 deletions
diff --git a/Makefile.pre.in b/Makefile.pre.in
index 207798e..843c50f 100644
--- a/Makefile.pre.in
+++ b/Makefile.pre.in
@@ -514,6 +514,13 @@ $(LIBRARY_OBJS) $(MODOBJS) Modules/$(MAINOBJ): $(PYTHON_HEADERS)
######################################################################
# Test the interpreter (twice, once without .pyc files, once with)
+# In the past, we've had problems where bugs in the marshalling or
+# elsewhere caused bytecode read from .pyc files to behave differently
+# than bytecode generated directly from a .py source file. Sometimes
+# the bytecode read from a .pyc file had the bug, somtimes the directly
+# generated bytecode. This is sometimes a very shy bug needing a lot of
+# sample data.
+
TESTOPTS= -l
TESTPROG= $(srcdir)/Lib/test/regrtest.py
TESTPYTHON= $(RUNSHARED) ./$(BUILDPYTHON) -E -tt