Am 28.02.2015 um 07:47 schrieb Fam Zheng:
Hello, everyone
I'm glad to announce the fresh Patchew server deployment:
http://qemu.patchew.org/
The mission of this project is to help identify obvious defects (coding style,
compiling, etc.) of posted patches.
Follow the green "passed" or red "failed" button in the page and you'll see the
testing log. You can also see which series have got reviews or comments.
Q: How will this impact patch submission and merging process?
Nothing is affected (at least for now), use this as an auxiliary.
Q: What exactly are tested for each patch?
* scripts/checkpatch.pl
* git am (on top of qemu.git)
* ./configure --target-list=x86_64-softmmu
* make
* make check
Q: No different architectures, compilers or targets?
Not yet. A simple script does the test in a docker instance. A bigger
coverage is possible though, by adding steps to the script:
[1]: https://github.com/famz/patchew/blob/master/tests/qemu-devel.sh
Q: Where is the said email notification?
The email notification feature is ready. In a few days I will enable
automatic replying to the list, once the web interface and testing are both
running smoothly and up to speed. Currently the only recipient is Fam :)
Q: Where is the source code?
https://github.com/famz/patchew
(Pull requests very welcome!)
Enjoy, and feel free to make comments!
Thank you!
---
Fam Zheng
That's really great!
Maybe in a next step, the code coverage could be improved by installing
more optional software packages on your host. Currently the output of
configure contains many lines with "no" (GTK support is missing, for
example). For an Ubuntu 32 bit host, I just installed all software
packages which improve code coverage during the build, see my
documentation on http://wiki.qemu.org/Hosts/Linux. I promptly got a
build error because some parts of QEMU (migration/rdma.c) only support
64 bit builds...
So for the future, both 32 and 64 bit builds would be useful. Then of
course also cross builds for Windows would be nice. :-) If you run many
builds, you can save memory and time by using --enable-debug for most of
them.
Thanks
Stefan
