-
-
Notifications
You must be signed in to change notification settings - Fork 402
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
Using Apple-Git breaks make check in dulwich #1188
Comments
Can you provide the error output? |
Will do. Most are KeyErrors for missing b'Head' and others are revparse head not returning an sha. It is almost as if the fast-import of the testdata repo .export files is broken. Using git from git/git passes all tests. |
Here is the log from running make check using Apple-Git. With normal git, everything passes:
|
With normal git:
|
Thanks; nothing immediately jumps out that might be the cause of the breakage. There are no relevant changes between 2.39.2 and 2.39.3 that I can see: https://github.com/git/git/blob/master/Documentation/RelNotes/2.39.3.txt And the Apple-git specific changes also don't appear to be relevant: |
Yes, I looked for about an hour, even managed to add progress and checkpoint commands to the testdata/repos/ .export files and checked that "progress done" was emitted by apple-git when it did the fast-import. It was. But the tests still failed. I even modded the tests/compat/utils.py file to not do a clean up and manually printed out the repo.path in /var/tmp so that I could look there and all appeared to be fine. I am not sure why this is happening. But thought you might want to warn other mac users about the need to use real git when running the dulwich make check just to prevent incorrect bug reports. |
FYI,
I was testing some changes and I was playing with dulwich make check to verify that I broke nothing and came across the following irregularity:
Using straight dulwich master from today (and all recent earlier ones I have tested), If I use Apple's installed /usr/bin/git (ie. Apple-Git that comes with Xcode) to run make check there are 40 errors and 7 fails all related to tests that use "fast-import". This is with the very latest versions of Xcode on Monterrey and Ventura versions of macOS.
I tried with my Manjaro linux vm and all worked like a charm.
So I grabbed the latest real git source release tag and built it on my macOS machine and make check now passes all tests (skipping 82 with 1 expected fail).
So something related to Apple's supplied git has broken something related to "fast import" which I have been unable to track down (and frankly it is not worth any extra time). IMHO, Apple should not be forking tools like git just to make it work better with its horrible Xcode.
So perhaps for macOS users of dulwich interested in testing you could mention in your test docs or in a readme that they must use MacPorts git or Homebrew git or simply tell them to build git themselves. But not to use the built in git (Apple-Git from the Xcode tools) for running make check.
Hope this helps.
Kevin
The text was updated successfully, but these errors were encountered: