From 039701179263e7154b2fc766a700169517bcbb41 Mon Sep 17 00:00:00 2001 From: yarikoptic Date: Wed, 25 Mar 2020 00:01:36 +0000 Subject: [PATCH 1/2] initial report on failing gpg related tests inside singularity container --- ...ng_build_inside_singularity_container.mdwn | 43 +++++++++++++++++++ 1 file changed, 43 insertions(+) create mode 100644 doc/bugs/tests_fail___40__gpg-agent_related__63____41___when_running_build_inside_singularity_container.mdwn diff --git a/doc/bugs/tests_fail___40__gpg-agent_related__63____41___when_running_build_inside_singularity_container.mdwn b/doc/bugs/tests_fail___40__gpg-agent_related__63____41___when_running_build_inside_singularity_container.mdwn new file mode 100644 index 0000000000..1f735ab0b6 --- /dev/null +++ b/doc/bugs/tests_fail___40__gpg-agent_related__63____41___when_running_build_inside_singularity_container.mdwn @@ -0,0 +1,43 @@ +### Please describe the problem. + +I am trying to setup a cron job on github actions to daily test datalad against bleeding edge git-annex. All the few commands I am using are all in the workflow file: https://github.com/datalad/datalad-extensions/pull/7/files#diff-8364c688b76bfaf5df947cfd4d74eef7R42 + +To build git-annex I am using a singularity container (based on buster with all build-dependencies installed). +While building a binary standalone package (from first prepared .dsc) 3 tests fail: + +`3 out of 260 tests failed (195.33s)` + +- [web view of the logs](https://github.com/datalad/datalad-extensions/pull/7/checks?check_run_id=532056262) +- [and here they are all in raw form (probably would expire soon)](https://pipelines.actions.githubusercontent.com/2UPlDxaVvvbkeFX4btxWorCjpJvj40zvWY5ogH2yZibhOMcU7O/_apis/pipelines/1/runs/182/signedlogcontent/3?urlExpires=2020-03-24T23%3A51%3A03.1656651Z&urlSigningMethod=HMACV1&urlSignature=zmkF8NBdaLU3pAOT3WJ2C6R81sZjH4%2Bka2QiVynkEkU%3D) + +outside the container system is some ubuntu -- inside debian stable (buster). singularity bind mounts HOME, /tmp and passes all environment variables inside the container. + +if you search for `Z FAIL` you would find the hit +[[!format sh """ +2020-03-24T23:41:28.7154039Z crypto: [adjusted/master(unlocked) f647310] empty +2020-03-24T23:41:28.7485256Z adjust ok +2020-03-24T23:41:34.7685919Z gpg: can't connect to the agent: File name too long +2020-03-24T23:41:34.7687700Z gpg: error getting the KEK: No agent running +2020-03-24T23:41:34.7689081Z gpg: error reading '[stdin]': No agent running +2020-03-24T23:41:34.7690114Z gpg: import from '[stdin]' failed: No agent running +2020-03-24T23:41:34.7693611Z FAIL +"""]] + +I wonder if it relates to the discrepancy of gpg-agent running outside of the container and gpg inside the container, which I have detected when saw + +[[!format sh """ +2020-03-24T23:34:08.8873100Z gpg: WARNING: server 'gpg-agent' is older than us (2.2.4 < 2.2.12) +2020-03-24T23:34:08.8873946Z gpg: Note: Outdated servers may lack important security fixes. +2020-03-24T23:34:08.8875072Z gpg: Note: Use the command "gpgconf --kill all" to restart them. +2020-03-24T23:34:08.9223394Z signfile git-annex_8.20200309+git101-ga51a94f61-1~ndall+1_source.buildinfo +"""]] + +in the beginning of the run, or may be just the fact that inside the container it shouldn't use `gpg-agent`... +I wonder if there is an easy way to disable tests which would rely on having connection to gpg-agent? + +FWIW, +- similarish and [then mitigated situation happened awhile back](https://git-annex.branchable.com/bugs/7.20181211+git29-gab4a1bed9_fails_tests_during_neurodebian_build/) +- the same version package builds fine using our conventional neurodebian build setup using cowbuilder (no singularity) + +[[!meta author=yoh]] +[[!tag projects/datalad]] From 79ba17946fcae4c9cf23342fa75c389846ddaa9e Mon Sep 17 00:00:00 2001 From: spwhitton Date: Wed, 25 Mar 2020 16:31:13 +0000 Subject: [PATCH 2/2] Added a comment --- ...ent_2_fb15c2a1ae1c38ece951cc5e0d07f3db._comment | 14 ++++++++++++++ 1 file changed, 14 insertions(+) create mode 100644 doc/todo/git-annex_find_--batch_will_not_accept_absolute_paths/comment_2_fb15c2a1ae1c38ece951cc5e0d07f3db._comment diff --git a/doc/todo/git-annex_find_--batch_will_not_accept_absolute_paths/comment_2_fb15c2a1ae1c38ece951cc5e0d07f3db._comment b/doc/todo/git-annex_find_--batch_will_not_accept_absolute_paths/comment_2_fb15c2a1ae1c38ece951cc5e0d07f3db._comment new file mode 100644 index 0000000000..e3ec903ec4 --- /dev/null +++ b/doc/todo/git-annex_find_--batch_will_not_accept_absolute_paths/comment_2_fb15c2a1ae1c38ece951cc5e0d07f3db._comment @@ -0,0 +1,14 @@ +[[!comment format=mdwn + username="spwhitton" + avatar="http://cdn.libravatar.org/avatar/9c3f08f80e67733fd506c353239569eb" + subject="comment 2" + date="2020-03-25T16:31:13Z" + content=""" +Hello Joey, + +I was passing `--unlocked` only. + +Version 8.20200226 installed from buster-backports. + +Thanks! +"""]]