-
-
Notifications
You must be signed in to change notification settings - Fork 2.8k
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
Typeshed CI tests fail with error about __add__ vs. __iadd__ #1254
Comments
I've never seen this before. Do you think that it's possible to reproduce this issue with an empty Python file that only depends on builtins, typing and/or abc? If so, it shouldn't be too hard to manually verify the potential places where hash seed could make a difference. |
Sadly I've not been able to repro this yet. I'll keep an eye open. |
Another theory: it may depend on the order in while os.listdir() returns the files in a package. The traveis tests run on Linux, I only test on OSX. I think OSX returns files in sorted order. |
Should we sort the result of |
This was because runtests.py passes typing.pyi on the command line before builtins.pyi. I've checked in a hack for typeshed/runtests.py but we need to leave this open for a better fix. It's rstill reproducible as follows:
|
I cannot seem to replicate @gvanrossum's error using that command. Perhaps this has been fixed? |
On the other hand, the same command for Python 2:
crashes with:
|
The latter crash however is a duplicate of #2386. So that I think we can close this. |
Example: https://travis-ci.org/python/typeshed/builds/112511679
The specific error is:
I cannot repro this locally and the Travis CI tests pass when the PR is merged: https://travis-ci.org/python/typeshed/builds/112653577
I've seen this error before but only in my "incremental" branch. It's pretty shy -- sometimes I get it consistently, sometimes it's irreproducible (in fact I haven't seen it in a while). I think the cause of the error is a subtlety in the order in which the import cycle (builtins, typing, abc) is type-checked. My theory is that in my branch the processing order is dependent on Python's hash seed; but I've also made some subtle changes to the processing of cycles in that branch.
I have two hypotheses about why this is now happening in the Travis CI tests for typeshed:
The text was updated successfully, but these errors were encountered: