public inbox for buildbot@sourceware.org
 help / color / mirror / Atom feed
From: "Frank Ch. Eigler" <fche@elastic.org>
To: Mark Wielaard <mark@klomp.org>
Cc: Indu Bhagat <indu.bhagat@oracle.com>,
	binutils@sourceware.org, buildbot@sourceware.org
Subject: Re: libsframe builder (Was: [PATCH 0/2] libsframe: fix some memory leaks)
Date: Fri, 23 Dec 2022 09:41:24 -0500	[thread overview]
Message-ID: <Y6W+FEAXDaIeaAtT@elastic.org> (raw)
In-Reply-To: <98617b373993a3c6054b9389cddfde56b9aec7d1.camel@klomp.org>

Hi -

>          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" },
> [...]

(For the record, all of those .log/.sum files, and more, are pulled
into the bunsen database automagically, so listing them all here for
storage and presentation in the buildbot system is not really
necessary.)

- FChE

  reply	other threads:[~2022-12-23 14:41 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 [this message]
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=Y6W+FEAXDaIeaAtT@elastic.org \
    --to=fche@elastic.org \
    --cc=binutils@sourceware.org \
    --cc=buildbot@sourceware.org \
    --cc=indu.bhagat@oracle.com \
    --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).