test_watch_multiple_dirs fails consistently
Dieses Issue hat noch niemand übernommen.
Bewertung
- Schwierigkeit
- 3/5
- Geschätzter Aufwand
- 1-2 Tage
- Anfängerfreundlichkeit
- 42/100
Rechercherichtung
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.
Vom Indexierungsmodell aus dem Issue-Text verfasst.
Beschreibung
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.
- Vorherrschende Sprache
- Python
- Sterne
- 1.1k
- Forks
- 148
- PR-Merge-Kennzahlen
- Keine gemergten PRs in 30 T.
Entwicklungsumgebung
Dieses Projekt bietet weder Dev-Container noch Dockerfile noch Beitragsleitfaden – die Einrichtung liegt bei Ihnen. Beginnen Sie mit der README; die allgemeinen Schritte stehen in unserem Leitfaden für den ersten Beitrag.
Erste Schritte
- Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
- Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
- Forken Sie das Repository und arbeiten Sie in einem Branch.
- Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.
Mehr aus lepture/python-livereload
-
Schwierigkeit 1/5 Unter einer Stunde Anfängerfreundlichkeit 70/100
lepture/python-livereload#159 · 3 Reaktionen ·
-
Schwierigkeit 4/5 3-5 Tage Anfängerfreundlichkeit 35/100
lepture/python-livereload#288 ·
-
Schwierigkeit 3/5 1-2 Tage Anfängerfreundlichkeit 38/100
lepture/python-livereload#283 · 1 Kommentar ·
-
Schwierigkeit 4/5 3-5 Tage Anfängerfreundlichkeit 25/100
lepture/python-livereload#282 ·
-
Schwierigkeit 4/5 3-5 Tage Anfängerfreundlichkeit 25/100
lepture/python-livereload#279 ·
Alle Issues in lepture/python-livereload
Ähnliche Issues
-
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 82/100
microsoft/markitdown#2820 ·
Maintainer antworten meist innerhalb von 1 Tag
-
bug
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 66/100
Maintainer antworten meist innerhalb von 1 Tag
-
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 72/100
yt-project/yt#5624 ·
Maintainer antworten meist innerhalb von 1 Tag
-
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 72/100
-
bug
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 82/100
NousResearch/hermes-agent#148376 ·
Maintainer antworten meist innerhalb von 1 Tag