Take screenshot of VM desktop on Chocolatey CLI timeout

[sync-by-unito]

What You Are Seeing?

Package Verifier currently takes a screenshot of the test VM's desktop when the overall Vagrant "session" times out.

The resulting gist will include this screenshot and the included logs will abruptly cut off (as they are collected at the time of the Vagrant time out).

It is possible, however, for the Chocolatey CLI command being run to time out before Vagrant. When this happens no screenshot is taken and the logs end "complete" with an exit code.

What is Expected?

A screenshot should be taken and included on the gist if Chocolatey CLI to aid in troubleshooting why the timeout occurred.

How Did You Get This To Happen? (Steps to Reproduce)

It's difficult to force this to happen organically.

It should be possible to reduce the CommandExecutionTimeoutSeconds in package-verifier.exe.config from 2700 to something much lower to force the Chocolatey CLI command to time out before Vagrant (I cannot actually see where the timeout for Vagrant is defined.)

System Details

• Operating System: Windows Server 2019
• Windows PowerShell Version: 5.1.17763.5202
• Chocolatey CLI Version: 0.10.15 (on host)/2.2.2 (inside test environment)
• Chocolatey Licensed Extension version: N/A
• Chocolatey License type (Professional / Business / ?): N/A
• Terminal/Emulator: N/A

Output Log

• https://gist.github.com/choco-bot/d82194f9568c1984f298b0655d9ab2c9 -> Example of Chocolatey CLI timeout, no screenshot with exit code.
• https://gist.github.com/choco-bot/87b89fbd34f333123b038c3307842f16 -> Example of Vagrant timeout, screenshot but no exit code.

Workarounds

N/A

Proposed Solution

Screenshot on Chocolatey CLI timeout (unsure of actual implementation)

Related Issues and Tickets

• https://gitlab.com/chocolatey/community-infrastructure/package-verifier/-/issues/55
• https://gitlab.com/chocolatey/community-infrastructure/package-verifier/-/issues/63

Done Checklist

• Documentation has been updated.
• Automated tests have been added to cover this bug.
• Manual tests have been added to cover this bug.
• Title is suitable for using in Release Notes?

┆Issue is synchronized with this Gitlab issue by Unito