forked from ros/meta-ros
-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
1 parent
a135ffc
commit feb4b5f
Showing
1 changed file
with
22 additions
and
0 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,22 @@ | ||
--- | ||
name: Bug report | ||
about: Create a report to help us improve | ||
title: '' | ||
labels: '' | ||
assignees: '' | ||
|
||
--- | ||
|
||
**Describe the bug** | ||
A clear and concise description of what the bug is. | ||
|
||
**To Reproduce** | ||
List all the Yocto layers you have included in the build and the revisions you were using. | ||
What MACHINE you're building for and what host OS you're using. | ||
|
||
The "Build Configuration:" section shown by bitbake at the beginning of the build is very good start. | ||
|
||
Then show the exact error you're seeing, often it's useful to attach whole log.do_<task> from ${WORKDIR} and if it doesn't show much details, then additional files as well (like config.log from ${B} directory for do_configure errors with autotools or CMakeOutput.log/CMakeError.log files with cmake). | ||
|
||
**Expected behavior** | ||
A clear and concise description of what you expected to happen. |