-
Notifications
You must be signed in to change notification settings - Fork 132
Ensure that gcc path is only added once to DLL search path #678
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
Conversation
The suspense is killing me |
Look at the stack trace next. ;) |
I haven’t tested this but I personally don’t understand how this could fix the problem. Aren’t we bound to hit the same problem again if we the Windows runner has some weird and long path to gcc? |
@lucianopaz, I'm not protecting against long paths, I'm protecting against the path being added over and over again. |
Yes, I understand that, but I don’t understand why doing that prevents the error you were seeing with long path names. |
My hypothesis is simply that the error message is wrong. If you look at my stack trace, the path that triggered the error has quite an ordinary length. So I am hoping that when we encounter those absurdly long Conda prefix paths that we're only triggering the limit because we add it multiple times. Like I wrote above, I'm not sure this will solve the problem, but I suspect it might. |
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #678 +/- ##
=======================================
Coverage 80.76% 80.76%
=======================================
Files 162 162
Lines 46694 46698 +4
Branches 11420 11421 +1
=======================================
+ Hits 37711 37715 +4
Misses 6734 6734
Partials 2249 2249
|
I was working on #685 but when I run pre-commit locally, mypy fails with this message:
|
Hi @HarshvirSandhu, thanks for letting us know, but could you please provide more details? In particular, could you please provide the specific mypy error that is reported for This is a bit strange since I'm unable to reproduce it locally, and usually these things are caught by the automated tests. |
Hello @maresb and @HarshvirSandhu ,
pytensor/pytensor/link/c/cmodule.py Line 287 in bc3dda0
|
Thanks @Dhruvanshu-Joshi for the info! It seems quite mysterious why we are now seeing different results when mypy is run locally vs in the CI. (We see that the CI checks are failing in #702 after you added |
@maresb I am running mypy via pre-commit. Currently, I am using windows 11. |
As reported in <pymc-devs#678 (comment)>, mypy was failing on Windows due to an unnecessary type: ignore. This fixes it by ignoring the unused-ignore so that Windows is covered.
As reported in <#678 (comment)>, mypy was failing on Windows due to an unnecessary type: ignore. This fixes it by ignoring the unused-ignore so that Windows is covered.
Description
This is an attempt to solve
This is a wild guess at the cause since I don't have Windows, and it's appearing only in the PyMC test suite. In any case I think this is unlikely to hurt.
Related Issue
Checklist
Type of change