[Numpy-svn] [numpy/numpy] c43a8f: TST: mark floating point error tests as unconditio...

[GitHub]

  Branch: refs/heads/maintenance/1.6.x
  Home:   https://github.com/numpy/numpy
  Commit: c43a8f282f66cf86cf30e56ef8efc61264fd6e86
      https://github.com/numpy/numpy/commit/c43a8f282f66cf86cf30e56ef8efc61264fd6e86
  Author: Ralf Gommers <ralf.gommers at googlemail.com>
  Date:   2012-05-19 (Sat, 19 May 2012)

  Changed paths:
    M numpy/core/tests/test_numeric.py

  Log Message:
  -----------
  TST: mark floating point error tests as unconditional knownfail.  See #1755.


  Commit: 3e1280678e5175794410f4bff30f771ad866b144
      https://github.com/numpy/numpy/commit/3e1280678e5175794410f4bff30f771ad866b144
  Author: Ralf Gommers <ralf.gommers at googlemail.com>
  Date:   2012-05-19 (Sat, 19 May 2012)

  Changed paths:
    M numpy/testing/nosetester.py

  Log Message:
  -----------
  BUG: fix running tests with coverage=True.

The --cover-inclusive argument means that coverage.py tries to include every
single .py file in the source tree in the coverage report. This leads to test
errors, because it tries to import files like setupscons.py (which will of
course directly fail for anyone not having numscons installed).

(backport of bfaaefe5)


  Commit: 5982e1b33d25e029429f52f181a868b70067b3b0
      https://github.com/numpy/numpy/commit/5982e1b33d25e029429f52f181a868b70067b3b0
  Author: Ralf Gommers <ralf.gommers at googlemail.com>
  Date:   2012-05-19 (Sat, 19 May 2012)

  Changed paths:
    M numpy/random/tests/test_random.py

  Log Message:
  -----------
  TST: for numpy.random test, back off test precision a little.

This test was reported to be failing once for 1.6.2rc1, test precision may be
set slightly too agressive.


Compare: https://github.com/numpy/numpy/compare/b6fac09...5982e1b