Golang: Remaining test case are stopped when adding fmt.Printf for console log purpose

[jawahar273]

Using Printf function from fmt has stopping remaining running test case and allowed for submit which lead to false positive case.

Link: https://exercism.org/tracks/go/exercises/need-for-speed

[github-actions]

Hi and welcome to Exercism! 👋

We have a community forum which is the correct place to most the majority of requests:

• Get help in Exercism Support.
• Report bugs or suggest improvements in Bugs & Feature Requests.

If you are suggesting a new feature or an improvement to Exercism, we also suggest taking a read of this post first.

Unless this issue has been pre-approved (or you are part of the Exercism Team) it will likely be closed without a response. See you in the forum!

[github-actions]

Hello. Thanks for opening an issue on Exercism. We are currently in a phase of our journey where we have paused community contributions to allow us to take a breather and redesign our community model. You can learn more in this blog post. As such, all issues and PRs in this repository are being automatically closed.

That doesn't mean we're not interested in your ideas, or that if you're stuck on something we don't want to help. The best place to discuss things is with our community on the Exercism Community Forum. You can use this link to copy this into a new topic there.

---

Note: If this issue has been pre-approved, please link back to this issue on the forum thread and a maintainer or staff member will reopen it.

[SleeplessByte]

@ErikSchierboom you probably want to move this to go-test-runner

[github-actions]

Hello. Thanks for opening an issue on Exercism. We are currently in a phase of our journey where we have paused community contributions to allow us to take a breather and redesign our community model. You can learn more in this blog post. As such, all issues and PRs in this repository are being automatically closed.

That doesn't mean we're not interested in your ideas, or that if you're stuck on something we don't want to help. The best place to discuss things is with our community on the Exercism Community Forum. You can use this link to copy this into a new topic there.

---

Note: If this issue has been pre-approved, please link back to this issue on the forum thread and a maintainer or staff member will reopen it.

[junedev]

@jawahar273 We are aware of this problem and there is already an issue for it here: #6
Go 1.20 shipped improvements for the json output so potentially updating the Go version might already help.