LKFT sends a daily report (here's an example) to the kselftest mailing list that contains the results of kselftest on the daily -next build.
This report is generated by qa-reports, but not sent from qa-reports. Rather, it uses a jenkins job and some custom scripting. The implementation of this report uses the following files and jobs.
The trigger job runs every hour and looks for new builds in qa-reports that have not yet been reported.
The jenkins jobs check out the following scripts from lkft-tools
Note also that there is a custom jinja2 template in qa-reports that is used to filter out the kselftest data from the rest of the data.