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
ERROR: test_big_arrays (test_io.TestSavezLoad) on OS X + Python 3.3 #3858
Comments
I can reproduce this. Looks like a Python 3.x bug.
The above works with Python 2.7 but not with 3.3:
Both Python are installed from the dmgs on python.org. I can't find an issue for this on bugs.python.org but IIRC the |
Test introduced in gh-2942. |
Or maybe this is another OSX I/O bug? Remember, OSX libc is buggy and has issues in fwrite/fread when dealing with data blocks close to 2**32, which we had to work around in tofile/fromfile... |
In any case, we obviously have to work around it by splitting up the write (Even if it's ultimately libc's fault, python should probably work around
|
Yes, we can work around it by chunking. Maybe this issue should also be forwarded to Python devs, so that they could also implement chunking themselves... |
Ah, forgot about those issues. Tried to test on my 10.6 machine, but there the same script just hangs. Could be due to the hardware though, it's an ancient machine. |
Is this a 1.8.0 blocker? I'm going to put it there just so it isn't forgotten, it can always be removed. Does anyone know if it works for Python 3.2? |
Also, IIRC, we've only chunked reads, it may be that a test that writes a large file is broken. |
I wouldn't hold up the release for this one, it's not a regression. Mark it knownfail though in the 1.8.x branch if it's not failed before the release. |
@rgommers Does if fail only with OSX and 3.3? You say that it works for python 2.7, is that correct? |
It doesn't fail for 2.7, but the test doesn't check that what's written to file is correct. It's likely not to be correct, see other issues that Pauli linked. |
@rgommers So OSX in general. I'll leave it open in 1.9-devel to motivate a fix and open an issue. |
This is reported fixed in OS X Mavericks. This is probably won't fix, as the proper fix is to upgrade the OS. See also #2931. |
Closing, should be fixed by Mavericks. Please reopen if the problem persists. |
This is still happening for me on Mavericks with numpy 1.8.1 and python 3.4 (also 3.3) from Anaconda; if I comment out the The test passes, and data appears to be loaded correctly, using python 2.7 from Anaconda. This isn't necessarily a flaw with numpy, but others appear to be working around this or similar issues, e.g. torch/DEPRECEATED-torch7-distro@40e6593 (which is for reading rather than writing, but I'm also unable to read large files on python 3). |
Running the testcase using Python 3.4 with numpy 1.8.1 on Mac OS X 10.9.4 (Mavericks) results in the known |
Another data point - using OSX 10.9.5 (Mavericks) and I get the same issue. I just saw this bug in the python tracker: https://bugs.python.org/issue24658 |
Might as well reopen this. I don't know if it will be fixed when Python solves their part, but we will find out. |
Happens here, latest macOS, python (3.6), and numpy. |
FYI Still seeing this bug on latest macOS (10.12.6) and Python 3.5.2 (Anaconda 4.2.0). |
Getting this error as well, macOS Sierra, python 3.6, numpy |
There looks to be some motion on the Python issue, but perhaps we should just go ahead and chunk the writes. |
Looks like this isn't going to get fixed upstream anytime soon. Anyone know the latest status? |
Hi all, Could you try this issue with the last version of Python 3.6, 3.7 and 3.8a because I think to have fixed the issue on OSX with this PR (python/cpython#1705). I have an other PR for 2.7, but this one is not yet ready :/ Thank you for your feedback. |
@rgommers Any chance you can test this? Any other feedback on the current status of this would be welcome. |
The |
@rgommers can you revisit this? |
This is indeed fixed as far as I can tell, at least with Python 3.7 from Anaconda. No other reports either, so closing. Thanks everyone, and @matrixise in particular for fixing this. |
Reported by Piet van Oostrum on the mailing list against 1.8.0rc1 on OS X with Python 3.3:
The text was updated successfully, but these errors were encountered: