You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Josh McKenzie (Jira)" <ji...@apache.org> on 2026/04/07 20:39:00 UTC

[jira] [Commented] (CASSANALYTICS-144) Constrain CI resources to prevent error 100 from gradle post test parameterization

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

Josh McKenzie commented on CASSANALYTICS-144:
---------------------------------------------

Even pulled down to 1 worker 6G heap I'm still getting gradle kills OOM. We're going to need to split out pipelines and trim some things down.

> Constrain CI resources to prevent error 100 from gradle post test parameterization
> ----------------------------------------------------------------------------------
>
>                 Key: CASSANALYTICS-144
>                 URL: https://issues.apache.org/jira/browse/CASSANALYTICS-144
>             Project: Apache Cassandra Analytics
>          Issue Type: Task
>            Reporter: Josh McKenzie
>            Assignee: Josh McKenzie
>            Priority: Normal
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> In CASSANALYTICS-122, we made changes to circleci config to prevent some error 100's that showed up after CASSANALYTICS-60. It looks like test parameterization plus bridge plus some changes to heap pressure may have tipped us over an edge we were teetering on for awhile.
> We need to hard constrain things in base build.gradle files to no daemon, max workers 1, and heap max 2048 for test instances instead of having a circleci specific band-aid. Kind of a "global temporary band-aid" of sorts. The goal is to get things correct at the root so we can then start to relax constraints to speed them up with some more intentionality around how we constrain execution environments.
> Ideally we also need to specify and document the intended CI execution environment constraints in terms of CPU and memory so we know what our requirements are to stay within.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org