From: Indu Bhagat <indu.bhagat@oracle.com>
To: Mark Wielaard <mark@klomp.org>,
binutils@sourceware.org, buildbot@sourceware.org
Subject: Re: libsframe builder (Was: [PATCH 0/2] libsframe: fix some memory leaks)
Date: Fri, 23 Dec 2022 07:24:36 -0800 [thread overview]
Message-ID: <ba4b0899-03d0-9d24-b905-2a8dcc00563e@oracle.com> (raw)
In-Reply-To: <98617b373993a3c6054b9389cddfde56b9aec7d1.camel@klomp.org>
On 12/23/22 06:22, Mark Wielaard wrote:
> Hi Indu,
>
> On Thu, 2022-12-22 at 14:54 -0800, Indu Bhagat via Binutils wrote:
>> This patch set fixes some memory leaks in the libsframe and it's
>> testsuite.
>
> I see you are an enthusiastic user of the binutils-try buildbot. But
> changes under libsframe/ don't trigger new builds and the libsframe
> testsuite isn't actually ran.
>
heh, binutils-try buildbot's enthusiastic user I am, yes. I did wonder
if there are enough resources for users to be doing this so frequently
(with almost every patch set before commit), I hope its not a problem ?
Right, I noticed that libsframe/ testsuite is not being run, but
binutils-try buildbot has still been useful to catch regressions to
gas/ld by my code ...
Asking about adding libsframe/ testsuite was on my list, thanks for
doing that.
Best Regards,
Indu
> The following tweak to the buildbot master.cfg should fix that.
>
> Please let buildbot@sourceware.org know if you need more tweaks to
> better test the new code.
>
> Cheers,
>
> Mark
next prev parent reply other threads:[~2022-12-23 15:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20221222225457.1095930-1-indu.bhagat@oracle.com>
2022-12-23 14:22 ` Mark Wielaard
2022-12-23 14:41 ` Frank Ch. Eigler
2022-12-23 16:06 ` Mark Wielaard
2022-12-23 15:24 ` Indu Bhagat [this message]
2022-12-23 16:13 ` Mark Wielaard
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=ba4b0899-03d0-9d24-b905-2a8dcc00563e@oracle.com \
--to=indu.bhagat@oracle.com \
--cc=binutils@sourceware.org \
--cc=buildbot@sourceware.org \
--cc=mark@klomp.org \
/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).