forgejo/.forgejo/workflows
Earl Warren cb656c3309 fix(ci): use 512MB for elasticsearch instead of 32GB
It can be observed that when elasticsearch runs in the CI the process
uses 32GB of resident memory.

Set Xmx and Xms to no more than the threshold that the JVM uses for
compressed object pointers (compressed oops); the exact threshold
varies but is near 32 GB. You can verify that you are under the
threshold by looking for a line in the logs like the following:

Refs: https://www.elastic.co/guide/en/elasticsearch/reference/7.5/docker.html
Refs: https://www.elastic.co/guide/en/elasticsearch/reference/7.5/heap-size.html
(cherry picked from commit d1dadf4e06)
2024-07-16 11:01:31 +00:00
..
backport.yml [CI] configure backport to comment on the PR on failure 2024-04-15 18:23:57 +02:00
build-release-integration.yml Disable duplicate builds 2024-03-25 13:24:53 +01:00
build-release.yml fix(release): add missing ARG RELEASE_VERSION 2024-04-17 17:16:53 +02:00
cascade-setup-end-to-end.yml [CI] simplify end-to-end test cascading PR 2024-03-20 18:16:56 +01:00
e2e.yml tests: run JavaScript tests when web_src/js is modified 2024-07-08 18:58:33 +00:00
mirror.yml [CI] mirror to forgejo-integration daily instead of each commit 2024-02-17 11:55:52 +01:00
publish-release.yml ci(release): upgrade v*.next.forgejo.org when the release is ready 2024-07-01 12:52:59 +02:00
renovate.yml Update renovate to v37.421.2 2024-07-01 00:01:26 +00:00
testing.yml fix(ci): use 512MB for elasticsearch instead of 32GB 2024-07-16 11:01:31 +00:00