-
Notifications
You must be signed in to change notification settings - Fork 123
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
Update test time action #1219
Update test time action #1219
Conversation
I made some adjustment which hopefully let us know if the action is working as expected. I just ran the action (logs here #1124). Are the correct test jobs being logged now? Should we skip or not skip some still? |
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.
Looks good
What are we skipping right now? |
Py3.10 or float32 1 or Benchmark |
Perfect then! |
What about the numpy 2 distinction. Should be enough to include >2.0 and exclude the others. but the linked issue looked good... |
All of the py3.12 are using numpy>=2 to my knowledge. Should it be explicit filter? |
No, I just wanted to double check |
This will be outdated again by #1199 so we may want to wait? |
Anything to do on this? |
Thanks @wd60622 |
Description
Changes:
Related Issue
Checklist
Type of change
📚 Documentation preview 📚: https://pytensor--1219.org.readthedocs.build/en/1219/