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

Progress percentage starts at 100/nsteps instead of 0 #375

Open
astrofrog opened this issue Mar 3, 2016 · 0 comments
Open

Progress percentage starts at 100/nsteps instead of 0 #375

astrofrog opened this issue Mar 3, 2016 · 0 comments
Labels
idea Low-priority enhancement suggestion

Comments

@astrofrog
Copy link
Contributor

In the following example, the progress value should probably start at 0% and go to 10% during the first step?

·· Installing into py2.7-Cython-jinja2-numpy1.8..
· Running 1810 total benchmarks (10 commits * 1 environments * 181 benchmarks)
[ 10.00%] · For astropy commit hash fb78e8c0:
[ 10.00%] ·· Building for py2.7-Cython-jinja2-numpy1.8...............................................................................................
[ 10.00%] ·· Benchmarking py2.7-Cython-jinja2-numpy1.8
[ 10.06%] ··· Running io_ascii.time_ascii.AastexFloat.time_read                                                       259.24ms
[ 10.11%] ··· Running io_ascii.time_ascii.AastexFloat.time_write                                                      958.90ms
[ 10.17%] ··· Running io_ascii.time_ascii.AastexInt.time_read                                                         292.38ms
[ 10.22%] ··· Running io_ascii.time_ascii.AastexInt.time_write                                                           1.55s
[ 10.28%] ··· Running io_ascii.time_ascii.AastexString.time_read                                                      247.27ms
[ 10.33%] ··· Running io_ascii.time_ascii.AastexString.time_write                                                     491.34ms
[ 10.39%] ··· Running io_ascii.time_ascii.BasicFloat.time_read
@pv pv added the enhancement Triaged as an enhancement request label Jun 5, 2016
@pv pv added the idea Low-priority enhancement suggestion label Jun 1, 2019
@pv pv removed the enhancement Triaged as an enhancement request label Jun 30, 2019
@asmeurer asmeurer mentioned this issue May 11, 2020
Open
@HaoZeke HaoZeke mentioned this issue Apr 23, 2023
Open
32 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
idea Low-priority enhancement suggestion
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@pv @astrofrog