Packer logging for build.ps1 - Windows Systems

[ProtoDroidBot]

• Operating System Version: Windows 10 Pro x64
• Provider (VirtualBox/VMWare): VirtualBox
• Vagrant Version: 2.2.4
• Packer Version: 1.4.0
• Are you using stock boxes (downloaded) or were they built from scratch using Packer? Built from Scratch / Building in progress
• Is the issue reproducible or intermittent? (Should be) Reproducible

When trying to diagnose a few issues with #259, I noticed that the PowerShell build script (build.ps1) does not implement packer logging via $env:PACKER_LOG=1 and $env:PACKER_LOG_PATH=""(from https://www.packer.io/docs/other/debugging.html ). This is causing packer logs to only output via terminal / stdout and not output to packer_build.log as would normally be required to file an issue.

[clong]

Thanks for reporting this! Fixed in f7e0765

[dlee35]

Received error with PACKER_LOG_PATH set to Packer dir ("Couldn't setup log output"). Submitted PR #273.