mirror of
https://github.com/microsoft/vcpkg.git
synced 2024-12-18 20:37:50 +08:00
a1737683a6
* [issue template] Emphasise that console output isn't enough * comments before failure logs * Be even more specific * Remove s * Address CR * ⁉ * use new label Co-authored-by: Jack·Boos·Yu <47264268+JackBoosY@users.noreply.github.com> Co-authored-by: Jack·Boos·Yu <47264268+JackBoosY@users.noreply.github.com>
34 lines
888 B
Markdown
34 lines
888 B
Markdown
---
|
|
name: Report package build failure
|
|
about: Let us know about build failures in ports.
|
|
title: "[<port name>] build failure"
|
|
labels: category:port-bug
|
|
assignees: ''
|
|
|
|
---
|
|
|
|
<!-- ⚠ Please use the generated issue template instead to report a port build failure. ⚠ -->
|
|
<!-- ⁉ You can find its location at the end of the console output. ⁉ -->
|
|
|
|
**Host Environment**
|
|
|
|
- OS: [e.g. Windows/Linux etc...]
|
|
- Compiler: revision
|
|
|
|
**To Reproduce**
|
|
|
|
Steps to reproduce the behavior:
|
|
|
|
`./vcpkg install xxxx`
|
|
|
|
**Failure logs**
|
|
|
|
- Cut and paste the appropriate build messages from the console output.
|
|
- Attach ***every failure log file*** mentioned in the console output.
|
|
|
|
<!-- ‼ **The console output by itself is not enough to investigate a build failure.** ‼ -->
|
|
|
|
**Additional context**
|
|
|
|
Add any other context about the problem here, such as what you have already tried to resolve the issue.
|