-
-
Notifications
You must be signed in to change notification settings - Fork 422
[skip changelog] Refactor and add TEST_LDFLAGS
to test-unit-race
and test-legacy
tasks
#1417
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
Conversation
@per1234 do you think that this is worth to port somehow in our asset repo?
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.
It must be proof that nobody ever ran the test-unit-race
task. Should we use the -race
flag when the CI runs the unit tests? I guess it will make them take a little longer, but it doesn't seem to be significant, especially since the unit tests will always finish way before the integration test workflow run.
Should we use the -race flag when the CI runs the unit tests?
Sounds reasonable to me, I'll open another PR after discussing it with @cmaglie and @silvanocerza 👍
Please check if the PR fulfills these requirements
before creating one)
our contributing guidelines
UPGRADING.md
has been updated with a migration guide (for breaking changes)The PR adds the
TEST_LDFLAGS
totest-unit-race
andtest-legacy
tasksThe task
test-unit-race
was failing in checking if the correct version parameter are passed correctly during build time here https://github.com/arduino/arduino-cli/blob/master/version/version_test.go#L29Passing now to the task commands the
TEST_LDFLAGS
, the test runs successfullytitled accordingly?
Bonus: Bumped the go version in the
go.mod
to 1.16 here c3358a0See how to contribute