pytestbot
pytestbot
[GitMate.io](https://gitmate.io) thinks possibly related issues are https://github.com/pytest-dev/pytest/issues/3346 (Please error when fixtures conflict), https://github.com/pytest-dev/pytest/issues/2872 (mark fixtures ), https://github.com/pytest-dev/pytest/issues/2399 (marks should propogate through fixtures), https://github.com/pytest-dev/pytest/issues/2424 (dynamically generated fixtures), and https://github.com/pytest-dev/pytest/issues/3351 (Is there...
_Original comment by_ **Matthias Geier (BitBucket: [geier](http://bitbucket.org/geier), GitHub: [geier](http://github.com/geier))**: --- This would be a great feature! I found another (I don't know if more or less ugly) work-around: ``` #!python...
_Original comment by_ **Floris Bruynooghe (BitBucket: [flub](http://bitbucket.org/flub), GitHub: [flub](http://github.com/flub))**: --- Tentatively assigning this to me as I think I might be able to come up with a reasonable patch. It'll...
_Original comment by_ **Praveen Shirali (BitBucket: [praveenshirali](http://bitbucket.org/praveenshirali), GitHub: [praveenshirali](http://github.com/praveenshirali))**: --- The quoted examples work because functions `a` and `b` are part of the same module as `test_foo`, and within the...
_Original comment by_ **BitBucket: [dpwrussell](http://bitbucket.org/dpwrussell), GitHub: [dpwrussell](http://github.com/dpwrussell)**: --- This would be an awesome feature. @praveenshirali I don't think your alternative is used as a fixture, it just calls the fixture...
[GitMate.io](https://gitmate.io) thinks possibly related issues are https://github.com/pytest-dev/pytest/issues/1563 (All pytest tests skipped), https://github.com/pytest-dev/pytest/issues/251 (dont ignore test classes with a own constructor silently), https://github.com/pytest-dev/pytest/issues/1364 (disallow test skipping), https://github.com/pytest-dev/pytest/issues/149 (Distributed testing silently ignores...
[GitMate.io](https://gitmate.io) thinks possibly related issues are https://github.com/pytest-dev/pytest/issues/538 (Fixture scope documentation), https://github.com/pytest-dev/pytest/issues/805 (Fixture execution order ), https://github.com/pytest-dev/pytest/issues/668 (autouse fixtures break scope rules), and https://github.com/pytest-dev/pytest/issues/2846 (Unexpected order of tests using parameterized fixtures).
Original comment by @alfredodeza We have been able to get rid of these empty errors by closing `sys.stderr` and `sys.stdout` in ceph-deploy (see reference issue http://tracker.ceph.com/issues/7594 ) This is how...
Original comment by @RonnyPfannschmidt this one needs a reconsideration on bootstrapping, might take a while due to our own time cosntraints
Original comment by @danstender We have a fix for that: [https://sources.debian.net/src/execnet/1.4.1-3/debian/patches/test_gateway-fix-race-condition.patch/](https://sources.debian.net/src/execnet/1.4.1-3/debian/patches/test_gateway-fix-race-condition.patch/)