Skip to content

fix(test): support running our test suite under -trimpath, closes #397#439

Merged
klaernie merged 4 commits intomainfrom
trimpath
Mar 11, 2025
Merged

fix(test): support running our test suite under -trimpath, closes #397#439
klaernie merged 4 commits intomainfrom
trimpath

Conversation

@klaernie
Copy link
Copy Markdown
Member

@klaernie klaernie commented Feb 8, 2025

Thanks for @gkampitakis we can now support running the editorconfig-checker test suite with -trimpath.

@klaernie klaernie linked an issue Feb 8, 2025 that may be closed by this pull request
@klaernie
Copy link
Copy Markdown
Member Author

klaernie commented Feb 8, 2025

@xsy420, @orhun and @anjandev: I would welcome a review from you confirming that I did not overlook any problems that could occur in your build processes.

@xsy420
Copy link
Copy Markdown

xsy420 commented Feb 8, 2025

it build fine with my PKGBUILD after updating _commit variable to f57718a on my machine
and also in gitlab ci https://gitlab.archlinux.org/xsy420/editorconfig-checker-git/-/pipelines/119244
Thank you all

Copy link
Copy Markdown
Member

@theoludwig theoludwig left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Great! 😄

To clarify, does that mean that now editorconfig-checker can be compiled both with and without the -trimpath option? If we don't compile with -trimpath, it works too right?

Should we release a v3.2.1, as soon, as this is merged, to unblock Alpine Linux and other distributions?

@klaernie
Copy link
Copy Markdown
Member Author

klaernie commented Feb 9, 2025

To clarify, does that mean that now editorconfig-checker can be compiled both with and without the -trimpath option? If we don't compile with -trimpath, it works too right?

It will work with both with and without -trimpath.

Should we release a v3.2.1, as soon, as this is merged, to unblock Alpine Linux and other distributions?

Definitely.

This commit is guaranteed to be broken, since our code not yet handles
the caveats regarding the current working dir assumption that go-snaps
now has.
…lute path

Since we "tamper" with the current working directory to achieve a
certain output from files.GetRelativePath(), we now need to help
snaps find the __snapshots__ directory.
@klaernie
Copy link
Copy Markdown
Member Author

@mstruebing could I bother you for the final review?

Copy link
Copy Markdown
Member

@mstruebing mstruebing left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

build failure since #360

5 participants