pull_requests: 334370740
This data as json
| id | node_id | number | state | locked | title | user | body | created_at | updated_at | closed_at | merged_at | merge_commit_sha | assignee | milestone | draft | head | base | author_association | auto_merge | repo | url | merged_by |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 334370740 | MDExOlB1bGxSZXF1ZXN0MzM0MzcwNzQw | 3471 | closed | 0 | Restrict pytest to 'unit' tests (i.e. not hypothesis) | 5635139 | Currently Azure is running hypothesis tests in any test job that has hypothesis installed (found in https://github.com/pydata/xarray/pull/3285). This isn't required, since we have a separate job for hypothesis, and slows down the normal tests. We can either exclude it in the test job or in the tests that pytest runs as specified in `setup.cfg` I think adjusting pytest's test paths in `setup.cfg` is a more logical place: pytest is responsible for running normal / unit tests in `xarray/tests`, and hypothesis can run the tests in `properties` | 2019-10-30T16:25:31Z | 2019-10-31T14:29:09Z | 2019-10-31T13:42:44Z | a570e878fdb1f3f9302175ea4f71cc092032e156 | 0 | 9a9f3d9024ab7c577be24547f78ee87f526382bf | 59f88f776f290f216531d074b6e73a50a9f7c37c | MEMBER | 13221727 | https://github.com/pydata/xarray/pull/3471 |
Links from other tables
- 0 rows from pull_requests_id in labels_pull_requests