Skip to content
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

Automate benchmarking and update benchmarks #356

Merged
merged 1 commit into from
Jun 15, 2018
Merged

Automate benchmarking and update benchmarks #356

merged 1 commit into from
Jun 15, 2018

Conversation

nex3
Copy link
Contributor

@nex3 nex3 commented Jun 15, 2018

Closes #293

@nex3 nex3 requested a review from jmesserly June 15, 2018 01:34
Copy link

@jmesserly jmesserly left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM! super cool to have automated benchmarks checked in

await runAsync("git",
arguments: ["fetch", "origin"], workingDirectory: path);
await runAsync("git",
arguments: ["reset", "--hard", "origin/master"],

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This can be a bit destructive on your local changes, if you ran it by accident. Not only to the working tree but also to the current branch pointer. I wonder if it'd be worth a git checkout origin/master just to be safe, so it'd error out if you had local changes.

Since it's only used for other sass impl repos it's probably pretty safe even so, but just wondering if the extra level of reset --hard is necessary.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

checkout doesn't update the local master branch's pointer, which I worry could hypothetically mess up some infrastructure. These repositories are all in the build/ directory anyway, which is generally expected to be destructively modified by grinder tasks, so I don't feel too bad about doing that here as well.

@nex3 nex3 merged commit 048cbe1 into master Jun 15, 2018
@nex3 nex3 deleted the benchmark branch June 15, 2018 18:29
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants