Earl Warren d1dadf4e06 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		2024-07-16 08:10:58 +02:00
..
testdata/build-release	Update code.forgejo.org/oci/alpine Docker tag to v3.20	2024-05-25 02:05:40 +00:00
workflows	fix(ci): use 512MB for elasticsearch instead of 32GB	2024-07-16 08:10:58 +02:00
cascading-pr-end-to-end	[CI] simplify end-to-end test cascading PR	2024-03-20 18:16:56 +01:00
cascading-release-end-to-end	[CI] simplify running end-to-end tests while building a release	2024-03-20 20:20:42 +01:00