From: David Malcolm <dmalcolm@redhat.com>
To: Paulo Matos <pmatos@linki.tools>, "gcc@gcc.gnu.org" <gcc@gcc.gnu.org>
Subject: Re: GCC Buildbot Update
Date: Fri, 15 Dec 2017 14:29:00 -0000 [thread overview]
Message-ID: <1513348171.27881.230.camel@redhat.com> (raw)
In-Reply-To: <b38f19dc-7dc9-af7a-4f00-593605e00d42@linki.tools>
On Fri, 2017-12-15 at 10:16 +0100, Paulo Matos wrote:
>
> On 14/12/17 12:39, David Malcolm wrote:
[...]
> > It looks like you're capturing the textual output from "jv compare"
> > and
> > using the exit code. Would you prefer to import "jv" as a python
> > module and use some kind of API? Or a different output format?
> >
>
> Well, I am using a fork of it which I converted to Python3. Would you
> be
> open to convert yours to Python3? The reason I am doing this is
> because
> all other Python software I have and the buildbot use Python3.
Done.
I found and fixed some more bugs, also (introduced during my
refactoring, sigh...)
> I would also prefer to have some json format or something but when I
> looked at it, the software was just printing to stdout and I didn't
> want
> to spend too much time implementing it, so I thought parsing the
> output
> was just easier.
I can add JSON output (or whatever), but I need to get back to gcc 8
work, so if the stdout output is good enough for now, let's defer
output changes.
> > If you file pull request(s) for the changes you've made in your
> > copy of
> > jamais-vu, I can take at look at merging them.
> >
>
> Happy to do so...
> Will merge your changes into my fork first then.
>
> Kind regards,
next prev parent reply other threads:[~2017-12-15 14:29 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-14 8:56 Paulo Matos
2017-12-14 11:39 ` David Malcolm
2017-12-15 9:16 ` Paulo Matos
2017-12-15 14:29 ` David Malcolm [this message]
2017-12-16 11:07 ` Paulo Matos
2018-01-24 19:20 ` jamais-vu can now ignore renumbering of source lines in dg output (Re: GCC Buildbot Update) David Malcolm
2018-01-25 7:25 ` Paulo Matos
2018-01-29 13:55 ` Paulo Matos
2018-01-29 14:19 ` David Malcolm
2018-01-29 14:27 ` Paulo Matos
2017-12-14 20:32 ` GCC Buildbot Update Christophe Lyon
2017-12-15 7:42 ` Markus Trippelsdorf
2017-12-15 9:21 ` Paulo Matos
2017-12-15 11:10 ` Markus Trippelsdorf
2017-12-15 17:05 ` Segher Boessenkool
2017-12-16 11:54 ` Paulo Matos
2017-12-15 9:19 ` Paulo Matos
2017-12-15 9:21 ` Christophe Lyon
2017-12-15 9:29 ` Paulo Matos
2017-12-20 8:32 ` Paulo Matos
2017-12-20 9:52 ` Christophe Lyon
2017-12-20 10:02 ` Paulo Matos
2017-12-20 10:09 ` Christophe Lyon
2017-12-20 11:49 ` James Greenhalgh
2017-12-20 14:01 ` Paulo Matos
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1513348171.27881.230.camel@redhat.com \
--to=dmalcolm@redhat.com \
--cc=gcc@gcc.gnu.org \
--cc=pmatos@linki.tools \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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).