git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: Github actions failing

From
NSENGIYUMVA WILBERFORCE <nsengiyumvawilberforce@gmail.com>
Date
Jan 9, 2023, 04:40 UTC
Message-ID
<CA+PPyiHOLUm87eHuxyhbqqML33Q6g-he_DKRxTEb2fu-2p3NSQ@mail.gmail.com>
In-Reply-To
<CAP8UFD2huFgTjB1hNGyGnMKPONOG6ZV-wvxWkTaz-iZNfxrhJA@mail.gmail.com>
Show 16 quoted lines
> There is the following in the above log:
>
> > 2293 error: cannot run gpg: No such file or directory
>
> so maybe gpg isn't installed on the test system.
>
> It looks like the test you added doesn't have the "GPG" prerequisite. Compare:
>
> -> test_expect_success 'test bare signature atom'
>
> with:
>
> -> test_expect_success GPG 'show good signature with custom format'
>
> There is a "GPG" prerequisite in the latter but not the former.
>

Thanks, I missed the GPG flag. Now I get the following after forcing the push. I have been looking for the problem but I can't figure it out. I will be glad for any help

Show 45 quoted lines
>
> git checkout -b signed &&
> 1840 echo 1 >file && git add file &&
> 1841 test_tick && git commit -S -m initial &&
> 1842 git verify-commit signed 2>out &&
> 1843 head -3 out >expected &&
> 1844 tail -1 out >>expected &&
> 1845 echo >>expected &&
> 1846 git for-each-ref refs/heads/signed --format="%(signature)" >actual &&
> 1847 test_cmp actual expected
> 1848
> 1849 + git checkout -b signed
> 1850 Switched to a new branch 'signed'
> 1851 + echo 1
> 1852 + git add file
> 1853 + test_tick
> 1854 + test -z set
> 1855 + test_tick=1112912113
> 1856 + GIT_COMMITTER_DATE=1112912113 -0700
> 1857 + GIT_AUTHOR_DATE=1112912113 -0700
> 1858 + export GIT_COMMITTER_DATE GIT_AUTHOR_DATE
> 1859 + git commit -S -m initial
> 1860 [signed 4dc4b90] initial
> 1861 Author: A U Thor <author@example.com>
> 1862 1 file changed, 1 insertion(+)
> 1863 create mode 100644 file
> 1864 + git verify-commit signed
> 1865 + head -3 out
> 1866 + tail -1 out
> 1867 + echo
> 1868 + git for-each-ref refs/heads/signed --format=%(signature)
> 1869 + test_cmp actual expected
> 1870 + test 2 -ne 2
> 1871 + eval diff -u "$@"
> 1872 + diff -u actual expected
> 1873 --- actual 2023-01-08 19:40:42.169214115 +0000
> 1874 +++ expected 2023-01-08 19:40:42.121213837 +0000
> 1875 @@ -1,4 +1,5 @@
> 1876 gpg: Signature made Sun Jan 8 19:40:42 2023 UTC
> 1877 gpg: using DSA key 13B6F51ECDDE430D
> 1878 +gpg: checking the trustdb
> 1879 gpg: Good signature from "C O Mitter <committer@example.com>"
> 1880
> 1881 error: last command exited with $?=1
> 1882 not ok 338 - test bare signature atom

On Sun, Jan 8, 2023 at 1:17 PM Christian Couder <christian.couder@gmail.com> wrote:

Show 44 quoted lines
>
> Hi,
>
> On Sun, Jan 8, 2023 at 11:07 AM NSENGIYUMVA WILBERFORCE
> <nsengiyumvawilberforce@gmail.com> wrote:
> >
> > 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?
>
> There is the following in the above log:
>
> > 2293 error: cannot run gpg: No such file or directory
>
> so maybe gpg isn't installed on the test system.
>
> It looks like the test you added doesn't have the "GPG" prerequisite. Compare:
>
> -> test_expect_success 'test bare signature atom'
>
> with:
>
> -> test_expect_success GPG 'show good signature with custom format'
>
> There is a "GPG" prerequisite in the latter but not the former.
Previous: Christian CouderNext: Christian Couder
Message 4 of 7 in “Github actions failing”
  1. NSENGIYUMVA WILBERFORCEJan 8, 2023
  2. NSENGIYUMVA WILBERFORCEJan 8, 2023
  3. Christian CouderJan 8, 2023
  4. NSENGIYUMVA WILBERFORCEJan 9, 2023
  5. Christian CouderJan 9, 2023
  6. Andreas SchwabJan 9, 2023
  7. NSENGIYUMVA WILBERFORCEJan 9, 2023

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.