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

Execution time measurement patch #922

Closed
wants to merge 190 commits into from

Conversation

vershov
Copy link

@vershov vershov commented Feb 19, 2014

Here is second version of the time measurement patch. First version is #919 and are to be closed.

  • I have fixed all issues raised early, as well as have added execution time at gpx output.
  • json output is now could contain "exec_time_ms":n as well as xml output has appropriate field at the metadata field.
  • I have put measurement class into Util/TimingUtil.h, suppose it's more appropriate way to do measurement that existent one. We could discuss it here.

@DennisOSRM
Copy link
Collaborator

please rebase your changes onto the latest develop branch and push with -f option

@DennisOSRM
Copy link
Collaborator

Here's a script that should help rebasing your efforts against the latest origin/develop:

https://gist.github.com/DennisOSRM/9094297

@emiltin
Copy link
Contributor

emiltin commented Feb 19, 2014

you need to change the PR so it's against develop, instead of master.

@DennisOSRM it's possible to change the default branch for the repo, maybe worth considering?

commit 10b8b0b
Author: vershov <vladimir.a.ershov@gmail.com>
Date:   Wed Feb 19 16:52:18 2014 +0100

    small fix

commit 0f15054
Author: vershov <vladimir.a.ershov@gmail.com>
Date:   Wed Feb 19 13:09:07 2014 +0100

    changes into exec time measurement

commit 4efcca3
Author: vershov <vladimir.a.ershov@gmail.com>
Date:   Tue Feb 18 22:57:48 2014 +0100

    Adding execution time measurement facility
@vershov
Copy link
Author

vershov commented Feb 19, 2014

@DennisOSRM I have tried your script but it seems something is going wrong anyway, could you please advise?

@emiltin
Copy link
Contributor

emiltin commented Feb 19, 2014

the script looks complicated to me. why not just something like this?
git fetch origin # assuming gihub remove is called 'origin'
git checkout exec_time_patch # checkout your branch
git rebase origin/develop # rebase on develop

@emiltin
Copy link
Contributor

emiltin commented Feb 19, 2014

but again, this PR is currently against master, it needs to be against develop

@DennisOSRM
Copy link
Collaborator

@emiltin is right, change the PR to be against develop branch. There is no need to open a new one. You should be able to change this.

@vershov
Copy link
Author

vershov commented Feb 19, 2014

Correct pull request is #923

@vershov vershov closed this Feb 19, 2014
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.

6 participants