7.20181211+git29-gab4a1bed9 fails tests during neurodebian build

Please describe the problem.

Trying to build fresh snapshot for neurodebian but 3 tests report failing Full buildlogs are at http://neuro.debian.net/files/buildlogs/git-annex/7.20181211+git29-gab4a1bed9

neurodebian@smaug ../7.20181211+git29-gab4a1bed9-1~ndall+1 % grep -B3 '^FAIL' git-annex_7.20181211+git29-gab4a1bed9-1\~ndall+1_amd64.build 
    bup remote:                                           OK (0.11s)
    crypto:                                               gpg: can't connect to the agent: IPC connect call failed
gpg: error getting the KEK: No agent running
FAIL
--
    bup remote:                                           OK (0.19s)
    crypto:                                               gpg: can't connect to the agent: IPC connect call failed
gpg: error getting the KEK: No agent running
FAIL
--
nothing to commit, working tree clean
gpg: can't connect to the agent: IPC connect call failed
gpg: error getting the KEK: No agent running
FAIL

done I think.. --Joey

RSS Atom

comment 1

I'll bet 14971414dc263fcb8124b4cf6b14b9b7a19189af somehow led to this since the test suite now runs gpg with its home directory set to be inside the test repo and not in the system's temporary directory.

But I tested that commit on filesystems down to FAT, so it seems strange it would fail on whatever filesystem you are testing on.

Comment by joey — Tue Jan 1 16:10:48 2019

Remove comment

the build details

cowbuilder is used, underlying file system (dedicated to debian pkgs building) is ext4. but is it a filesystem effect somehow or just a "partially" isolated environment aspect (such as those pbuilder/cowbuilder chroots)? The message gpg: can't connect to the agent: IPC connect call failed suggests that may be tests pass for you locally as connecting to your gpg agent?

Comment by yarikoptic — Wed Jan 2 01:14:39 2019

Remove comment

comment 3

Having what seems a related problem on my i386 autobuilder:

gpg: keyblock resource '/home/builder/gitbuilder/build/.t/tmprepo89/.git/annex/othertmp/gpgtest/2/pubring.kbx': No such file or directory
gpg: failed to create temporary file '/home/builder/gitbuilder/build/.t/tmprepo89/.git/annex/othertmp/gpgtest/2/.#lk0x57fed950.orca.13095': No such file or directory
gpg: can't connect to the agent: No such file or directory
gpg: problem with the agent: No agent running
gpg: can't create `/home/builder/gitbuilder/build/.t/tmprepo89/.git/annex/othertmp/gpgtest/2/random_seed': No such file or directory
user error (gpg ["--batch","--no-tty","--use-agent","--quiet","--trust-model","always","--batch","--passphrase-fd","28","--symmetric","--force-mdc","--no-textmode"] exited 2)
copy: 1 failed
FAIL (2.31s)
Test.hs:1645:
copy --to encrypted remote failed

Probably gpg error output has failed, but this is also failing to connect to the agent. And it seems a file/directory gpg expects to find is not present when it's running in the test harness.

Comment by joey — Fri Jan 18 17:51:09 2019

Remove comment

comment 4

I've fixed the problem I described above. But I don't think it was the same problem; the neurodebian build log is not complaining about missing files/directories.

gpg in the test suite is using a separate home directory, so it starts a separate gpg-agent process for that. If the test suite is run on a filesystem where gpg-agent can't work, due say to unix sockets not being supported, that might be why it fails.

Comment by joey — Mon Jan 21 18:12:13 2019

Remove comment

comment 5

Anyway, see if f5f059e288b5e618e5c7c86d1db4bfd23d8b39ad somehow fixed it..

Comment by joey — Mon Jan 21 19:18:51 2019

Remove comment

comment 6

tried to build 7.20181211+git284-g6f0d98f2a - it seems that the failing one is different one now?

prop_parse_show_Config:                               FAIL
  *** Failed! Falsifiable (after 3 tests and 1 shrink):
  fromList [("\791992","")]
  Use --quickcheck-replay=133129 to reproduce.
prop_upFrom_basics:                                   OK (0.03s)
...
1 out of 291 tests failed (254.87s)