Hi -
(ping)
commit 23c3100e992029994f33eb4a1465570b476c1df4 (HEAD -> master)
Author: Frank Ch. Eigler
Date: Mon Sep 23 18:03:31 2024 -0400
contrib/test_summary: Add bunsen uploading mode
This makes it easy for someone to push gcc dejagnu/autoconf test
results to a bunsen [1]
Hi Frank, all,
> On 26 Sep 2024, at 15:53, Frank Ch. Eigler wrote:
>> Regarding functionality, perfect enough AFAICT. I was going to
>> make a nitpick comment about comments with full sentences and
>> all that GNU...but better be consistent with the rest of the
>> file. Thanks!
>
> I don't
Hi -
> Regarding functionality, perfect enough AFAICT. I was going to
> make a nitpick comment about comments with full sentences and
> all that GNU...but better be consistent with the rest of the
> file. Thanks!
I don't mind addressing even nitpicks, while awaiting word from
someone who can
On Mon, 23 Sep 2024, Frank Ch. Eigler wrote:
> Hi, HP -
>
> > I'd love for (something like) gcc-testresults@ to be usefully
> > searchable (it can be done but... lacks), so please allow me:
>
> Certainly!
>
> > > +: ${bunsengit=ssh://sourceware.org/git/bunsendb.git/};
> > > +: ${bunsentag=`who
Hi, HP -
> I'd love for (something like) gcc-testresults@ to be usefully
> searchable (it can be done but... lacks), so please allow me:
Certainly!
> > +: ${bunsengit=ssh://sourceware.org/git/bunsendb.git/};
> > +: ${bunsentag=`whoami`/gcc/`uname -m`-`date +%Y%m%d-%H%M`};
>
> That uname -m loo
I'd love for (something like) gcc-testresults@ to be usefully
searchable (it can be done but... lacks), so please allow me:
On Fri, 13 Sep 2024, Frank Ch. Eigler wrote:
> diff --git a/contrib/test_summary b/contrib/test_summary
> index 5760b053ec27..867ada4d6b81 100755
> --- a/contrib/test_summar
On Tue, Sep 17, 2024 at 11:13 AM Frank Ch. Eigler wrote:
>
> Hi -
>
> > [...]
> > I pretty much only use `contrib/test_summary` via the
> > `mail-report.log` target in the top-level Makefile; maybe add a
> > `bunsen` target to the top-level Makefile, too, to simplify invoking
> > it?
>
> Something
Hi -
> [...]
> I pretty much only use `contrib/test_summary` via the
> `mail-report.log` target in the top-level Makefile; maybe add a
> `bunsen` target to the top-level Makefile, too, to simplify invoking
> it?
Something like this: ?
diff --git a/Makefile.in b/Makefile.in
index 966d60454960..4
On Fri, Sep 13, 2024 at 4:19 PM Frank Ch. Eigler wrote:
>
> Hi -
>
> The gcc-testresults mailing list is a well-established place to plop
> snippets of testsuite results. It's an okay way to archive and
> distribute overall counts, but it's not machine readable, and it's way
> incomplete (lacks .
Hi -
The gcc-testresults mailing list is a well-established place to plop
snippets of testsuite results. It's an okay way to archive and
distribute overall counts, but it's not machine readable, and it's way
incomplete (lacks .log content, a lot of metadata, barely meaningfully
searchable) for tr
10 matches
Mail list logo
