-
Notifications
You must be signed in to change notification settings - Fork 4
feat: support pinning the codspeed-go-runner #176
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
adriencaccia
left a comment
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.
As seen together, let's keep the installation of the go-runner inside codspeed
6b8f638 to
11a039a
Compare
|
@not-matthias can you rebase so we ensure the tests are passing? |
1e5c627 to
d485ec8
Compare
|
I'll remove the memory tests for now and create a new issue to not block this PR (because it looks like we need some changes in the memtrack CLI to support some of the cmds) |
d485ec8 to
6f9134f
Compare
adriencaccia
left a comment
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 should be documented in the readme as well
6f9134f to
1d194bb
Compare
1d194bb to
dfb7340
Compare
|
Good catch. Also updated the description to match the one in the runner |
(the failing tests are only due to memory which doesn't support
allow-emptyat the moment, was fixed in CodSpeedHQ/codspeed#205)Depends on
CodSpeedHQ/codspeed#213#178