-
Notifications
You must be signed in to change notification settings - Fork 17.9k
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: TestSparseFiles failing on plan9/arm builder #21977
Comments
The test is only failing on the plan9/arm builder because this builder use the Fossil file system for /tmp instead of ramfs. It seems there is an issue with the handling of sparse files in the Fossil file system. |
Change https://golang.org/cl/65352 mentions this issue: |
CL 60871 added TestSparseFiles. This test is succeeding on Plan 9 when executed on the ramfs file system, but is failing when executed on the Fossil file system. This may be due to an issue in the handling of sparse files in the Fossil file system on Plan 9 that should be investigated. Updates #21977. Change-Id: I177afff519b862a5c548e094203c219504852006 Reviewed-on: https://go-review.googlesource.com/65352 Reviewed-by: Ian Lance Taylor <[email protected]>
I'll investigate why this is failing on Plan9. On OS without sparse file support, this test should still pass. It does however rely on being able to |
TestSparseFiles was removed in 2017 by CL 78030. |
That assumption does not hold for |
CL 60871 added TestSparseFiles. This test is failing on the plan9/arm builder.
See https://build.golang.org/log/6c62187355a860390505342ac82661184645f959
The text was updated successfully, but these errors were encountered: