public inbox for buildbot@sourceware.org
 help / color / mirror / Atom feed
From: Mark Wielaard <mark@klomp.org>
To: Indu Bhagat <indu.bhagat@oracle.com>,
	binutils@sourceware.org,  buildbot@sourceware.org
Subject: libsframe builder (Was: [PATCH 0/2] libsframe: fix some memory leaks)
Date: Fri, 23 Dec 2022 15:22:38 +0100	[thread overview]
Message-ID: <98617b373993a3c6054b9389cddfde56b9aec7d1.camel@klomp.org> (raw)
In-Reply-To: <20221222225457.1095930-1-indu.bhagat@oracle.com>

[-- Attachment #1: Type: text/plain, Size: 517 bytes --]

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.

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

[-- Attachment #2: 0001-Add-libsframe-to-binutils_files.patch --]
[-- Type: text/x-patch, Size: 3031 bytes --]

From b58f0c5e82062f9c1160b72bba62a425c993fc79 Mon Sep 17 00:00:00 2001
From: Mark Wielaard <mark@klomp.org>
Date: Fri, 23 Dec 2022 14:44:53 +0100
Subject: [PATCH] Add libsframe to binutils_files

Because gdb and binutils share a git repo we only trigger builds
if they are part of gdb or binutils. libsframe is a new subdir
part of binutils.

Also add an explicit check-libsframe to binutils_step_checks.
---
 builder/master.cfg | 13 ++++++++++---
 1 file changed, 10 insertions(+), 3 deletions(-)

diff --git a/builder/master.cfg b/builder/master.cfg
index 1e17aa3..8a66ae8 100644
--- a/builder/master.cfg
+++ b/builder/master.cfg
@@ -671,6 +671,7 @@ c['schedulers'].append(gccrust_bootstrap_scheduler)
 binutils_files = ["bfd/",
                   "binutils/", "gas/", "ld/",
                   "libctf/",
+                  "libsframe/",
                   "gold/", "elfcpp/",
                   "include/", "libiberty/", "opcodes/",
                   "configure", "Makefile.in"]
@@ -2106,14 +2107,17 @@ binutils_step_check = steps.Test(
         workdir='binutils-build',
         command=['make',
                  util.Interpolate('-j%(prop:ncpus)s'),
-                 'check-ld', 'check-gas', 'check-binutils'],
+                 'check-ld', 'check-gas', 'check-binutils',
+                 'check-libsframe'],
         name='make check',
         logfiles={ "ld.sum": "ld/ld.sum",
                    "ld.log": "ld/ld.log",
                    "gas.sum": "gas/testsuite/gas.sum",
                    "gas.log": "gas/testsuite/gas.log",
                    "binutils.sum": "binutils/binutils.sum",
-                   "binutils.log": "binutils/binutils.log" },
+                   "binutils.log": "binutils/binutils.log",
+                   "libsframe.sum": "libsframe/libsframe.sum",
+                   "libsframe.log": "libsframe/libsframe.log" },
         haltOnFailure=False, flunkOnFailure=True)
 binutils_steps_bunsen = bunsen_logfile_upload_cpio_steps(
         ["*.sum", "*.log"],
@@ -2123,7 +2127,8 @@ binutils_step_check_libctf = steps.Test(
         workdir='binutils-build',
         command=['make',
                  util.Interpolate('-j%(prop:ncpus)s'),
-                 'check-ld', 'check-gas', 'check-binutils', 'check-libctf'],
+                 'check-ld', 'check-gas', 'check-binutils', 'check-libctf',
+                 'check-libsframe'],
         name='make check',
         logfiles={ "ld.sum": "ld/ld.sum",
                    "ld.log": "ld/ld.log",
@@ -2131,6 +2136,8 @@ binutils_step_check_libctf = steps.Test(
                    "gas.log": "gas/testsuite/gas.log",
                    "binutils.sum": "binutils/binutils.sum",
                    "binutils.log": "binutils/binutils.log",
+                   "libsframe.sum": "libsframe/libsframe.sum",
+                   "libsframe.log": "libsframe/libsframe.log",
                    "libctf.sum": "libctf/libctf.sum",
                    "libctf.log": "libctf/libctf.log" },
         haltOnFailure=False, flunkOnFailure=True)
-- 
2.18.4


       reply	other threads:[~2022-12-23 14:22 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 [this message]
2022-12-23 14:41   ` Frank Ch. Eigler
2022-12-23 16:06     ` Mark Wielaard
2022-12-23 15:24   ` Indu Bhagat
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=98617b373993a3c6054b9389cddfde56b9aec7d1.camel@klomp.org \
    --to=mark@klomp.org \
    --cc=binutils@sourceware.org \
    --cc=buildbot@sourceware.org \
    --cc=indu.bhagat@oracle.com \
    /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).