From: Keith Seitz <keiths@redhat.com>
To: Serhei Makarov <me@serhei.io>
Cc: bunsen@sourceware.org
Subject: Re: Creating local play area
Date: Tue, 1 Sep 2020 10:08:32 -0700 [thread overview]
Message-ID: <18faefee-505f-ff03-ee6e-b329f0fad7d1@redhat.com> (raw)
In-Reply-To: <9f1d8e59-d504-49ee-aa78-6ccb11d441d3@www.fastmail.com>
[re-adding list]
On 9/1/20 8:43 AM, Serhei Makarov wrote:
>
> On Tue, Sep 1, 2020, at 11:23 AM, Keith Seitz via Bunsen wrote:
>> 5) mkdir bunsen.git; pushd bunsen.git
>> 6) git init
>> 7) popd
> The 'bunsen init' subcommand creates the correct data:
> $ git clone https://sourceware.org/git/bunsen.git bunsen-test
> $ pushd bunsen-test
> $ ./bunsen.py init
> $ ls .bunsen
> bunsen.git config scripts
> $ popd
> $ BUNSEN_REPO=./bunsen-test ./bunsen-test/bunsen.py run +list_runs
>
>> gitdb.exc.BadName: Ref 'HEAD' did not resolve to an object
>>
>> I've almost assuredly goofed with #6.
>
> 'bunsen init' creates an initial commit from which to branch; the
> error is due to the Git repo you used not yet having any commits.
Oh, geez. I was just thinking to myself, "There should be some sort of
initialization subcommand for new repositories." Doh!
I finally got it to import my test run by setting both BUNSEN_DIR and
BUNSEN_REPO.
>
> The warnings are non-fatal but may point to ways the GDB log parser can be improved.
>
Due to the nature of GDB's test suite, there will be plenty of room (on both
sides) for improvement.
Keith
prev parent reply other threads:[~2020-09-01 17:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-01 15:23 Keith Seitz
[not found] ` <9f1d8e59-d504-49ee-aa78-6ccb11d441d3@www.fastmail.com>
2020-09-01 15:44 ` Serhei Makarov
2020-09-01 17:08 ` Keith Seitz [this message]
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=18faefee-505f-ff03-ee6e-b329f0fad7d1@redhat.com \
--to=keiths@redhat.com \
--cc=bunsen@sourceware.org \
--cc=me@serhei.io \
/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).