Script profiling
- Dominant language
- Java
- Stars
- 26
- Forks
- 22
- PR merge metrics
- No merged PRs in 30d
Description
_From [josteinaj@gmail.com](https://code.google.com/u/josteinaj@gmail.com/) on May 27, 2013 16:31:38_
It would be really handy to be able to run a script in "profiling mode" and get back some information on which parts of the script takes the most time.
Calabash 1.0.9 added support for profiling: https://github.com/ndw/xmlcalabash1/commit/806d5cd16434cf5e2c707167bac7518b14ee928a I'm not sure what would be simplest to implement; for each job individually or for all jobs. It should be possible to retrieve the profiling log for each job separately.
What do you think?
_Original issue: http://code.google.com/p/daisy-pipeline/issues/detail?id=320_
Contributor guide
No contributing guide indexed for this repository
Assessment
This issue has not been assessed yet.