| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
| |
It's not always possible to guarantee this, so also adds a test to verify that we don't hang
|
| |
|
|
|
|
|
|
|
| |
An example output for the test added in the previous commit is:
AssertionError: Reference cycles were found when calling make_cycle: 1 objects were collected, of which 1 are shown below:
list object with id=2279664872136:
[<Recursion on list with id=2279664872136>,
<Recursion on list with id=2279664872136>]
|
| |
|
|
|
|
| |
This also means we can now test that our test is actually able to detect the type of failure we expect
Trying to give myself some tools to debug the failure at https://github.com/numpy/numpy/pull/10882/files#r180813166
|
| |
|
|
|
|
|
|
| |
* Make PytestTester callable.
* Rename 'timer' to 'durations', corresponding with pytest.
* Offset 'verbose', no entry is now '-q'.
* Move some `ignore` warnings into PytestTester so that they
affect releases, not just develop.
|
| |
|
|
|
|
| |
[ci skip]
This is not used yet, but has been tested with temporary changes
and works.
|
| |
|
| |
Found via `codespell -q 3 -I ../numpy-whitelist.txt`
|
|
|
This is to prepare for the switch to pytest.
* Rename `numpy/testing/nose_tools` to `numpy/testing/_private`.
* Redirect imports as needed.
* Copy `_testutils.py` from scipy to `numpy/testing/_private`.
* Rename `_testutils.py` to `_pytester.py` and remove unneeded bits.
|
