home / github / issues

Menu
  • GraphQL API
  • Search all tables

issues: 514808098

This data as json

id node_id number title user state locked assignee milestone comments created_at updated_at closed_at author_association active_lock_reason draft pull_request body reactions performed_via_github_app state_reason repo type
514808098 MDExOlB1bGxSZXF1ZXN0MzM0MzcwNzQw 3471 Restrict pytest to 'unit' tests (i.e. not hypothesis) 5635139 closed 0     5 2019-10-30T16:25:31Z 2019-10-31T14:29:09Z 2019-10-31T13:42:44Z MEMBER   0 pydata/xarray/pulls/3471

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

{
    "url": "https://api.github.com/repos/pydata/xarray/issues/3471/reactions",
    "total_count": 1,
    "+1": 1,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
    13221727 pull

Links from other tables

  • 0 rows from issues_id in issues_labels
  • 5 rows from issue in issue_comments
Powered by Datasette · Queries took 0.751ms · About: xarray-datasette