public inbox for
 help / color / mirror / Atom feed
From: "Martin Liška" <>
To: Mark Wielaard <>,
Subject: Re: buildbot users try branch builders for elfutils
Date: Mon, 15 Aug 2022 09:55:13 +0200	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

On 7/28/22 17:26, Mark Wielaard wrote:
> Hi,
> I setup git users try branches for elfutils. If you have commit
> access to elfutils.git you can now push to a users/<name>/try-xxx
> branch and the buildbot will do builds and sent you (the commit
> author) email about the results. The builds are also visible at:


I would like to try this great feature!

> My workflow to use this looks like:
> - git checkout -b ar_size
> - hack, hack, hack... OK, looks good to submit
> - git commit -a -m "Now who got an ar_size?"
> - git push origin ar_size:users/mark/try-ar_size
> - ... wait for the emails to come in or watch buildbot logs ...

But I get:

git push origin PR29474-fix-debuginfod-concurrency:users/marxin/try-PR29474-fix-debuginfod-concurrency
Enumerating objects: 15, done.
Counting objects: 100% (15/15), done.
Delta compression using up to 16 threads
Compressing objects: 100% (9/9), done.
Writing objects: 100% (9/9), 1.69 KiB | 1.69 MiB/s, done.
Total 9 (delta 7), reused 0 (delta 0), pack-reused 0
error: remote unpack failed: unable to create temporary object directory
To ssh://
 ! [remote rejected]   PR29474-fix-debuginfod-concurrency -> users/marxin/try-PR29474-fix-debuginfod-concurrency (unpacker error)
error: failed to push some refs to 'ssh://'

Can you please take a look what happens?


  reply	other threads:[~2022-08-15  7:55 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-28 15:26 Mark Wielaard
2022-08-15  7:55 ` Martin Liška [this message]
2022-08-15 10:01   ` Mark Wielaard
2022-08-15 10:08     ` Martin Liška

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \

* 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).