Fail lazygit integration/component test for 0.64.1 and 0.65.0 release tarballs

[band-a-prend]

Describe the bug

I'm prepared the update for Gentoo dev-vcs/lazygit-0.64.1 and -0.65.0 (guru repository) package and ran tests via build scrips with command go test ./... -short as usual and got an error message:

...
ok      github.com/jesseduffield/lazygit/pkg/i18n       0.075s
ok      github.com/jesseduffield/lazygit/pkg/integration/clients        0.062s
?       github.com/jesseduffield/lazygit/pkg/integration/clients/injector       [no test files]
2026/09/06 23:21:32 must run in lazy project folder or child folder
FAIL    github.com/jesseduffield/lazygit/pkg/integration/components     0.062s
?       github.com/jesseduffield/lazygit/pkg/integration/tests  [no test files]
?       github.com/jesseduffield/lazygit/pkg/integration/tests/bisect   [no test files]
?       github.com/jesseduffield/lazygit/pkg/integration/tests/branch   [no test files]
?       github.com/jesseduffield/lazygit/pkg/integration/tests/cherry_pick      [no test files]
?       github.com/jesseduffield/lazygit/pkg/integration/tests/commit   [no test files]
?       github.com/jesseduffield/lazygit/pkg/integration/tests/config   [no test files]
?       github.com/jesseduffield/lazygit/pkg/integration/tests/conflicts        [no test files]
?       github.com/jesseduffield/lazygit/pkg/integration/tests/custom_commands  [no test files]
?       github.com/jesseduffield/lazygit/pkg/integration/tests/demo     [no test files]
?       github.com/jesseduffield/lazygit/pkg/integration/tests/diff     [no test files]
?       github.com/jesseduffield/lazygit/pkg/integration/tests/file     [no test files]
?       github.com/jesseduffield/lazygit/pkg/integration/tests/filter_and_search        [no test files]
?       github.com/jesseduffield/lazygit/pkg/integration/tests/filter_by_author [no test files]
?       github.com/jesseduffield/lazygit/pkg/integration/tests/filter_by_path   [no test files]
?       github.com/jesseduffield/lazygit/pkg/integration/tests/interactive_rebase       [no test files]
?       github.com/jesseduffield/lazygit/pkg/integration/tests/misc     [no test files]
?       github.com/jesseduffield/lazygit/pkg/integration/tests/patch_building   [no test files]
?       github.com/jesseduffield/lazygit/pkg/integration/tests/reflog   [no test files]
?       github.com/jesseduffield/lazygit/pkg/integration/tests/remote   [no test files]
?       github.com/jesseduffield/lazygit/pkg/integration/tests/shared   [no test files]
?       github.com/jesseduffield/lazygit/pkg/integration/tests/shell_commands   [no test files]
?       github.com/jesseduffield/lazygit/pkg/integration/tests/staging  [no test files]
?       github.com/jesseduffield/lazygit/pkg/integration/tests/stash    [no test files]
?       github.com/jesseduffield/lazygit/pkg/integration/tests/status   [no test files]
?       github.com/jesseduffield/lazygit/pkg/integration/tests/submodule        [no test files]
?       github.com/jesseduffield/lazygit/pkg/integration/tests/sync     [no test files]
?       github.com/jesseduffield/lazygit/pkg/integration/tests/tag      [no test files]
?       github.com/jesseduffield/lazygit/pkg/integration/tests/ui       [no test files]
?       github.com/jesseduffield/lazygit/pkg/integration/tests/undo     [no test files]
?       github.com/jesseduffield/lazygit/pkg/integration/tests/worktree [no test files]
?       github.com/jesseduffield/lazygit/pkg/integration/types  [no test files]
?       github.com/jesseduffield/lazygit/pkg/jsonschema [no test files]
?       github.com/jesseduffield/lazygit/pkg/logs       [no test files]
?       github.com/jesseduffield/lazygit/pkg/logs/tail  [no test files]
ok      github.com/jesseduffield/lazygit/pkg/snake      0.049s
ok      github.com/jesseduffield/lazygit/pkg/tasks      1.611s
ok      github.com/jesseduffield/lazygit/pkg/theme      0.075s
?       github.com/jesseduffield/lazygit/pkg/updates    [no test files]
ok      github.com/jesseduffield/lazygit/pkg/utils      0.022s
ok      github.com/jesseduffield/lazygit/pkg/utils/yaml_utils   0.013s
FAIL

To Reproduce

Steps to reproduce the behavior:

1. Get lazygit-0.65.0 Source code (tar.gz) tarball from release page, unpack and go into the lazygit-0.65.0 directory
2. Build the lazygit with command go build -o "bin/lazygit" -ldflags "-X main.version=0.65.0"
3. Run tests with command go test ./... -short
4. See the error message:

2026/09/06 23:21:32 must run in lazy project folder or child folder
FAIL    github.com/jesseduffield/lazygit/pkg/integration/components     0.062s

Expected behavior

All tests are passed

Version info: 0.64.1 and 0.65.0

Terminal info:

What terminal are you using, and which version? For some types of bugs this information can be relevant.
I used konsole terminal.

Additional context

There is no similar error for tests with lazygit-0.64.0 or early version tarballs. When build from fetched github release-commit / latest commit master (c07f4d) there's no the same isssue. Is the message must run in lazy project folder or child folder related to this failed github.com/jesseduffield/lazygit/pkg/integration/components test? How could I skip this test or should this test is moved from "short" set?

Note

Please try updating to the latest version or manually building the latest master to see if the issue still occurs.

[stefanhaller]

I opened #6003 to fix this, and allow running all tests from a tarball, including integration tests.

Of course this doesn't help you for 0.64.1 and 0.65.0, it only helps for future releases. For these two, you can work around it with a simple mkdir .git in the extracted tarball.

BTW, the recommended way to run tests before building a package is ./scripts/check_commit.sh.

[band-a-prend]

@stefanhaller
Great thanks! I add the creation of empty .git directory before test running into build script and tests are OK now.

BTW, the recommended way to run tests before building a package is ./scripts/check_commit.sh

It's slightly difficult to do with Gentoo build system as it's use certain order and expects tests after ending of build process.

[stefanhaller]

Ah no, I didn't mean before the build process, you can run it afterwards. It doesn't matter actually. But I see that it requires the "just" utility which you may not have. The script simply runs two more checks in addition to running the tests: it checks the linter, and whether auto-generated files are up to date. Not sure you care about either when building your package.

Anyway, go test ./... should be fine too, but I'd leave out the -short so that it also runs integration tests.