Creating local play area

Creating local play area

[Keith Seitz]

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

Re: Creating local play area

[Serhei Makarov]

should have used reply to all

On Tue, Sep 1, 2020, at 11: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.
> 
> The warnings are non-fatal but may point to ways the GDB log parser can 
> be improved.
> 
> -- 
> All the best,
>     Serhei
>

Re: Creating local play area

[Keith Seitz]

[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