Re: openbsd code coverage

2018-01-02 Thread Marc Espie 
On Tue, Jan 02, 2018 at 12:40:33AM +0100, Aron Diehl wrote:
> Hi,
> 
> 
> I'm working on measuring OpenBSD code coverage.
> 
> 
> Code coverage of what? The regression-tests make target?
> 
> Cheers
> Aron

Obviously.

Re: openbsd code coverage

2018-01-01 Thread Aron Diehl 
Hi,


I'm working on measuring OpenBSD code coverage.


Code coverage of what? The regression-tests make target?

Cheers
Aron

Re: openbsd code coverage

2017-12-09 Thread Base Pr1me 
I only say this because I am extremely intoxicated. Will you please shut
the fuck up?

On Dec 9, 2017 17:08, "Rupert Gallagher"  wrote:

> Fuck you x9p anonymous coward.
>
> Sent from ProtonMail Mobile
>
> On Sat, Dec 9, 2017 at 23:02, x9p  wrote:
>
> > On Sat, December 9, 2017 3:33 pm, Anders Andersson wrote: > On Sat, Dec
> 9, 2017 at 12:46 PM, Rupert Gallagher  > wrote: >> Code Coverage? > > Type
> that into google instead, maybe you will get a better answer. > > Indeed
> redirecting @protonmail.com to /dev/null provides a much more pleasant
> misc@- reading experience, as suggested before. Just saw this email bcz
> of citation. cheers. x9p @protonmail.com>

Re: openbsd code coverage

2017-12-09 Thread Rupert Gallagher 
Fuck you x9p anonymous coward.

Sent from ProtonMail Mobile

On Sat, Dec 9, 2017 at 23:02, x9p  wrote:

> On Sat, December 9, 2017 3:33 pm, Anders Andersson wrote: > On Sat, Dec 9, 
> 2017 at 12:46 PM, Rupert Gallagher  > wrote: >> Code Coverage? > > Type that 
> into google instead, maybe you will get a better answer. > > Indeed 
> redirecting @protonmail.com to /dev/null provides a much more pleasant misc@- 
> reading experience, as suggested before. Just saw this email bcz of citation. 
> cheers. x9p @protonmail.com>

Re: openbsd code coverage

2017-12-09 Thread Rupert Gallagher 
The meaningful term is "test coverage", where "test" is the name of a test. To 
make sense, you must say what you are testing AND how you are testing it.

If you say "code coverage", you are just saying that you did not bother reading 
the papers, and you are just using a group of words without any meaning.

Sent from ProtonMail Mobile

On Sat, Dec 9, 2017 at 18:33, Anders Andersson  wrote:

> On Sat, Dec 9, 2017 at 12:46 PM, Rupert Gallagher wrote: > Code Coverage? 
> Type that into google instead, maybe you will get a better answer. 
> @protonmail.com>

Re: openbsd code coverage

2017-12-09 Thread x9p 
On Sat, December 9, 2017 3:33 pm, Anders Andersson wrote:
> On Sat, Dec 9, 2017 at 12:46 PM, Rupert Gallagher 
> wrote:
>> Code Coverage?
>
> Type that into google instead, maybe you will get a better answer.
>
>

Indeed redirecting @protonmail.com to /dev/null provides a much more
pleasant misc@- reading experience, as suggested before.

Just saw this email bcz of citation.

cheers.

x9p

Re: openbsd code coverage

2017-12-09 Thread Anders Andersson 
On Sat, Dec 9, 2017 at 12:46 PM, Rupert Gallagher  wrote:
> Code Coverage?

Type that into google instead, maybe you will get a better answer.

Re: openbsd code coverage

2017-12-09 Thread Rupert Gallagher 
Code Coverage?

Sent from ProtonMail Mobile

On Sat, Dec 9, 2017 at 12:32, Sergey Bronnikov <serg...@bronevichok.ru> wrote:

> Hi, I'm working on measuring OpenBSD code coverage. The process still has 
> drawbacks, but some results are already available. 
> https://ligurio.github.io/openbsd-tests/6.2/coverage.html Sergey

openbsd code coverage

2017-12-09 Thread Sergey Bronnikov 
Hi,

I'm working on measuring OpenBSD code coverage.
The process still has drawbacks,
but some results are already available.

https://ligurio.github.io/openbsd-tests/6.2/coverage.html

Sergey