test_watch_multiple_dirs fails consistently
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 42/100
Research direction
Start with tests/test_watcher.py, especially test_watch_multiple_dirs at line 147, and run that test under the reported Python 2.7 and 3.7 environments. Trace why watcher.examine() does not return (first_path, None); done means the multiple-directory watcher test passes consistently on both versions.
Written by the indexing model from the issue text.
Description
Hello,
While trying to package v2.6.1 for NixOS (see https://github.com/NixOS/nixpkgs/pull/61905) I noticed that the latest addition to your test suite test_watch_multiple_dirs kept failing for both Python 2.7 and Python 3.7 builds.
The nosetests trace with debug is:
nose.suite: DEBUG: precache is [Test(<tests.test_watcher.TestWatcher testMethod=test_watch_dir>), Test(<tests.test_watcher.TestWatcher testMethod=test_watch_file>), Test(<tests.test_watcher.TestWatcher testMethod=test_watch_glob>), Test(<tests.test_watcher.TestWatcher testMethod=test_watch_ignore>), Test(<tests.test_watcher.TestWatcher testMethod=test_watch_multiple_dirs>)]
test_watch_dir (tests.test_watcher.TestWatcher) ... ok
test_watch_file (tests.test_watcher.TestWatcher) ... ok
test_watch_glob (tests.test_watcher.TestWatcher) ... ok
test_watch_ignore (tests.test_watcher.TestWatcher) ... ok
test_watch_multiple_dirs (tests.test_watcher.TestWatcher) ... FAIL
nose.suite: DEBUG: context teardown
nose.suite: DEBUG: ancestor <class 'tests.test_watcher.TestWatcher'> may need teardown
nose.suite: DEBUG: <nose.suite.ContextSuite context=TestWatcher> setup ancestor <class 'tests.test_watcher.TestWatcher'>
nose.suite: DEBUG: <nose.suite.ContextSuite context=TestWatcher> teardown context <class 'tests.test_watcher.TestWatcher'>
nose: DEBUG: call fixture <class 'tests.test_watcher.TestWatcher'>.tearDownClass
nose.suite: DEBUG: ancestor <module 'tests.test_watcher' from '/build/source/tests/test_watcher.py'> may need teardown
nose.suite: DEBUG: <nose.suite.ContextSuite context=tests.test_watcher> setup ancestor <module 'tests.test_watcher' from '/build/source/tests/test_watcher.py'>
nose.suite: DEBUG: ancestor <module 'tests' from '/build/source/tests/__init__.py'> may need teardown
nose.suite: DEBUG: <nose.suite.ContextSuite context=tests> setup ancestor <module 'tests' from '/build/source/tests/__init__.py'>
nose.suite: DEBUG: ancestor <class 'tests.test_watcher.TestWatcher'> may need teardown
nose.suite: DEBUG: ancestor <class 'tests.test_watcher.TestWatcher'> already torn down
nose.suite: DEBUG: context teardown
nose.suite: DEBUG: ancestor <module 'tests.test_watcher' from '/build/source/tests/test_watcher.py'> may need teardown
nose.suite: DEBUG: <nose.suite.ContextSuite context=tests.test_watcher> setup ancestor <module 'tests.test_watcher' from '/build/source/tests/test_watcher.py'>
nose.suite: DEBUG: <nose.suite.ContextSuite context=tests.test_watcher> teardown context <module 'tests.test_watcher' from '/build/source/tests/test_watcher.py'>
nose.suite: DEBUG: ancestor <module 'tests' from '/build/source/tests/__init__.py'> may need teardown
nose.suite: DEBUG: <nose.suite.ContextSuite context=tests> setup ancestor <module 'tests' from '/build/source/tests/__init__.py'>
nose.suite: DEBUG: ancestor <module 'tests.test_watcher' from '/build/source/tests/test_watcher.py'> may need teardown
nose.suite: DEBUG: ancestor <module 'tests.test_watcher' from '/build/source/tests/test_watcher.py'> already torn down
nose.suite: DEBUG: context teardown
nose.suite: DEBUG: ancestor <module 'tests' from '/build/source/tests/__init__.py'> may need teardown
nose.suite: DEBUG: <nose.suite.ContextSuite context=tests> setup ancestor <module 'tests' from '/build/source/tests/__init__.py'>
nose.suite: DEBUG: <nose.suite.ContextSuite context=tests> teardown context <module 'tests' from '/build/source/tests/__init__.py'>
nose.suite: DEBUG: ancestor <module 'tests' from '/build/source/tests/__init__.py'> may need teardown
nose.suite: DEBUG: ancestor <module 'tests' from '/build/source/tests/__init__.py'> already torn down
nose.suite: DEBUG: context teardown
nose.suite: DEBUG: No reason to teardown (was_setup? False was_torndown? False)
======================================================================
FAIL: test_watch_multiple_dirs (tests.test_watcher.TestWatcher)
----------------------------------------------------------------------
Traceback (most recent call last):
File "/build/source/tests/test_watcher.py", line 147, in test_watch_multiple_dirs
assert watcher.examine() == (first_path, None)
AssertionError
----------------------------------------------------------------------
Ran 5 tests in 3.099s
FAILED (failures=1)
I can't really figure out why it fails.
- Dominant language
- Python
- Stars
- 1.1k
- Forks
- 149
- PR merge metrics
- No merged PRs in 30d
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from lepture/python-livereload
-
Difficulty 1/5 Under an hour Newbie friendliness 70/100
lepture/python-livereload#159 · 3 reactions ·
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
lepture/python-livereload#288 ·
-
Difficulty 3/5 1-2 days Newbie friendliness 38/100
lepture/python-livereload#283 · 1 comment ·
-
Difficulty 4/5 3-5 days Newbie friendliness 25/100
lepture/python-livereload#282 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 25/100
lepture/python-livereload#279 ·
All issues in lepture/python-livereload
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
Kludex/python-multipart#375 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
Maintainers usually reply within 3 days
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
Maintainers usually reply within 11 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 80/100
FuRongJun-1999/dsh-memory#1000 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
gcivil-nyu-org/team5-mon-fall26#154 ·
Maintainers usually reply within 1 day