As noted in this PR, I found that JFR currently sets the Main.isUnitTest flag, which is surprising—this is supposed to be running production workloads in general, not tests. On the other hand I am nervous about merely removing this flag from JFR since it gates a lot of things, like whether DownloadSettings.DailyCheck is active. On yet another hand, perhaps JFR packagings should be using the extension-filter plugin and JCasC to suppress useless background tasks like this. Or maybe we could have a more general "headless" mode in Jenkins, and JTH would set that in addition to a test-mode flag.