Test Server Notes
Various projects have facilities for putting their tests on a public server for use by different CI systems (other than in a git repository).
Different systems (test definition servers)
Syzkaller is a fuzzing tester for the Linux kernel. By means of fuzzing, it produces programs that can be used to reproduce the bugs that it finds. These are called 'reproducers', and are useful to test that a bug either still exists or does not exist (has been fixed) for a particular kernel under test.
Dmitry Vyukov has uploaded all current reproducers here: https://github.com/dvyukov/syzkaller-repros
The LTP project (Richard Palethorpe) is looking into adding support for these into LTP. Shuah Khan is working on creating a repository on kernel.org to hold such things. See this discussion: https://lists.yoctoproject.org/pipermail/automated-testing/2019-October/000516.html
Please note the following:
- you should run the 'run.sh' script inside the bin directory
- you need 32-bit x86 gcc and development libraries installed
The Fuego project is working on a server called 'fserver' (https://github.com/tbird20d/fserver.git) to allow sharing of test packages and test execution requests.
It uses Fuego's:
- test packaging system
- run packaging system
It uses json and yaml files and tar archives to store objects and meta-data on the server.
See a prototype implementation at: http://fuegotest.org/cgi-bin/fserver.py
Different systems (results)
Fuego has a prototype system for storing result (run) objects, but not for displaying testcase details. See http://fuegotest.org/cgi-bin/fserver.py/Runs