Set Git messages to English for TestRemoteLoad_LocalProtocol

[arthurbdiniz]

This pull request ensures consistent error message matching by setting LC_ALL=C in TestRemoteLoad_LocalProtocol, preventing locale-based variations in Git output.

To reproduce the bug a variation of LOCALE can be set and to then run go test.

Variation

LC_ALL = et_EE.UTF-8
LANGUAGE = et_EE.UTF-8:fr

Test Error

=== RUN   TestRemoteLoad_LocalProtocol/repo_does_not_exist_
    remoteloader_test.go:301: 
        	Error Trace:	/tmp/reprotest.tT0OHI/const_build_path/const_build_path/_build/src/sigs.k8s.io/kustomize/api/krusty/remoteloader_test.go:301
        	Error:      	Expect "accumulating resources: accumulation err='accumulating resources from 'file:///not/a/real/repo': evalsymlink failure on '/tmp/kustomize-3177399597/file:/not/a/real/repo' : lstat /tmp/kustomize-3177399597/file:: no such file or directory': failed to run '/usr/bin/git fetch --depth=1 file:///not/a/real/repo HEAD': fatal : '/not/a/real/repo' does not appear to be a git repository
        	            	fatal : Impossible de lire le dépôt distant.
        	            	
        	            	Veuillez vérifier que vous avez les droits d'accès
        	            	et que le dépôt existe.
        	            	: exit status 128" to match "fatal: '/not/a/real/repo' does not appear to be a git repository"
        	Test:       	TestRemoteLoad_LocalProtocol/repo_does_not_exist_

Since git command is has internalization support it will print the git error messages in french.

[k8s-ci-robot]

Welcome @arthurbdiniz!

It looks like this is your first PR to kubernetes-sigs/kustomize 🎉. Please refer to our pull request process documentation to help your PR have a smooth ride to approval.

You will be prompted by a bot to use commands during the review process. Do not be afraid to follow the prompts! It is okay to experiment. Here is the bot commands documentation.

You can also check if kubernetes-sigs/kustomize has its own contribution guidelines.

You may want to refer to our testing guide if you run into trouble with your tests not passing.

If you are having difficulty getting your pull request seen, please follow the recommended escalation practices. Also, for tips and tricks in the contribution process you may want to read the Kubernetes contributor cheat sheet. We want to make sure your contribution gets all the attention it needs!

Thank you, and welcome to Kubernetes. 😃

[k8s-ci-robot]

Hi @arthurbdiniz. Thanks for your PR.

I'm waiting for a kubernetes-sigs member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[stormqueen1990]

/lgtm

[koba1t]

Hi @arthurbdiniz
Thanks for reporting that testcase doesn’t pass specific environment!
I think this PR is valuable to merge.

I'm concerned if the test cases in the other file will fail due to LOCALE.
Could you check whether the other test passes or not?

[koba1t]

/ok-to-test

[koba1t]

@arthurbdiniz

Thanks for your contribution!
/approve

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: arthurbdiniz, koba1t

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details

Needs approval from an approver in each of these files:

• OWNERS [koba1t]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment