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.

Sign up for GitHub

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

Jump to bottom

Report timings #19

Open
jcfr opened this issue Oct 29, 2016 · 0 comments
Open

Report timings #19

jcfr opened this issue Oct 29, 2016 · 0 comments
Labels
enhancement help wanted

Comments

@jcfr
Copy link
Contributor

jcfr commented Oct 29, 2016

To help identify bottleneck, overall time used to run a script should be reported.

Similarly, timing for each substeps should be reported.

After:

[scikit-ci] Executing: python -m ci_addons travis/install_pyenv
[travis:install_pyenv.py] Executing: brew update
[travis:install_pyenv.py]   -> done [20s]
[travis:install_pyenv.py] Executing: brew outdated pyenv || brew upgrade pyenv
[travis:install_pyenv.py]   -> done [5s]
[travis:install_pyenv.py] Looking for pyenv 3.4.5
[travis:install_pyenv.py]   -> found [0s]

Before:

[scikit-ci] Executing: python -m ci_addons travis/install_pyenv
[travis:install_pyenv.py] Executing: brew update
[travis:install_pyenv.py]   -> done
[travis:install_pyenv.py] Executing: brew outdated pyenv || brew upgrade pyenv
[travis:install_pyenv.py]   -> done
[travis:install_pyenv.py] Looking for pyenv 3.4.5
[travis:install_pyenv.py]   -> found
@jcfr jcfr changed the title Report timing for each addon Report timings Oct 29, 2016
@jcfr jcfr mentioned this issue Oct 29, 2016
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement help wanted
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@jcfr