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
archive/tar: Example_sparseAutomatic and TestSparseEntries fails on iOS #21970
Comments
I'm trying to debug this issue, but I'm not sure how invoke the failing tests manually on iOS using gomote. I tried doing the following:
Do you have any ideas? |
I couldn't even get gomote as far as you did, so I debugged to issue manually. The problem seems to be that on darwin, the values of SEEK_HOLE and SEEK_DATA are swapped(!):
I confirmed that this change fixes the build on darwin/arm64 (but will obviously fail on every other unix):
|
You got to be freaking kidding me... Solaris invents SEEK_HOLE and SEEK_DATA and most Unix systems have since adopted the same convention with the same definition and semantics (for the most part). It seems utterly insane for Darwin to decide to change it up. \cc @rasky, do you know if High Sierra has these same (reversed) definitions of SEEK_HOLE and SEEK_DATA? It seems like a major mistake for Apple to switch these values up. Almost seems like a typo on their part. |
Change https://golang.org/cl/65570 mentions this issue: |
Confirmed, they're swapped in High Sierra as well. Example_sparseAutomatic was failing on High Sierra just like iOS. I mailed the fix. |
FWIW, I could only reproduce the Example_sparseAutomatic failure on high sierra. I don't know if the patch also fixes TestSparseEntries on iOS. |
The iOS builders are passing now, so I think it's safe to say it's fixed. Thanks. |
The iOS builders are currently failing with:
This test was added when implementing support for sparse files hole detection and punching. On OS+FS that do not support sparse files (such as iOS),
Example_sparseAutomatic
should still produce a non-sparse file, whose content matches the source file. However, the test is indicating that the contents differ for unknown reasons.The text was updated successfully, but these errors were encountered: