On 10/1/2013 9:44 AM, Patrick Reynolds wrote:
There is definitely a use case in which we want to aggregate coverage
between C++, Python, and Javascript in a web application.
By the way, sorry for the warning on the nightlies. That's fixed in next.
Right, so the change needs to be in
On 9/29/2013 2:37 PM, Patrick Reynolds wrote:
I'll leave this one to folks who are better versed in the arcane art of
Bullseye...
Does anyone still use this? ;)
Yes, it is still in use, and no it is not arcane. It is a really good
commercial cross platform branch based coverage tool.
On 9/28/2013 5:36 AM, Rolf Eike Beer wrote:
Break if everything is fine, continue on error or when no files are found? All
other handlers support being run in parallel, why not Bullseye?
Not really.
Return 0 if COVFILE is not set so, no coverage.
Return 0 if COVFILE is set but there was
That was very poor word choice on my part. My apologies. I mean to say:
I leave that to someone more expert in the Bullseye system.
--
Patrick Reynolds
Technical Leader
Kitware, Inc.
919 869 8848
On Monday, September 30, 2013 at 10:32 AM, Bill Hoffman wrote:
On 9/29/2013 2:37 PM, Patrick
Am 30.09.2013 16:45, schrieb Bill Hoffman:
On 9/28/2013 5:36 AM, Rolf Eike Beer wrote:
Break if everything is fine, continue on error or when no files are
found? All
other handlers support being run in parallel, why not Bullseye?
Not really.
Return 0 if COVFILE is not set so, no coverage.
Eike,
This is fantastic feedback. Thanks!
I've responded to specific issues inline.
TL;DR: I fixed a lot of these points. This should be closer to merge-ability.
--
Patrick Reynolds
Technical Leader
Kitware, Inc.
919 869 8848
On Saturday, September 28, 2013 at 5:36 AM, Rolf Eike Beer
Am Sonntag, 29. September 2013, 14:22:02 schrieben Sie:
Eike,
This is fantastic feedback. Thanks!
I've responded to specific issues inline.
TL;DR: I fixed a lot of these points. This should be closer to
merge-ability.
Am Freitag, 27. September 2013, 11:30:52 schrieb Patrick Reynolds:
