public inbox for elfutils@sourceware.org
 help / color / mirror / Atom feed
* [htdocs] Add Code Coverage Results for Elfutils 0.168
@ 2017-01-05 16:06 Lukas Berk
  2017-01-05 19:02 ` Mark Wielaard
  0 siblings, 1 reply; 3+ messages in thread
From: Lukas Berk @ 2017-01-05 16:06 UTC (permalink / raw)
  To: elfutils-devel

Hi,

The patch itself was too big for the mailing list, but you can find it
on the upstream lberk/coverage branch.

commit ed93952625f4627ae9000fcf46cd7a0a0cd0b382
Author: Lukas Berk <lberk@redhat.com>
Date:   Thu Jan 5 09:58:51 2017 -0500

    Add code coverage results for Elfutils 0.168
    
    These results used to be hosted on fedorapeople.org. Migrating these
    over to sourceware.org htdocs for a more consistent resource and
    documentation location.
    
    Results will be located under:
    https://sourceware.org/elfutils/coverage
    
    Signed-off-by: Lukas Berk <lberk@redhat.com>

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: [htdocs] Add Code Coverage Results for Elfutils 0.168
  2017-01-05 16:06 [htdocs] Add Code Coverage Results for Elfutils 0.168 Lukas Berk
@ 2017-01-05 19:02 ` Mark Wielaard
  2017-01-06 17:12   ` Lukas Berk
  0 siblings, 1 reply; 3+ messages in thread
From: Mark Wielaard @ 2017-01-05 19:02 UTC (permalink / raw)
  To: Lukas Berk; +Cc: elfutils-devel

On Thu, Jan 05, 2017 at 11:05:55AM -0500, Lukas Berk wrote:
> The patch itself was too big for the mailing list, but you can find it
> on the upstream lberk/coverage branch.
> 
> commit ed93952625f4627ae9000fcf46cd7a0a0cd0b382
> Author: Lukas Berk <lberk@redhat.com>
> Date:   Thu Jan 5 09:58:51 2017 -0500
> 
>     Add code coverage results for Elfutils 0.168
>     
>     These results used to be hosted on fedorapeople.org. Migrating these
>     over to sourceware.org htdocs for a more consistent resource and
>     documentation location.
>     
>     Results will be located under:
>     https://sourceware.org/elfutils/coverage
>     
>     Signed-off-by: Lukas Berk <lberk@redhat.com>

Thanks for that. If you check this in could you add a link from the
main page. Just something like:

diff --git a/index.html b/index.html
index 0f0b9fe..32e5f93 100644
--- a/index.html
+++ b/index.html
@@ -58,6 +58,8 @@
       <A HREF="ftp://sourceware.org/pub/elfutils/">ftp://sourceware.org/pub/elfutils/</A> or <A HREF="https://sourceware.org/elfutils/ftp/">https://sourceware.org/elfutils/ftp/</A>
     </P>
 
+    <P>Tests <A HREF="coverage/">code coverage</A> for last release.</P>
+
     <P>
     Included libraries:
     </P>

And a coverage/README file with instructions how to regenerate
the pages after a new elfutils release.

Ideally we would automate this with some buildbot setup of course.
But for now having it done by hand is better than not having it.

Cheers,

Mark

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: [htdocs] Add Code Coverage Results for Elfutils 0.168
  2017-01-05 19:02 ` Mark Wielaard
@ 2017-01-06 17:12   ` Lukas Berk
  0 siblings, 0 replies; 3+ messages in thread
From: Lukas Berk @ 2017-01-06 17:12 UTC (permalink / raw)
  To: Mark Wielaard; +Cc: elfutils-devel

Hi,

Mark Wielaard <mark@klomp.org> writes:
[...]
> Thanks for that. If you check this in could you add a link from the
> main page. Just something like:

Thanks, added and commited.

> And a coverage/README file with instructions how to regenerate
> the pages after a new elfutils release.

Added this as well.

> Ideally we would automate this with some buildbot setup of course.
> But for now having it done by hand is better than not having it.

I don't have the means to host the master buildbot, but if you'd like help
configuring such a setup, I'd be willing to help get it up and running.

Cheers,

Lukas

^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2017-01-06 17:12 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2017-01-05 16:06 [htdocs] Add Code Coverage Results for Elfutils 0.168 Lukas Berk
2017-01-05 19:02 ` Mark Wielaard
2017-01-06 17:12   ` Lukas Berk

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).