-
Improvement
-
Resolution: Unresolved
-
Minor
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.
- causes
-
JENKINS-60552 Fail to call a script method stored as a class attribute/field
-
- Open
-
- relates to
-
JENKINS-58407 Fail to call a Closure stored as a class attribute/field
-
- Resolved
-
[JENKINS-55764] Reconsider use of Main.isUnitTest in JFR
Labels | New: triaged |
Link |
New:
This issue relates to |
Link | New: This issue causes JENKINS-60552 [ JENKINS-60552 ] |
Assignee | New: Oleg Nenashev [ oleg_nenashev ] |