diff options
| author | Björn Höfling <bjoern.hoefling@bjoernhoefling.de> | 2021-02-27 22:57:11 +0100 |
|---|---|---|
| committer | Björn Höfling <bjoern.hoefling@bjoernhoefling.de> | 2021-02-27 23:34:09 +0100 |
| commit | 23dcf4339d1dc102b2c509a151734f4caff793bd (patch) | |
| tree | 28e84131f5e6152166de643718460b1949144e76 /gnu/packages/admin.scm | |
| parent | decd0dc6bcf88669d272e61f95de0a4d0649fbf8 (diff) | |
| download | guix-23dcf4339d1dc102b2c509a151734f4caff793bd.tar guix-23dcf4339d1dc102b2c509a151734f4caff793bd.tar.gz | |
gnu: java-snappy: Fix checks when build machine has too much memory.
* gnu/packages/java-compression.scm (java-snappy)[arguments]: Add
set-test-memory-size phase.
This fixes <https://debbugs.gnu.org/cgi/bugreport.cgi?bug=46780>.
Thanks to zimoun for the solving idea.
The CachingBufferPoolTest tries to allocate a lot of memory (20GB) and the
test succeeds if there is not enough memory available in the JVM.
When the build machine has a lot of memory (which is the case on the Guix
CI system), the JVM will use more than 20GB as maximum heap size. In
consequence, the test fails.
The new phase adds a maxmemory size of 2G for the tests. Thus all other
tests will have enough memory and the CachingBufferPoolTest will fail.
Diffstat (limited to 'gnu/packages/admin.scm')
0 files changed, 0 insertions, 0 deletions