| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
| |
Use an improved version of multissl test helper to compile a local copy
of OpenSSL 1.1.0g.
Signed-off-by: Christian Heimes <christian@python.org>
|
|
|
|
|
|
| |
running make (GH-4346)" (#4592)
Fix breakage documented in bpo-32149.
This reverts commit d8d6b9122134f040cd5a4f15f40f6c9e3386db4d.
|
|
|
|
| |
(GH-4346)
|
|
|
|
|
|
|
| |
* Add Tools/scripts/smelly.py: script checking if all symbols
exported by libpython start with "Py" or "_Py".
* Modify "make smelly" to run smelly.py: the command now fails with a
non-zero exit code if libpython leaks a "smelly" symbol.
* Travis CI now runs "make smelly"
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
bpo-31231, bpo-30871: Replace "./python -m test.pythoninfo" with
"make pythoninfo", since macOS uses ./python.exe.
|
|
|
|
|
|
| |
* Add Lib/test/pythoninfo.py: script collecting various informations
about Python to help debugging test failures.
* regrtest: remove sys.hash_info and sys.flags from header.
* Travis CI, Appveyor: run pythoninfo before tests
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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.
|
| |
|
|
|
| |
Also fixed a few more line endings that were missed in GH-840, which were causing failure.
|
| |
|
| |
|
|
|
| |
Also weakens the 'should this be run?' regex to allow all builds when .travis.yml changes.
|
|
|
| |
Initially the macOS builds are allowed to fail until such time that they can be determined to be stable and not add an unacceptable amount of time to the overall Travis-passing process.
|
| |
|
| |
|
| |
|
| |
|
|
|
| |
Instead have gcc be used for the coverage build so gcc is exercised in at least one place.
|
| |
|
|
|
| |
The $CXX environment variable is not exported under the 'c' language on Travis.
|
|
|
| |
This will eliminate one of the builds in Travis, allowing for CI overall to complete faster.
|
|
|
| |
No need to wait passing tests after resolving Misc/NEWS conflicts.
|
|
|
|
|
|
| |
rstlint.py run by "make check" doesn't support Python 2.
"make venv" runs "$(PYTHON) -m venv", whereas Python 2 doens't
provide the venv module: it's a module of Python 3 standard library.
|
|
|
|
|
|
|
| |
- Return to always building the docs, it's a relatively cheap operation,
the check had a bug, and the docs build depends on other files.
- Add `make suspicious`
- Do all three checks as one `make check suspicious html` invocation for
earliest possible exit in case of issues.
|
|
|
|
|
|
|
|
|
|
|
| |
If someone pushes a branch to python/cpython and then creates a PR
it will cause Travis to run tests needlessly, once for the PR and
once for the push. This will limit the branches that Travis will
run tests for to the `master` branch and branches that match the regex
`^\d\.\d$`.
This will have the effect that if someone purposely makes another branch
they won't get tests to run, but in that rare case they can adjust this
themselves.
|
|
|
|
|
| |
complete (#101)
Without this flag, the coverage test will hold up the status of the pull request.
|
| |
|
|
|
| |
Closes python/core-workflow#14
|
|
|
|
|
|
|
|
|
|
| |
Currently, http://buildbot.python.org/all/buildslaves/ware-docs
buildbot is only run as post-commit. For example, bpo-29521 (PR#41)
introduced two warnings, unnotified by the Travis CI docs job.
Modify the docs job to run toosl/rstlint.py.
Fix also the two minor warnings which causes the buildbot slave to
fail.
|
| |
|
|
|
|
|
|
|
| |
If the IRC notification is stored in plaintext, then anyone who forks
the repository and also adds it to travis will send notifications to
the IRC channel for their fork by default. Since the secure variable
is encrypted using a repository specific key, this will only work when
it is being built using the correct repository.
|
|
|
| |
bpo-29527.
|
|
|