yes, it makes sense to fix failing tests, they're real problems. You don't need to create the issue and you can just do the PR. This is the appropriate mailing list, but we work a lot through IRC On Sat, Jan 2, 2016 at 1:44 AM, Sergey Matyunin <sergeymatyunin@gmail.com> wrote:
Dear Maciej,
Thanks for the answer! Does it make sense to fix failing tests? Or may be they were left as is because they are irrelevant?
Do numpypy developers use these tests or some other tests? Does any guidelines exist for numpypy developers? Do I need to create an issue for each PR?
Is this maillist the right place for asking that questions?
On Fri, Jan 1, 2016 at 10:50 PM, Maciej Fijalkowski <fijall@gmail.com> wrote:
This is the actual state
On Fri, Jan 1, 2016 at 11:43 PM, Sergey Matyunin <sergeymatyunin@gmail.com> wrote:
Hello,
I am curious about the status of unit tests of numpy for pypy. Where can I get actual information about it?
I have installed pypy 4.0.1, numpypy for it (tag 4.0.1) and launched numpy tests using numpy.test() Looks like there is a plenty of failed tests:
Ran 4157 tests in 15.592s FAILED (KNOWNFAIL=5, SKIP=116, errors=648, failures=149)
Is it the actual state or may be I did something wrong?
-- Sergey _______________________________________________ pypy-dev mailing list pypy-dev@python.org https://mail.python.org/mailman/listinfo/pypy-dev
-- Sergey