-
Notifications
You must be signed in to change notification settings - Fork 2.1k
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
chore: enable Swift CI tests #2838
Conversation
1e20edd
to
b97fca7
Compare
Signed-off-by: Martin Chodur <[email protected]>
b97fca7
to
158b13d
Compare
@GiedriusS PTAL |
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 looks good. Yes, every commit is the way we do it right now! (:
Co-authored-by: Bartlomiej Plotka <[email protected]> Signed-off-by: Giedrius Statkevičius <[email protected]>
8995cd2
to
f4d32ac
Compare
Flaky test, rerun |
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! Added @bwplotka's suggestion to your branch and then had to force push because, again, I fell into the trap of clicking "Commit suggestion" but without adding DCO 🤦
Added by thanos-io#2838. Signed-off-by: Giedrius Statkevičius <[email protected]>
Sorry for the lag I was on vacation. Thanks for fixing the typo and merging! :) |
Added by #2838. Signed-off-by: Giedrius Statkevičius <[email protected]>
Signed-off-by: Martin Chodur [email protected]
Added Swift CI tests as suggested in #2829
I'm not sure if it should run for every test? I'm not sure if we are somehow limited in the CircleCI usage.
From time perspective it does not significantly prolong the test stage in CI.