danmayer (Dan Mayer)
- Login: danmayer
- Email: dan@mayerdan.com
- Registered on: 06/15/2014
- Last sign in: 12/26/2018
Issues
open | closed | Total | |
---|---|---|---|
Assigned issues | 0 | 0 | 0 |
Reported issues | 0 | 0 | 0 |
Activity
12/26/2018
- 05:15 PM Ruby master Feature #15022: Oneshot coverage
- This is great thanks @mame, I think this will be a significant performance win when I add support for this into Cover...
03/11/2018
- 09:03 PM Ruby master Bug #9572: Restarting Coverage does not produce correct coverage result
- OK, this lead me on a big journey of chasing better benchmarking related to `Coverage` and Coverband, which is my pri...
01/15/2018
- 10:03 PM Ruby master Bug #9572: Restarting Coverage does not produce correct coverage result
- I am seeing emails from Aaron's comments.
- 09:54 PM Ruby master Bug #9572: Restarting Coverage does not produce correct coverage result
- > Pause / Resume just seems like ignoring coverage information for some code.
Yes, the goal would be to ignore it...
01/14/2018
- 09:10 PM Ruby master Bug #9572: Restarting Coverage does not produce correct coverage result
- Thanks for the reply... So you are right about the calculating the current coverage with `peek_result` and if we want...
- 05:55 PM Ruby master Bug #9572: Restarting Coverage does not produce correct coverage result
- I would like to work on closing this out but I believe due to changes in the API expectations since the bug was filed...
06/15/2014
- 01:51 PM Ruby master Bug #9572: Restarting Coverage does not produce correct coverage result
- I have been having this problem as well.
It seems good that Coverage.result resets the coverage data, but once Cov...
Also available in: Atom