-
-
Notifications
You must be signed in to change notification settings - Fork 512
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
fix: use correct path for gotestsum output #1287
fix: use correct path for gotestsum output #1287
Conversation
✅ Deploy Preview for testcontainers-go ready!
To edit notification comments on pull requests, go to your Netlify site settings. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Pending the final approval to the rollback of the indents, but other than that, LGTM! Thanks for the quick fix! 👏
…ithub.com/sebastianbuechler/testcontainers-go into fix-use-correct-path-for-gotestsum-output
Reverted the linting. Thanks for the package! |
The unit test that is failing is https://github.com/testcontainers/testcontainers-go/blob/main/modulegen/main_test.go#LL479C46-L479C55 It covers that the templates are properly rendered for each module. Would you mind updating the test too? 🙏 |
Kudos, SonarCloud Quality Gate passed! 0 Bugs No Coverage information |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM! Thanks for detecting this subtle bug and proposing a quick fix! Much appreciated 👏
What does this PR do?
Use the correct path for the gotestsum output in the module-postgres pipeline
Why is it important?
It's broken.
Related issues
How to test this PR
Check module-postgres pipeline
Follow-ups
If this fix works we can check other pipelines as well if they need a fix too.