tbot creates while executing testcases so called events. After tbot ended with the testcase it can call event_backends, which convert the events to different formats.

There are standard Events which tbot create automatically, for example the Event “Start” is created when tbot starts a new Testcase.

It is also possible to create Testcases specific Events. Therefore a Testcase only has to call the function create_event()


current created standard Events

Event-ID content
log log content
Boardname Name of board
BoardnameEnd End of tests for Boardname
Start Start of TC
End End of TC

Testcases specific Events

Event-ID content
Toolchain used Toolchain
Event-ID content
PW_NR current patchwork patchnumber
PW_CLEAN current patchworknumber patch is clean or not
PW_AA current patchworknumber patch is already applied
PW_APPLY current patchworknumber patch is applies clean or not
Event-ID content
UBOOT_DEFCONFIG used U-Boot configuration
UBOOT_SRC_PATH path, where U-boot source is located
Event-ID content
UBOOT_TEST_PY path to test py result
Event-ID content
Event-ID content
LINUX_VERSION Linux version
Event-ID content
LINUX_DEFCONFIG used Linux configuration
LINUX_SRC_PATH path, where Linux source is located
Event-ID content
SET_DOC_FILENAME set a name for the logfile



pick some Events and put the content into a MYSQL database. Now the DB content can be readen with a simple php script to create a webpage, see for a minimal example:


use gnuplot for creating a statistic image of called testcases.


Use the Eventinformation for creating nice DOT graphics from the test. see a raw example:

Demo Output of a git bisect Demotestcase

planned Event backends:


make from the logs tbot collected, DUTS specific textfiles, so the logs can integrated into the DULG


create xunit files for presenting the results in jenkins

kernel CI:

adapt to a format, so the testresults can be presented at kernel CI (just an idea...)