Hi all,
Today I've included a fourth type of the automatic patchew replies: FreeBSD.
So far we have these tests running by patchew on each patch series:
* Docker tests
Basically it is
make docker-test-quick@centos6 \
docker-test-build@min-glib \
docker-test-mingw@fedora"
* checkpatch.pl
Each patch is fed to ./scripts/checkpatch.pl and all errors are reported.
* s390x
It runs on a machine shared by Fedora team, basically only "./configure and
make", because "make check" hanging is tricky to deal with from an
automation perspective. (Ideas?)
* FreeBSD
Like s390x.
Q1: In the worst case, you get four individual auto replies from patchew. Is
that too many? Do you prefer one reply with all the results concatenated into
one?
Q2: Some think the full log in the mail body is more than necessary. Is it
better or worse if it is a "tail -n 200" of the log in the body and the full log
attached?
Q3: What other tests do maintainers want? Different hosts? Different configure
combinations?
Q4: Any other improvements/features you want? (E.g. some documentation? :)
Fam
