| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
| |
* Oops, tzdata was introduced in Python 3.6: remove it from regrtest
* Remove also Lib/test/libregrtest/__init__.py file: add by mistake
on a backport.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
When running the test suite using --use=all / -u all, exclude tzdata
since it makes test_datetime too slow (15-20 min on some buildbots)
which then times out on some buildbots.
-u tzdata must now be enabled explicitly, -u tzdata or -u all,tzdata,
to run all test_datetime tests.
Fix also regrtest command line parser to allow passing -u
extralargefile to run test_zipfile64.
Travis CI: remove -tzdata. Replace -u all,-tzdata,-cpu with -u all,-cpu since tzdata is now excluded from -u all.
(cherry picked from commit 5b392bbaeb9d9b1db961ecfc7315d8c8662c27f6)
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
3.6 to 3.5 (#2540)
* [3.6] bpo-29512, bpo-30776: Backport regrtest enhancements from master to 3.6 (#2513)
* bpo-29512: Add test.bisect, bisect failing tests (#2452)
Add a new "python3 -m test.bisect" tool to bisect failing tests.
It can be used to find which test method(s) leak references, leak
files, etc.
(cherry picked from commit 84d9d14a1fa395fbd21262ba195490be25a7b3bc)
* bpo-30776: regrtest: reduce memleak false positive (#2484)
Only report a leak if each run leaks at least one memory block.
(cherry picked from commit beeca6e1e5fd01531b1db7059498b13d07dca525)
(cherry picked from commit a3ca94d0504157a112a1f89bfe8be1307116fc73)
* bpo-30764: Fix regrtest --fail-env-changed --forever (#2536) (#2539)
--forever now stops if a fail changes the environment.
(cherry picked from commit 5e87592fd12e0b7c41edc11d4885ed7298d5063b)
(cherry picked from commit 4132adb4b8f90893d8f19ff46edff56f189faca0)
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
* bpo-30523: regrtest --list-cases --match (#2401)
* regrtest --list-cases now supports --match and --match-file options.
Example: ./python -m test --list-cases -m FileTests test_os
* --list-cases now also sets support.verbose to False to prevent
messages to stdout when loading test modules.
* Add support._match_test() private function.
(cherry picked from commit ace56d583664f855d89d1219ece7c21c2fddcf30)
* bpo-30764: regrtest: add --fail-env-changed option (#2402)
* bpo-30764: regrtest: change exit code on failure
* Exit code 2 if failed tests ("bad")
* Exit code 3 if interrupted
* bpo-30764: regrtest: add --fail-env-changed option
If the option is set, mark a test as failed if it alters the
environment, for example if it creates a file without removing it.
(cherry picked from commit 63f54c68936d648c70ca411661e4208329edcf26)
* bpo-30776: reduce regrtest -R false positives (#2422)
* Change the regrtest --huntrleaks checker to decide if a test file
leaks or not. Require that each run leaks at least 1 reference.
* Warmup runs are now completely ignored: ignored in the checker test
and not used anymore to compute the sum.
* Add an unit test for a reference leak.
Example of reference differences previously considered a failure
(leak) and now considered as success (success, no leak):
[3, 0, 0]
[0, 1, 0]
[8, -8, 1]
(cherry picked from commit 48b5c422ffb03affb00c184b9a99e5537be92732)
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
master to 3.5 (#2279)
* bpo-30383: regrtest: prepend testdir to sys.path
* bpo-30383: Backport test_regrtest
* regrtest: rename --slow option to --slowest
The old --slow syntax is still accepted.
* regrtest: add a single oneliner summary
Example: "Tests result: SUCCESS"
* test_regrtest: add test_coverage()
regrtest now also displays the number of successful tests when
coverage is used.
* test_regrtest: add test_crashed()
Handle correctly crashing test: account the crash has a failed test,
but continue to run other tests.
* regrtest: backport --list-tests feature
* regrtest: backport --fromfile enhancements
* regrtest: backport displaying progress enhancements
* test_regrtest: backport test_randseed()
* regrtest: Fix --coverage on Windows
Don't ignore any directory anymore. Change backported from master.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
regrtest (#2250)
* bpo-30540: regrtest: add --matchfile option
* Add a new option taking a filename to get a list of test names to
filter tests.
* support.match_tests becomes a list.
* Modify run_unittest() to accept to match the whole test identifier,
not just a part of a test identifier.
For example, the following command only runs test_access()
of the FileTests class of test_os:
$ ./python -m test -v -m test.test_os.FileTests.test_access test_os
* bpo-30523: regrtest: Add --list-cases option
* Add --list-cases option to regrtest
* Add get_abs_module() function, use it in list_cases()
* Add ns mandatory positional argument to runtest()
and runtest_inner()
* Add file optional parameter to printlist()
Co-Authored-By: Louie Lu <git@louie.lu>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
* Rewrite code to pass slaveargs from the master process to worker
processes: reuse the same code of the Python master branch
* Move code to initialize tests in a new setup_tests() function,
similar change was done in the master branch
* In a worker process, call setup_tests() with the namespace built
from slaveargs to initialize correctly tests
Before this change, warm_caches() was not called in worker processes
because the setup was done before rebuilding the namespace from
slaveargs. As a consequence, the huntrleaks feature was unstable. For
example, test_zipfile reported randomly false positive on reference
leaks.
|
|
|
| |
Workaround for a regrtest bug.
|
|
|
|
|
|
|
|
|
| |
Buildbots don't run tests with -vv and so only log "xxx was modified
by test_xxx" which is not enough to debug such random issue. In many
cases, I'm unable to reproduce the warning and so unable to fix it.
Always logging the value before and value after should help to debug
such warning on buildbots.
(cherry picked from commit ec4b17239d899550be4ee6104b61751bb3c70382)
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
Reloading the warnings module duplicates filters in warnings.filters. Fixing
the issue is tricky. It was decided to simply remove the check from Python 3.5,
since the bug only impacts Python unit tests, not real applications.
The check is kept in Python 3.6 and newer.
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
regrtest -W hides output if a test pass, but also when env changed and so the
env changed warning is hidden. So it's hard to debug. With this change, stderr
is now always displayed when a test doesn't pass.
|
| |
|
| |
|
| |
|
|\ |
|
| | |
|
| | |
|
| | |
|
| |
| |
| |
| |
| |
| | |
Since PGO building doesn't care about test failures, silence them when
running the test suite for performance reasons. Initial patch by
Alecsandru Patrascu of Intel.
|
|\ \
| |/ |
|
| |
| |
| |
| | |
anymore
|
|\ \
| |/ |
|
| | |
|
| |
| |
| |
| | |
Patch by Martin Panter.
|
|\ \
| |/
| |
| | |
directories are left after running a test.
|
| |
| |
| |
| | |
directories are left after running a test.
|
|/
|
|
| |
loader.loadTestsFromModule() logged errors.
|
| |
|
|\ |
|
| | |
|
|\ \
| |/ |
|
| | |
|
| |
| |
| |
| | |
Python now uses SipHash24 on all major platforms.
|
| |
| |
| |
| |
| | |
If bots fail due to using this flag, the buildbot scripts have to be modified
to omit it. Regrtest ignores it anyway.
|
| | |
|
| |
| |
| |
| | |
Moving subprocess execution of tests into a function.
|
| | |
|
| | |
|
| |
| |
| |
| | |
parsing. Added more tests for regrtest's argument parsing.
|
| |
| |
| |
| | |
See http://hg.python.org/sandbox/sbt#spawn
|
|\ \
| |/ |
|
| |
| |
| |
| | |
testsuite.
|
| | |
|
| |
| |
| |
| | |
applicable.
|
| |
| |
| |
| | |
in subprocesses.
|