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

Fix benchmark script #154

Merged
merged 1 commit into from
Oct 23, 2017
Merged

Fix benchmark script #154

merged 1 commit into from
Oct 23, 2017

Conversation

zamotany
Copy link
Contributor

Fixes #153

@zamotany zamotany requested a review from satya164 October 23, 2017 12:05
@@ -12,17 +12,18 @@ const resultsTable = new Table({
colWidths: [60, 10, 10],
});

const outDir = path.join(__dirname, 'suites/_temp');
const outDir = 'benchmark/_temp';
Copy link
Member

@satya164 satya164 Oct 23, 2017

Choose a reason for hiding this comment

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

maybe path.join(__dirname, 'benchmark', '_temp'); ?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

outDir must be relative to CWD

@codecov
Copy link

codecov bot commented Oct 23, 2017

Codecov Report

Merging #154 into master will not change coverage.
The diff coverage is n/a.

Impacted file tree graph

@@           Coverage Diff           @@
##           master     #154   +/-   ##
=======================================
  Coverage   97.52%   97.52%           
=======================================
  Files          19       19           
  Lines         404      404           
  Branches       81       81           
=======================================
  Hits          394      394           
  Misses         10       10

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update d1c7562...6291e43. Read the comment docs.

@satya164
Copy link
Member

Maybe we should add a snapshot test for the benchmark.

  • When someone makes changes, they'll be aware of the perf impact
  • Will make sure that the script keeps working

@zamotany
Copy link
Contributor Author

Adding snapshot test doesn't make any sense, those are timings which changes between runs even on the same machine. Manually storing results of benchmark in JSON files and comparing it with some threshold would be a acceptable solution.

If you want to ensure the benchmark is working, we can run it on Circle CI.

@zamotany zamotany merged commit 55a0b13 into master Oct 23, 2017
@zamotany zamotany deleted the fix-benchmark branch October 23, 2017 12:41
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