-
-
Notifications
You must be signed in to change notification settings - Fork 4
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
Added nanobind to test suite #44
Conversation
Okay, looks like it's working! The tests are of course failing, but that's the failure I had reported. |
Curiously, there is a more complex failure pattern: some tests are reporting this error message In other cases, the whole interpreter crashes without writing an error message |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It seems like pypy3.10 segfaults. Let's let the nightlies run and see if it still happens.
Windows is failing to find the c-extensions. |
Now everything fails the proper way even on Windows ;) |
Reran the jobs to pick up new nightlies. There is now a new internal test failure from a test with this comment “taken from https://github.com/wjakob/pypy_issues at commit 03890103”, maybe now PyPy behaves the same as cpython? |
The windows build bot is down, so the results did not change. That 3.10 segfault is weird. |
CI is green, merging. Thanks @wjakob |
Thank you 🙇 |
This PR adds nanobind to the PyPy test suite. Let's see 🤞