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
gh-101334: Don't force USTAR format in test_tarfile. #101572
Conversation
That causes the test to fail when run using a high UID as that ancient format cannot represent it. The current default (PAX) and the old default (GNU) both support high UIDs.
|
!buildbot aarch64 Debian Clang |
|
!buildbot aarch64 Debian.* |
|
!buildbot aarch64 |
|
The command will test the builders whose names match following regular expression: The builders matched are:
|
|
Thanks @gpshead for the PR, and @ethanfurman for merging it |
|
Sorry @gpshead and @ethanfurman, I had trouble checking out the |
|
GH-101583 is a backport of this pull request to the 3.10 branch. |
|
Thanks @gpshead for the PR, and @ethanfurman for merging it |
|
GH-101584 is a backport of this pull request to the 3.11 branch. |
That causes the test to fail when run using a high UID as that ancient format cannot represent it. The current default (PAX) and the old default (GNU) both support high UIDs. (cherry picked from commit ffcb822) Co-authored-by: Gregory P. Smith <greg@krypto.org>
That causes the test to fail when run using a high UID as that ancient format cannot represent it. The current default (PAX) and the old default (GNU) both support high UIDs. (cherry picked from commit ffcb822) Co-authored-by: Gregory P. Smith <greg@krypto.org>
|
That causes the test to fail when run using a high UID as that ancient format cannot represent it. The current default (PAX) and the old default (GNU) both support high UIDs.