Signature test seems to fail on Windows

[Roland van Ipenburg]

No description provided.

[Roland van Ipenburg]

Output from 'C:\Strawberry261\perl\bin\perl.exe ./Build test':

# Testing Geo::METAR::Deduced v1.0.3
t\00_base.t ........ ok
Error verifying signature: Message hash does not match signature checkbytes
# Looks like your test exited with 2 before it could output anything.
t\00_signature.t ... 
Dubious, test returned 2 (wstat 512, 0x200)
Failed 1/1 subtests 

‌

[Roland van Ipenburg]

It’s odd that this seems to fail while Module::Signature and Test::Signature are installed, but if those are installed without testing them what are we going to do about it?

'gpg' is not recognized as an internal or external command,
operable program or batch file.
Error verifying signature: Message hash does not match signature checkbytes
# Looks like your test exited with 2 before it could output anything.

‌

‌

[Roland van Ipenburg]

The way Test::Signature works is that it also fails when the key server is not reachable, so that makes it flaky enough to not require it in automated testing.

Options:

• Don’t require Module::Signature for user tests, that way the user is responsible for having it properly installed or not and Test::Signature won’t fail the user test without it as a feature.
• If that still makes Windows fail – users have actively installed Module::Signature, but in a broken way – we up the hurdle by only doing the Test::Signature when TEST_SIGNATURE is set.

‌