-
Notifications
You must be signed in to change notification settings - Fork 702
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
[BUG] 2024.05.09 tests failing on Alpine Linux #5171
Comments
Should be fixed by 8c2775f |
Hey, thanks for fast reply. I continue to have 2 errors, not the same ones: https://paste.sr.ht/~stacyharper/f1352d92ed7e2dcb5fd438e96b8e06c56f8f3df8 |
Okay this one is probably related to my personal git configs, or git wrappers. But it is susprise me that it affect the tests. |
something like |
I got a wrap around git that might cause this: https://git.sr.ht/~stacyharper/dotfiles/tree/master/item/bin/git |
On Sat, May 11, 2024 at 07:51:35AM -0700, Willow wrote:
I got a wrap around git that might cause this: https://git.sr.ht/~stacyharper/dotfiles/tree/master/item/bin/git
yeah don't redefine the meaning of `git show`. Better use `git config`, or an alias, or name it something other than `git`
|
We should probably export EDIT: seems we already do that, how come this did not work ? Although we use GIT_CONFIG_NOSYSTEM which has been replaced in git 2.32 with GIT_CONFIG_SYSTEM |
It does work. But they overrode
|
Understood, I dont think we can do anything on Kakoune's side for that. I believe the rest of the tests should be fixed now. |
IIRC my problem was that it is currently not possible to define a different format for different git subcommands
The only solution would be to use /usr/bin/git but this then make it impossible for the user to wrap it. Maybe it is possible to do so just for the test suite? (ex: use a specific PATH) |
No. That's not a problem, it's a feature. You must never completely override You wouldn't override Again, what you want is either a different name or configure Git to do what you want, like:
This configuration mechanism does exactly the same thing except it's clearly scoped and can thus be feasibly overridden by our test suite which wants predictable behavior.
It's not that we can't do anything but we should not encourage users to break their systems.
Does that mean that they pass for you?
We should not circumvent |
Really, don't tell people what they wants... I never asked for your opinion. I don't even ask for a fix. I just pointed that in those situations, kakoune tests fails.
Really? Break their system? Right, anyway I don't want to continue debating with you. You've been rude here, and on the IRC channel too. |
That's a misunderstanding; in my book "what you want" means "this is how you can achieve the same thing without this problem" which I think is useful, factual information.
I was trying to share facts, not opinions.
Ok. If I were in your shoes I'd want to fix it.
Yes.
The main reason I was yelling is because I didn't think I got my point across.
This is the conversation
If I had spent more time I would have phrased my requests for information in a more elaborate way. |
I am sure we could work around your specific use case, but other wrapping issues would come out eventually and we would have to pile more and more brittle hacks to make those work. I'd rather assume that if Kakoune calls That said, in this specific case we expect a specific output format from git, and we assume this specific format will stay the default. It might be better to explicitely ask for it explicitely by adding a |
@krobelus Okay, I'm willing to pass. Let's forget this? Communication is hard, even more in open-source world. My last comment was rude too, so please accept my apology.
I agree with this. If this is an easy to add parameter in the test suite? I can't find the correct place to add it on |
Okay cool. The git-show command is defined in git.kak as
|
Version of Kakoune
v2024.05.09
Reproducer
We are bumping the Alpine Linux package recipe, but 2 tests are failing.
Outcome
Tests fails (edit-fifo-noscroll and blame-jump-message)
Expectations
Tests pass
Additional information
Here the
make check
output:https://paste.sr.ht/~stacyharper/87d16c81da7120ba760978d753d4cbe423b52f13
The text was updated successfully, but these errors were encountered: