skoppu22 commented on code in PR #183:
URL:
https://github.com/apache/cassandra-analytics/pull/183#discussion_r2959389308
##########
.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:
- We don't know which tests causing this to tag them. Gradle getting killed
while executing pipelines starting with spark3-* which run unit tests (gradlew
check). Pipelines starting with int-* are running fine. This problem exists in
trunk, not created by this PR. Running CI with --info didn't give any clues as
it was bloating logs and CI killing gradle
- And we will have the same problem of finding the culprit everytime CI is
broken
--
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]
