Merge branch 'one-core' of https://github.com/ErwanAliasr1/fio
[fio.git] / REPORTING-BUGS
CommitLineData
fb0480b1
JA
1Reporting a bug
2---------------
3
96d1809b
SW
4...via the mailing list
5=======================
6
7If you notice anything that seems like a fio bug or want to ask fio related
8questions, please send a plain-text only email to the list
9(fio@vger.kernel.org, see README) about it. If you are not running the newest
10release of fio please upgrade first.
a4f581f9
JA
11
12When reporting a bug, you'll need to include:
fb0480b1
JA
13
141) A description of what you think the bug is
96d1809b 152) Environment (e.g. Linux distro version, kernel version). This is mostly
fb0480b1 16 needed if it's a build bug.
96d1809b 173) The output from fio --version .
fb0480b1
JA
184) How to reproduce. Please include a full list of the parameters
19 passed to fio and the job file used (if any).
20
fda82fda
JA
21A bug report can't have too much information. Any time information that
22is left out and has to be asked for will add to the turn-around time
23of getting to the bottom of the issue, and an eventual fix.
a4f581f9 24
fb0480b1 25That's it!
96d1809b
SW
26
27...via GitHub issues
28====================
29
30Please create an issue in the GitHub issue tracker
31(https://github.com/axboe/fio/issues ) but observe the following:
32
33a) If you are asking a question on how to do something ("How do I/Why is?")
34 please send it to the mailing list and not GitHub issues. The fio project
35 uses GitHub issues for reproducible bugs/enhancement requests.
36b) Please reproduce your bug using the latest fio listed on
37 https://github.com/axboe/fio/releases (see the Source and Building sections
38 of the README for how to build fio from source).
39c) Include all of the information requested in the mailing list section above
40 (description, environment, version, reproduction steps and all job parameters).
41
42Thanks!