-
Notifications
You must be signed in to change notification settings - Fork 45
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
CI updates #244
CI updates #244
Conversation
I get this error when I try to use this locally
|
Ah I think this is why |
Left by mistake whilst debugging
And move meta tests to top-level meta_tests folder
Only assert mixed sign scenarios when signbit() is available
And update skips file
Tests seem to work locally now. |
pytest has some seriously annoying limitations like this. It's a good thing we aren't trying to distribute the test suite as a package because this sort of thing would make doing that extremely difficult. |
One more thing, I've figured out how to limit examples for the tests marked with |
Feel free to merge this whenever you feel it is ready. |
This broke the array-api-compat CI. Fix at #245 |
How do you feel about adding these as required checks in the branch protection rules? Admins would still be able to bypass the checks if necessary, but it would making merging a PR that breaks the tests much less likely. |
Mind my ignorance on branch protection rules—what would we be adding as required checks exactly? The tests pasing? Or new tests for |
The tests for this repo. It isn't possible to require checks across repos. I went ahead and enabled it. You can go to https://github.com/data-apis/array-api-tests/settings/branch_protection_rules/22738169 to change the settings. |
--ci
flag & splits the meta tests into a seperate folder./meta_tests/
./array_api_tests/meta/
was a CI test anywhoconftest.py
hacksunvectorized
marker