Skip to content

Conversation

blueyed
Copy link
Contributor

@blueyed blueyed commented Feb 13, 2019

No description provided.

pstradomski and others added 30 commits February 7, 2019 02:05
…n build directories that symlink to actual source.
The workaround was removed from the logging module by creating python
properties for verbosity related settings in the terminalreporter.

Closes: pytest-dev#4733
pytest.main: collect: factor out _visit_filter
Fix "ValueError: Plugin already registered" exceptions when running in build directories that symlink to actual source.
…etadata

Ignore pip-generated 'pip-wheel-metadata' folder [skip ci]
Remove terminal_reporter workaround from logging.py
Document junit_family option in the reference docs
tox: use deps for pluggymaster testenvs
This can spam a lot of warnings (per invocation), e.g.:

> lsof: WARNING: can't stat() nsfs file system /run/docker/netns/default
        Output information may be incomplete.

Or from Travis/MacOS:

> lsof: WARNING: can't stat() vmhgfs file system /Volumes/VMware Shared Folders
>       Output information may be incomplete.
>       assuming "dev=31000003" from mount table
While I think that pdb++ should be fixed in this regard (by using
`pdb.Pdb`, and not `self.__class__` maybe), this ensures that custom
debuggers like this are working.
…_and_file_in_args

Fix handling of pkg init and test file via args
flatten is an alias in more-itertools anyway
Constrain more_itertools for Python 2.7 compatibility
pdbpp: fix capturing with recursive debugging
Just a few environments for now to see how it will behave for a few days
@nicoddemus
Copy link
Member

/me waiting for GitHub Actions to try to do this automatically 😁

@blueyed
Copy link
Contributor Author

blueyed commented Feb 13, 2019

/me waiting for GitHub Actions to try to do this automatically 

How would this work?

In this case probably not anyway, since there were conflicts in tox.ini.

@nicoddemus
Copy link
Member

How would this work?

I didn't use GitHub Actions yet, but I think it could, after every merge to master, merge to features and open a PR.

In this case probably not anyway, since there were conflicts in tox.ini.

Oh yeah in that case we need to do it by hand.

@blueyed
Copy link
Contributor Author

blueyed commented Feb 13, 2019

I didn't use GitHub Actions yet, but I think it could, after every merge to master, merge to features and open a PR.

A bit too much probably, no?
I think it is good to just do it after releases etc.

@nicoddemus
Copy link
Member

A bit too much probably, no?

Possibly, but I suppose we can try to do that daily for example (if there are changes), but also we can try a few frequencies until we find the right spot.

@blueyed blueyed merged commit 1dbf440 into pytest-dev:features Feb 13, 2019
@blueyed blueyed deleted the merge-master-into-features branch February 13, 2019 19:23
@blueyed
Copy link
Contributor Author

blueyed commented Feb 13, 2019

Hmm, no codecov status/comment.. the site says that their service is partially degraded.

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.

7 participants