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

looponfail output issues w/ looponfailroots #51

Open
2 tasks
aljosa opened this issue Mar 3, 2016 · 0 comments
Open
2 tasks

looponfail output issues w/ looponfailroots #51

aljosa opened this issue Mar 3, 2016 · 0 comments

Comments

@aljosa
Copy link

aljosa commented Mar 3, 2016

when using xdist "-f, --looponfail" and large number of "looponfailroots" folders is set, output in shell is almost useless because you need to scroll each time something changes.

example output, some content removed:

### LOOPONFAILING ###
unit/test_...
### waiting for changes ###
### Watching:   ...
### Watching:   ...
### Watching:   ...
### Watching:   ...
### Watching:   ...
### Watching:   ...
### Watching:   ...
### Watching:   ...
### Watching:   ...
### Watching:   ...
### Watching:   ...
### Watching:   ...
### Watching:   ...
### Watching:   ...
### Watching:   ...
### Watching:   ...
### Watching:   ...
### Watching:   ...
### Watching:   ...
### Watching:   ...
### Watching:   ...
### Watching:   ...
### Watching:   ...
### Watching:   ...
### Watching:   ...
### Watching:   ...
### Watching:   ...
### Watching:   ...
### Watching:   ...
### Watching:   ...
### Watching:   ...

a somewhat expected response would be to set less roots and rearrange project or that i'm doing something wrong.
here is a simple example why this is irrelevant:
a project using python and javascript can have various workers generating data and logs which all trigger looponfail.

possible solutions:

  • allow regex(s) to specify which files/folders should be watched
  • display "Watching ..." for looponfailroots only once when "py.test -f" starts
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants