public inbox for bunsen@sourceware.org
 help / color / mirror / Atom feed
From: Keith Seitz <keiths@redhat.com>
To: bunsen@sourceware.org
Subject: Creating local play area
Date: Tue, 1 Sep 2020 08:23:46 -0700	[thread overview]
Message-ID: <25dabd44-4d48-b809-c97c-9c0069f19d40@redhat.com> (raw)

Hi,

I'd like to play with bunsen in a local sandbox, and I've run into a problem that
isn't entirely obvious to me. [I am working solely on gdb-related bits.]

Here's what I've got/done:

1) checkout bunsen to CWD
2) mkdir sandbox; cd sandbox
3) ln -s ../bunsen .
4) Created a tarball in ~/tmp that contains gdb.log, gdb.sum, and a README.txt
   containing some more-or-less made up branch and "upstream" commit.
5) mkdir bunsen.git; pushd bunsen.git
6) git init
7) popd
8) export BUNSEN_REPO=`pwd`/bunsen.git
9) ./bunsen/bunsen-add.py project=gdb manifest=gdb.log,gdb.sum \
   commit_module=gdb.commit_logs tar=test-results.tar

With #9, I get a lot of "WARNING:" messages (which I will investigate later)
and a python exception:

Processed /tmp/tmpl_wx4eic/gdb.log Red Hat Enterprise Linux 8.3-1.el8 x86_64 66012pass 1738fail
Created new branch gdb/testlogs-2020-06
Traceback (most recent call last):
  File "./bunsen/bunsen-add.py", line 82, in <module>
    commit_id = _commit_logs.commit_logs(b, wd, tar, tarfile=tar,
  File "/home/keiths/work/bunsen/bunsen/scripts-master/gdb/commit_logs.py", line 241, in commit_logs
    commit_id = b.commit(opts.tag, wd=wd, push=False, allow_duplicates=False)
  File "/home/keiths/work/bunsen/bunsen/bunsen.py", line 1163, in commit
    wd.checkout_branch(branch_name, skip_redundant_checkout=True)
  File "/home/keiths/work/bunsen/bunsen/bunsen.py", line 734, in checkout_branch
    branch = self.create_head(branch_name)
  File "/usr/lib/python3.8/site-packages/git/repo/base.py", line 389, in create_head
    return Head.create(self, path, commit, force, logmsg)
  File "/usr/lib/python3.8/site-packages/git/refs/symbolic.py", line 546, in create
    return cls._create(repo, path, cls._resolve_ref_on_create, reference, force, logmsg)
  File "/usr/lib/python3.8/site-packages/git/refs/symbolic.py", line 497, in _create
    target = repo.rev_parse(str(reference))
  File "/usr/lib/python3.8/site-packages/git/repo/fun.py", line 334, in rev_parse
    obj = name_to_object(repo, rev)
  File "/usr/lib/python3.8/site-packages/git/repo/fun.py", line 147, in name_to_object
    raise BadName(name)
gitdb.exc.BadName: Ref 'HEAD' did not resolve to an object

I've almost assuredly goofed with #6.

Any idea what might be wrong? Have I missed instructions on how to properly initialize
the git repo/db store?

Keith


             reply	other threads:[~2020-09-01 15:23 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-01 15:23 Keith Seitz [this message]
     [not found] ` <9f1d8e59-d504-49ee-aa78-6ccb11d441d3@www.fastmail.com>
2020-09-01 15:44   ` Serhei Makarov
2020-09-01 17:08   ` Keith Seitz

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=25dabd44-4d48-b809-c97c-9c0069f19d40@redhat.com \
    --to=keiths@redhat.com \
    --cc=bunsen@sourceware.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).