Replies: 3 comments
-
Attaching log file from my team's ADO pipeline. |
Beta Was this translation helpful? Give feedback.
-
curl, which we use here, prints this output to stderr because it wants stdout to be usable as the actual output by various tools; stdout is usually inappropriate for progress notifications. As a workaround for now you can run bootstrap in a separate task with fail on stderr set to false, or you can redirect stderr in the invoking powershell script. (Note that boostrap doesn't generally report errors to stderr so looking for it is not very helpful here) Doing more binary releases of the vcpkg binary itself if/when we figure out the right way to do that for *nix and macOS will help |
Beta Was this translation helpful? Give feedback.
-
Describe the bug
I'm running vcpkg in Azure DevOps with a Microsoft-Hosted agent. vcpkg is a submodule of my team's repo, so we don't use the preinstalled instance on the agent machine - we use the submodule.
When building on the Windows agent, bootstrap succeeds with no errors.
When building on the Mac & Linux agent, bootstrap succeeds but first logs the following:
The problem is that the progress messages are logged to stderr. I'm calling vcpkg from a pwsh task, and have configured the task to fail if any errors are written, so writing to the error stream causes the task to fail.
It would be nice if vcpkg could only write to stdout unless there is a problem.
Beta Was this translation helpful? Give feedback.
All reactions