1--- 2name: Bug report 3about: Create a report to point us to an issue with the current codebase 4--- 5 6Thanks for taking the time to file an issue for Renode! 7 8Please familiarize yourself with our [Contributing guidelines](https://github.com/renode/renode/blob/master/CONTRIBUTING.md) first. 9 10### Description 11 12A clear and concise description of what the issue is about. 13 14### Expected behaviour 15 16What you expected to happen, and what is happening instead. 17 18### How to reproduce? 19 20We provide an [Issue reproduction template repository](https://github.com/renode/renode-issue-reproduction-template), which is the best way to show us how to reproduce your issue. 21 22If it makes sense in the context of your issue, please create your own repository using this template and adapt the test files until you see the test failing as you expect. 23If you know what the fix should be, you can also create a branch showing the fix and a passing test. 24 25Link this repository here to let us understand your issue easily. 26 27If you find it difficult to create such a repository, or it's not a viable way of reproducing your problem, please provide all the necessary details here: ``repl``, ``resc``, ``robot`` files, binaries, logs etc. 28Please keep in mind that this route may require more back-and-forth communication to establish the underlying cause of the problem. 29 30### Environment 31 32Please, provide the following information: 33 34- OS 35- Renode version (with commit SHA) 36 37### Additional information 38 39Please add all the information you feel is relevant but not clearly visible in the reproduction repo or otherwise. 40 41### Do you plan to address this issue and file a PR? 42 43Please let us know if you want to work on this yourself or need support. 44
