[ 
https://issues.apache.org/jira/browse/GEODE-8899?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17324050#comment-17324050
 ] 

ASF subversion and git services commented on GEODE-8899:
--------------------------------------------------------

Commit e65228ff6286d2f94c374f27c56708a5b6871f23 in geode's branch 
refs/heads/develop from Dale Emery
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=e65228f ]

GEODE-8899: Temporarily restore dunitParallelForks (#6335)

In my earlier commit to upgrade Gradle to v6.8.3, I inadvertently
removed the `-PdunitParallelForks` option from the build and test CI
scripts.

Some PRs do not yet include the Gradle upgrade. Without this option, the
Dockerized tests for those those PRs use only 8 test workers. Those
test tasks will likely time out.

The CI scripts must continue to specify `-PdunitParallelForks=<N>` until
all PRs include the Gradle upgrade.

Authored-by: Dale Emery <dem...@vmware.com>

> Update dockerized test plugin
> -----------------------------
>
>                 Key: GEODE-8899
>                 URL: https://issues.apache.org/jira/browse/GEODE-8899
>             Project: Geode
>          Issue Type: Test
>          Components: tests
>            Reporter: Dale Emery
>            Assignee: Dale Emery
>            Priority: Major
>              Labels: GeodeOperationAPI, pull-request-available
>
> *Problem:* The dockerized test plugin includes modified copies of internal 
> Gradle code. This code depends on internal Gradle classes and method 
> signatures as defined in Gradle 5.8. These dependencies prevent us from 
> updating Gradle.
> *Solution:* Update the dockerized test plugin code to be compatible with the 
> latest Gradle, and to take advantage of recent Gradle features (such as the 
> "worker lease" mechanism) that make some plugin details unnecessary.
> Where possible, change the plugin code to use public Gradle APIs.
> Where the plugin must depend on internal Gradle implementation details, 
> comment the code to indicate:
>  * Which internal Gradle implementation details the code depends on
>  * The latest version of Gradle known to satisfy these dependencies
> Where the plugin must use modified copies of internal Gradle code, comment 
> the code to indicate:
>  * Which Gradle class was copied
>  * Which version of Gradle the class was copied from
>  * What modifications were made in the copy, and why
> These comments will help identify implementation details in the plugin that 
> risk incompatibility with future versions of Gradle.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to