Consider Gradle wrapper as a wrapper for headless calculations#11266
Conversation
nikita-tkachenko-datadog
left a comment
There was a problem hiding this comment.
Let's move the new check to the isWrapper method. Otherwise, LGTM!
Test Environment - sbt-scalatestJob Status: success
|
Test Environment - netflix-zuulJob Status: success
|
Test Environment - nebula-release-pluginJob Status: success
|
Test Environment - pass4sJob Status: success
|
Test Environment - reactive-streams-jvmJob Status: success
|
Test Environment - sonar-kotlinJob Status: success
|
Test Environment - jolokiaJob Status: success
|
Test Environment - okhttpJob Status: success
|
Test Environment - spring_bootJob Status: success
|
Test Environment - sonar-javaJob Status: success
|
|
/merge |
|
View all feedbacks in Devflow UI.
The expected merge time in
daniel.mohedano@datadoghq.com cancelled this merge request build |
|
/merge -c |
|
View all feedbacks in Devflow UI.
|
|
/merge |
|
View all feedbacks in Devflow UI.
The expected merge time in
|
5a1127a
into
master
What Does This Do
ProcessHierarchy.isGradleLauncher()to not misclassify Gradle wrapper as headless.Motivation
:dd-smoke-tests:gradle:testwas timing out on master. Each launcher test iteration was building the repository index twice: once in the Gradle wrapper JVM and once in the spawned Gradle daemon. ProcessHierarchy misclassified the wrapper JVMs as headless due to launcher classes (org.gradle.launcher.Main/GradleMain) being missing at premain, since the wrapper loads the Gradle distribution later. Verified by enabling debug logs and seeing twoBuilding index of source files...lines in the test output instead of one.Contributor Checklist
type:and (comp:orinst:) labels in addition to any other useful labelsclose,fix, or any linking keywords when referencing an issueUse
solvesinstead, and assign the PR milestone to the issueJira ticket: [PROJ-IDENT]
Note: Once your PR is ready to merge, add it to the merge queue by commenting
/merge./merge -ccancels the queue request./merge -f --reason "reason"skips all merge queue checks; please use this judiciously, as some checks do not run at the PR-level. For more information, see this doc.