-
-
Notifications
You must be signed in to change notification settings - Fork 30.6k
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
test_future4 ran no test #79593
Comments
Since bpo-34279 has been fixed, regrtest now logs a message when a test runs no test. I noticed that test_future4 logs such message: ... I can reproduce the issue: $ ./python -m test test_future4
(...)
test_future4 run no tests
(...)
Tests result: NO TEST RUN The test has been added by:
diff --git a/Lib/test/test_future4.py b/Lib/test/test_future4.py
new file mode 100644
index 0000000000..805263be89
--- /dev/null
+++ b/Lib/test/test_future4.py
@@ -0,0 +1,10 @@
+"""This is a test"""
+import __future__
+from __future__ import nested_scopes
+
+def f(x):
+ def g(y):
+ return x + y
+ return g
+
+print f(2)(4) ... test removed by commit 3090694. A file recreated by: commit fa50bad
... I guess that it's related to: commit 3c60833
|
There are a few more on Windows: 4 tests run no tests: test_multiprocessing_fork and test_multiprocessing_forkserver should raise SkipTest on Windows. |
Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.
Show more details
GitHub fields:
bugs.python.org fields:
The text was updated successfully, but these errors were encountered: