geode-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (Jira)" <j...@apache.org>
Subject [jira] [Commented] (GEODE-7367) Specify memory usage for Cargo test containers
Date Wed, 30 Oct 2019 16:01:00 GMT

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

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

Commit f6d7e854fc6234f809330692927bc8a1226b578b in geode's branch refs/heads/feature/GEODE-7358
from BenjaminPerryRoss
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=f6d7e85 ]

GEODE-7367: Unignore  TomcatSessionBackwardsCompatibilityTomcat8WithOldModulesMixedWithCurrentCanDoPutFromOldModuleTest

Co-authored-by: Benjamin Ross <bross@pivotal.io>
Co-authored-by: Donal Evans <doevans@pivotal.io>

> Specify memory usage for Cargo test containers
> ----------------------------------------------
>
>                 Key: GEODE-7367
>                 URL: https://issues.apache.org/jira/browse/GEODE-7367
>             Project: Geode
>          Issue Type: Improvement
>          Components: tests
>            Reporter: Benjamin P Ross
>            Assignee: Benjamin P Ross
>            Priority: Major
>          Time Spent: 1.5h
>  Remaining Estimate: 0h
>
> Currently the server container class used by cargo tests has no specification for max
and initial heap causing them to default to amounts much larger than what our tests need.
This has caused the Tomcat Cargo tests to use significantly more memory than they need to
and put additional stress on the CI process.
> We can fix this by specifying an appropriate amount of memory in the server container's
configuration object.



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

Mime
View raw message