Matthew Barber

> Do we have reason to believe that it isn't enough to only accept > > * a test file (like `array_api_tests/test_special_cases.py`), > * a test name (like `array_api_tests/test_special_cases.py::test_binary`), or...

Well I don't think we're using tag-releases to emphasise stability, so much as using them as semantic breaks for when significant work has been done. Given that we shouldn't intentionally...

Also worth noting there is still uncertainty for some libraries in what namespace they'll publicly adopt the spec with (e.g. top-level like `pytorch` vs submodule like `numpy.array_api`). Think an example...

Relevant https://github.com/data-apis/array-api/issues/488

I still think this would be nice, but I think the test suite could do with some more refinement generally for this to be feasible, and even then doesn't seem...

Could we just change our own workflow to have `--hypothesis-max-examples=100`, instead of the default? As defo for something like JAX this makes it basically unusable on default runs :sweat_smile:

> A health check error generally indicates a bug in the test suite. It means we are filtering too much in one of the strategies. Yep, although when it comes...

Depends how, but yes. Specifying the test case externally (e.g. how we specify skips in CI), you'll need the unique test case id e.g. `array_api_tests/test_special_cases.py::test_iop[__ifloordiv__(x1_i is -0 and x2_i >...

> I'm attempting to implement a similar set of functions to [here down](https://github.com/data-apis/array-api-tests/blob/ddd3b7a278cd0c0b68c0e4666b2c9f4e67b7b284/conftest.py#L84) in the ivy conftest.py file. In principal, should this work? (currently not having any luck). Or is...

> Plain NumPy without the compat library fails because `np.asarray` doesn't have the copy keyword. Is that a requirement for the iop tests to work? Yep, on the in-place branch...