Junio C Hamano <gitster@xxxxxxxxx> wrote: > "Shawn O. Pearce" <spearce@xxxxxxxxxxx> writes: > > > "Shawn O. Pearce" <spearce@xxxxxxxxxxx> wrote: > >> If the user has misconfigured `user.signingkey` in their .git/config > >> or just doesn't have any secret keys on their keyring and they ask > >> for a signed tag with `git tag -s` we better make sure the resulting > >> tag was actually signed by gpg. > > This seems to fail the test depending on the order processes > happen to be scheduled. I haven't looked at it closely yet. That's not good. I noticed stepping through the code last night that if gpg is misconfigured (e.g. set a bad user.signingkey in .git/config) it will terminate and send SIGPIPE to git-tag, which makes it terminate. All my change did was implement proper error handling. So if you are seeing failures now then we probably have a problem with the code without my patch too... -- Shawn. - To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
