Patchtest starts up the bitbake (tinfoil) interface multiple times during testing. While this isn't very critical for the user testing a handful of patches, both the selftest suite and the automated patchtest service iterate over many patches to provide feedback, and lose significant amounts of time to simply re-initializing the system for each one. The patchtest code should be refactored to reduce the number of overall calls to tinfoil and find other optimizations that will improve runtime.
The reason that this is happening is because patchtest uses tinfoil to figure out which files have been added/modified/deleted/etc. in a given patch/series. The runtime impact of this can be reduced for now by using BB_SERVER_TIMEOUT = "60" in local.conf for patchtest runs (this has been implemented on my local selftest runs). For now, I think this is sufficient, as more significant patchtest adjustments will find newer ways to determine what files are changed. Closing for now, but it can be reopened if necessary.