Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Release 3.10.0 #4297

Merged
merged 64 commits into from
Nov 4, 2018
Merged

Release 3.10.0 #4297

merged 64 commits into from
Nov 4, 2018

Conversation

nicoddemus
Copy link
Member

No description provided.

nip3o and others added 30 commits October 15, 2018 20:04
Issue a warning when a fixture named 'request' is collected
…_remove_writable

minor: remove unused _shutil_rmtree_remove_writable
Running `pytest -k doesnotmatch` on pytest's own tests takes ~3s with
Kitty terminal for me, but only ~1s with `-q`.
It also is faster with urxvt, but still takes 2.2s there.

This patch only calls `report_collect` every 0.1s, which is good enough
for reporting collection progress, and improves the time with both Kitty
and urxvt to ~1.2s for me.
For pytest's own suite the `cache_info()` looks as follows:

    > session.config._getconftest_pathlist.cache_info()
    CacheInfo(hits=231, misses=19, maxsize=None, currsize=19)

While it does not really make a difference for me this might help with
larger test suites / the case mentioned in
pytest-dev#2206 (comment).
TerminalWriter: write "collecting" msg only once every 0.5s
blueyed and others added 14 commits October 31, 2018 23:13
Also renames `_path2confmods` to `_dirpath2confmods` for clarity (it is
expected to be a dirpath in `_importconftest`).

Uses an explicit maxsize, since it appears to be only relevant for a
short period [1].

Removes the lru_cache on _getconftest_pathlist, which makes no
difference when caching _getconftestmodules, at least with the
performance test of 100x10 files (pytest-dev#4237).

1: pytest-dev#4237 (comment)
…-msg

pdb: improve msg about output capturing with set_trace
_getconftestmodules: use functools.lru_cache
cacheprovider: display cachedir also in non-verbose mode if customized
Time: 5.73s => 5.88s/5.82s
Time: 5.73s/5.88s => 5.36s

(Before rebase: 4.86s => 4.45s)
Time: 5.36s => 4.85s (before rebase: 4.45s => 3.55s)
@blueyed
Copy link
Contributor

blueyed commented Nov 3, 2018

Linting fails:

WARNING CHANGELOG.rst:3 Duplicate explicit target name: "the documentation".

@RonnyPfannschmidt
Copy link
Member

@nicoddemus wrong target branch?

@RonnyPfannschmidt RonnyPfannschmidt changed the base branch from features to master November 3, 2018 20:19
@RonnyPfannschmidt RonnyPfannschmidt changed the base branch from master to features November 3, 2018 20:19
@RonnyPfannschmidt
Copy link
Member

please excuse that mistake, i missed the merge of the master branch
i propose we always mege master into features before creating a release branch to avoid startleing our human selfes

@blueyed
Copy link
Contributor

blueyed commented Nov 3, 2018

Still makes sense to target master here, no?
That's also what HOWTORELEASE says.

Copy link
Member

@RonnyPfannschmidt RonnyPfannschmidt left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

please fix the change-log ref duplication ^^

@codecov
Copy link

codecov bot commented Nov 3, 2018

Codecov Report

Merging #4297 into master will decrease coverage by 0.07%.
The diff coverage is 90.47%.

Impacted file tree graph

@@            Coverage Diff             @@
##           master    #4297      +/-   ##
==========================================
- Coverage   95.86%   95.79%   -0.08%     
==========================================
  Files         109      111       +2     
  Lines       24681    24922     +241     
  Branches     2396     2444      +48     
==========================================
+ Hits        23661    23873     +212     
- Misses        723      748      +25     
- Partials      297      301       +4
Flag Coverage Δ
#docs 28.9% <34.96%> (-0.05%) ⬇️
#doctesting 28.9% <34.96%> (-0.05%) ⬇️
#linting 28.9% <34.96%> (-0.05%) ⬇️
#linux 95.57% <90.47%> (-0.08%) ⬇️
#nobyte 91.81% <71.76%> (-0.18%) ⬇️
#numpy 92.92% <87.75%> (-0.08%) ⬇️
#pexpect 41.61% <52.81%> (-0.02%) ⬇️
#py27 93.92% <86.39%> (-0.12%) ⬇️
#py34 92.13% <72.44%> (-0.14%) ⬇️
#py35 92.14% <72.44%> (-0.14%) ⬇️
#py36 93.83% <84.01%> (-0.14%) ⬇️
#py37 92.2% <79.02%> (-0.1%) ⬇️
#trial 92.92% <87.75%> (-0.08%) ⬇️
#windows 93.97% <75.87%> (-0.16%) ⬇️
#xdist 93.71% <74.14%> (-0.17%) ⬇️
Impacted Files Coverage Δ
src/_pytest/capture.py 93.42% <100%> (+0.02%) ⬆️
src/_pytest/main.py 96.88% <100%> (+0.59%) ⬆️
testing/test_stepwise.py 100% <100%> (ø)
src/_pytest/deprecated.py 100% <100%> (ø) ⬆️
src/_pytest/config/__init__.py 95% <100%> (+0.02%) ⬆️
src/_pytest/hookspec.py 100% <100%> (ø) ⬆️
testing/deprecated_test.py 100% <100%> (ø) ⬆️
src/_pytest/compat.py 96.87% <100%> (+0.1%) ⬆️
testing/test_cacheprovider.py 99.7% <100%> (ø) ⬆️
testing/test_conftest.py 99.61% <100%> (ø) ⬆️
... and 13 more

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update f2b9bbd...3d88d18. Read the comment docs.

@nicoddemus nicoddemus changed the base branch from features to master November 3, 2018 23:10
@nicoddemus
Copy link
Member Author

Changed the base as requested

@blueyed
Copy link
Contributor

blueyed commented Nov 4, 2018

AppVeyour failed again in the middle:

Build started
git clone -q https://github.com/pytest-dev/pytest.git C:\projects\pytest
git fetch -q origin +refs/pull/4297/merge:
git checkout -qf FETCH_HEAD
Error making request with Error Code Forbidden and Http Status Code Forbidden. No further error information was returned by the service.

I've not restarted it, I think we're good without it, especially since you can only restart all of the jobs (the whole build)?!

@nicoddemus nicoddemus merged commit d1c9c54 into pytest-dev:master Nov 4, 2018
@nicoddemus nicoddemus deleted the release-3.10.0 branch November 4, 2018 15:25
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

9 participants