git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: NSENGIYUMVA WILBERFORCE <nsengiyumvawilberforce@gmail.com>
To: git@vger.kernel.org
Subject: Github actions failing
Date: Sun, 8 Jan 2023 13:02:50 +0300	[thread overview]
Message-ID: <CA+PPyiG=+rs_bOQbaNB311_DVdSc2g44SkLzpaqOER7rfxykrQ@mail.gmail.com> (raw)

Hi,
So I wanted to send the next patch after review.  All the tests pass
when I run them on my PC but I get something like the following error
when I test from my git branch
>
> + git checkout -b signed
> 2283 Switched to a new branch 'signed'
> 2284 + echo 1
> 2285 + git add file
> 2286 + test_tick
> 2287 + test -z set
> 2288 + test_tick=1112912113
> 2289 + GIT_COMMITTER_DATE='1112912113 -0700'
> 2290 + GIT_AUTHOR_DATE='1112912113 -0700'
> 2291 + export GIT_COMMITTER_DATE GIT_AUTHOR_DATE
> 2292 + git commit -S -m initial
> 2293 error: cannot run gpg: No such file or directory
> 2294 error: gpg failed to sign the data
> 2295 fatal: failed to write commit object
> 2296 error: last command exited with $?=128
> 2297 not ok 338 - test bare signature atom
What could be wrong?

             reply	other threads:[~2023-01-08 10:03 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-08 10:02 NSENGIYUMVA WILBERFORCE [this message]
2023-01-08 10:07 ` Github actions failing NSENGIYUMVA WILBERFORCE
2023-01-08 18:17 ` Christian Couder
2023-01-09  4:40   ` NSENGIYUMVA WILBERFORCE
2023-01-09  9:22     ` Christian Couder
2023-01-09 10:10       ` Andreas Schwab
2023-01-09 13:01       ` NSENGIYUMVA WILBERFORCE

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

  List information: http://vger.kernel.org/majordomo-info.html

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

  git send-email \
    --in-reply-to='CA+PPyiG=+rs_bOQbaNB311_DVdSc2g44SkLzpaqOER7rfxykrQ@mail.gmail.com' \
    --to=nsengiyumvawilberforce@gmail.com \
    --cc=git@vger.kernel.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. 
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

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