Am Tue, 10 Jul 2018 14:12:57 -0700 schrieb Junio C Hamano <gits...@pobox.com>:
> Henning Schild <henning.sch...@siemens.com> writes: > > > Add test cases to cover the new X509/gpgsm support. Most of them > > resemble existing ones. They just switch the format to x509 and set > > the signingkey when creating signatures. Validation of signatures > > does not need any configuration of git, it does need gpgsm to be > > configured to trust the key(-chain). > > We generate a self-signed key for commit...@example.com and > > configure gpgsm to trust it. > > > > Signed-off-by: Henning Schild <henning.sch...@siemens.com> > > --- > > t/lib-gpg.sh | 9 ++++++- > > t/lib-gpg/gpgsm-gen-key.in | 6 +++++ > > t/t4202-log.sh | 66 > > ++++++++++++++++++++++++++++++++++++++++++++++ > > t/t5534-push-signed.sh | 52 > > ++++++++++++++++++++++++++++++++++++ t/t7003-filter-branch.sh | > > 15 +++++++++++ t/t7030-verify-tag.sh | 47 > > +++++++++++++++++++++++++++++++-- t/t7600-merge.sh | 31 > > ++++++++++++++++++++++ 7 files changed, 223 insertions(+), 3 > > deletions(-) create mode 100644 t/lib-gpg/gpgsm-gen-key.in > > I saw my post-integration tests taking forever to finish for 'pu' > and "ps x" output showed that many tests (I ran tests in parallel) > were stuck and all of them were running gpgsm. > > For now, I've ejected the topic out of 'pu', as I want to finish > today's integration run with all the other topics first before > coming back to this topic. That must have been the key generation, see my reply to one of Jeffs mails. Henning
