Skip to content

DOC: contributing: fix asv usage instructions #13794

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

Merged
merged 1 commit into from
Jul 26, 2016

Conversation

pv
Copy link
Contributor

@pv pv commented Jul 26, 2016

The current asv usage instructions in contributing.rst may be unclear for PRs with multiple commits.

By default asv continuous uses head^ as the commit to compare to, whereas for PRs you usually want to compare to master. Write the instructions so that the comparison point is clear.

By default asv continuous uses head^ as the commit to compare to,
whereas for PRs you usually want to compare to master.
@codecov-io
Copy link

codecov-io commented Jul 26, 2016

Current coverage is 85.33% (diff: 100%)

Merging #13794 into master will not change coverage

@@             master     #13794   diff @@
==========================================
  Files           141        141          
  Lines         50711      50711          
  Methods           0          0          
  Messages          0          0          
  Branches          0          0          
==========================================
  Hits          43275      43275          
  Misses         7436       7436          
  Partials          0          0          

Powered by Codecov. Last update 3fdcea6...e624f9b

@sinhrks sinhrks added the Docs label Jul 26, 2016
@sinhrks sinhrks added this to the 0.19.0 milestone Jul 26, 2016

This command uses ``conda`` by default for creating the benchmark
You can replace ``HEAD`` with the name of the branch you are working on.
Copy link
Member

Choose a reason for hiding this comment

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

'You can' -> but it is not needed?

@jorisvandenbossche
Copy link
Member

@pv Thanks a lot for clarifying this!

@pv
Copy link
Contributor Author

pv commented Jul 26, 2016 via email

@jorisvandenbossche jorisvandenbossche merged commit a208c56 into pandas-dev:master Jul 26, 2016
@jorisvandenbossche
Copy link
Member

@pv I have actually another questions (was using the asv benchmark suite the last days): is there a way to run the suite for a specific commit? As with asv run I think you need to specify a range?
The situation I wanted this was to compare the benchmarks of two commits (last release vs master), for which I wanted to use asv compare, but did not yet run benchmarks for only one of the two commits

@pv
Copy link
Contributor Author

pv commented Jul 26, 2016 via email

@jorisvandenbossche
Copy link
Member

@pv Aha, thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants