Can we select tests in the tests directory selectively? I see the -T or --ticket option, but it doens't seem to find the test tagged with # ticket: <number here>. I can select unit tests using python runtests.py Cython.SubPackage.Tests.SomeTest, but I can't seem to do the same thing for tests in the tests directory. Running the entire suite takes rather long.
mark florisson, 11.04.2011 12:26:
Can we select tests in the tests directory selectively? I see the -T or --ticket option, but it doens't seem to find the test tagged with # ticket:<number here>.
I can select unit tests using python runtests.py Cython.SubPackage.Tests.SomeTest, but I can't seem to do the same thing for tests in the tests directory. Running the entire suite takes rather long.
You can still select them by name using a regex, e.g. runtests.py 'run\.empty_builtin_constructors' Stefan
On 11 April 2011 12:45, Stefan Behnel <stefan_ml@behnel.de> wrote:
mark florisson, 11.04.2011 12:26:
Can we select tests in the tests directory selectively? I see the -T or --ticket option, but it doens't seem to find the test tagged with # ticket:<number here>.
I can select unit tests using python runtests.py Cython.SubPackage.Tests.SomeTest, but I can't seem to do the same thing for tests in the tests directory. Running the entire suite takes rather long.
You can still select them by name using a regex, e.g.
runtests.py 'run\.empty_builtin_constructors'
Stefan _______________________________________________ cython-devel mailing list cython-devel@python.org http://mail.python.org/mailman/listinfo/cython-devel
Great, thanks! I'll update the hackerguide wiki.
On 11 April 2011 12:53, mark florisson <markflorisson88@gmail.com> wrote:
On 11 April 2011 12:45, Stefan Behnel <stefan_ml@behnel.de> wrote:
mark florisson, 11.04.2011 12:26:
Can we select tests in the tests directory selectively? I see the -T or --ticket option, but it doens't seem to find the test tagged with # ticket:<number here>.
I can select unit tests using python runtests.py Cython.SubPackage.Tests.SomeTest, but I can't seem to do the same thing for tests in the tests directory. Running the entire suite takes rather long.
You can still select them by name using a regex, e.g.
runtests.py 'run\.empty_builtin_constructors'
Stefan _______________________________________________ cython-devel mailing list cython-devel@python.org http://mail.python.org/mailman/listinfo/cython-devel
Great, thanks! I'll update the hackerguide wiki.
I see now that it is briefly mentioned there, apologies.
On Mon, Apr 11, 2011 at 3:56 AM, mark florisson <markflorisson88@gmail.com> wrote:
On 11 April 2011 12:53, mark florisson <markflorisson88@gmail.com> wrote:
On 11 April 2011 12:45, Stefan Behnel <stefan_ml@behnel.de> wrote:
mark florisson, 11.04.2011 12:26:
Can we select tests in the tests directory selectively? I see the -T or --ticket option, but it doens't seem to find the test tagged with # ticket:<number here>.
I can select unit tests using python runtests.py Cython.SubPackage.Tests.SomeTest, but I can't seem to do the same thing for tests in the tests directory. Running the entire suite takes rather long.
You can still select them by name using a regex, e.g.
runtests.py 'run\.empty_builtin_constructors'
Stefan _______________________________________________ cython-devel mailing list cython-devel@python.org http://mail.python.org/mailman/listinfo/cython-devel
Great, thanks! I'll update the hackerguide wiki.
I see now that it is briefly mentioned there, apologies.
I've added a note there about tags as well, and fixed the -T to look at the ticket tag. Note that "mode:run" is the default, so you don't need to explicitly tag mode except for compile/error tests. - Robert
Another, different but related issue: how can we get useful output from the test runner? e.g. I'm running my test with a '@cython.test_assert_path_exists("...")' and I get this error output: ====================================================================== ERROR: runTest (__main__.CythonRunTestCase) compiling (c) and running parallel ---------------------------------------------------------------------- Traceback (most recent call last): File "runtests.py", line 555, in run self.runCompileTest() File "runtests.py", line 386, in runCompileTest self.test_directory, self.expect_errors, self.annotate) File "runtests.py", line 532, in compile self.assertEquals(None, unexpected_error) AssertionError: None != u'9:0: Compiler crash in TreeAssertVisitor' So I'm seeing a traceback from the test runner (which I'm not really interested in :), but the actual traceback is not displayed. Can I also specify special link and compiler flags for a certain test, like in http://wiki.cython.org/enhancements/distutils_preprocessing ? Or do I have to export LDFLAGS and CFLAGS in my environment?
On Wed, Apr 13, 2011 at 4:07 AM, mark florisson <markflorisson88@gmail.com> wrote:
Another, different but related issue: how can we get useful output from the test runner? e.g. I'm running my test with a '@cython.test_assert_path_exists("...")' and I get this error output:
====================================================================== ERROR: runTest (__main__.CythonRunTestCase) compiling (c) and running parallel ---------------------------------------------------------------------- Traceback (most recent call last): File "runtests.py", line 555, in run self.runCompileTest() File "runtests.py", line 386, in runCompileTest self.test_directory, self.expect_errors, self.annotate) File "runtests.py", line 532, in compile self.assertEquals(None, unexpected_error) AssertionError: None != u'9:0: Compiler crash in TreeAssertVisitor'
So I'm seeing a traceback from the test runner (which I'm not really interested in :), but the actual traceback is not displayed.
I agree this could be improved, but I'm not sure the best way to do it.
Can I also specify special link and compiler flags for a certain test, like in http://wiki.cython.org/enhancements/distutils_preprocessing ? Or do I have to export LDFLAGS and CFLAGS in my environment?
You can't right now, but it would probably be worth adding. I'm not sure how we would handle missing dependancies in that case though. - Robert
participants (3)
-
mark florisson -
Robert Bradshaw -
Stefan Behnel