yifan-c commented on code in PR #183:
URL:
https://github.com/apache/cassandra-analytics/pull/183#discussion_r2975921090
##########
.circleci/config.yml:
##########
@@ -64,10 +64,13 @@ commands:
JDK_VERSION: "<<parameters.jdk>>"
INTEGRATION_MAX_PARALLEL_FORKS: 1
INTEGRATION_MAX_HEAP_SIZE: "1500M"
+ CORE_MAX_PARALLEL_FORKS: 2
+ CORE_TEST_MAX_HEAP_SIZE: "2048m"
CASSANDRA_USE_JDK11: <<parameters.use_jdk11>>
command: |
+ export GRADLE_OPTS="-Xmx2g -Dorg.gradle.jvmargs=-Xmx2g"
# Run compile/unit tests, skipping integration tests
- ./gradlew --stacktrace clean assemble check -x
cassandra-analytics-integration-tests:test
-Dcassandra.analytics.bridges.sstable_format=<<parameters.sstable_format>>
+ ./gradlew --no-daemon --max-workers=2 --stacktrace clean assemble
check -x cassandra-analytics-integration-tests:test
-Dcassandra.analytics.bridges.sstable_format=<<parameters.sstable_format>>
Review Comment:
> This problem exists in trunk, not created by this PR
All commits are made only after CI is green. I do not think the problem
pre-exists in trunk. Likely relevant to the new tests. You will have to dig
into the details to determine which test should be tagged with `Sequential`.
The general idea is to run the resource consuming tests sequentially.
@lukasz-antoniak, might have some tips.
> we will have the same problem of finding the culprit everytime CI is broken
I share the same concern. This is why I am conservative on modifying the CI
configuration, given that the CI issue is probably relevant to the current
patch.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
