Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

GPG tests fail on windows #339

Closed
jku opened this issue Feb 23, 2021 · 4 comments
Closed

GPG tests fail on windows #339

jku opened this issue Feb 23, 2021 · 4 comments

Comments

@jku
Copy link
Collaborator

jku commented Feb 23, 2021

If windows is enabled in CI workflow, the GPG signing tests fail with timeout:

TimeoutExpired: Command '['gpg', '--detach-sign', '--digest-algo', 'SHA256', '--homedir', 'c:/users/runner~1/appdata/local/temp/tmprxgwki/rsa']' timed out after 3 seconds

Removing the timeout gives a bit of relevant output:

gpg: starting migration from earlier GnuPG versions
gpg: can't connect to the agent: IPC connect call failed
gpg: error: GnuPG agent unusable. Please check that a GnuPG agent can be started.
gpg: migration aborted
gpg: can't connect to the agent: IPC connect call failed
gpg: can't connect to the agent: IPC connect call failed
gpg: keydb_search failed: No agent running
gpg: no default secret key: No agent running
gpg: signing failed: No agent running 

I tried to reproduce outside of securesystemslib but could not: This worked just fine on github (without any extra output):
gpg --detach-sign --digest-algo SHA256 --local-user 8465A1E2E0FB2B40ADB2478E18FB3F537E0C8A17 --homedir rsa
🤷

This blocks #326

@jku
Copy link
Collaborator Author

jku commented Feb 23, 2021

failure output with timeout=None https://github.com/jku/securesystemslib/runs/1960882376

@lukpueh
Copy link
Member

lukpueh commented Feb 23, 2021

in-toto tests that use securesystemslib.gpg do seem to work on windows too, see e.g. https://github.com/SolidifiedRay/in-toto/runs/1949133032?check_suite_focus=true#step:7:131

@lukpueh
Copy link
Member

lukpueh commented Feb 20, 2023

It fails because it cannot handle the absolute homedir paths passed from the tests (see #517). I'll submit a quick fix (pass relative paths in tests), along with other #507-blockers shortly.

@lukpueh
Copy link
Member

lukpueh commented Mar 1, 2023

Closed by #518

@lukpueh lukpueh closed this as completed Mar 1, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants