From: "Björn Höfling" <bjoern.hoefling@bjoernhoefling.de>
To: 46780@debbugs.gnu.org
Subject: bug#46780: java-snappy: Test failure on ci.guix.gnu.org
Date: Thu, 25 Feb 2021 21:52:45 +0100 [thread overview]
Message-ID: <20210225215245.4e34edcf@alma-ubu.fritz.box> (raw)
[-- Attachment #1: Type: text/plain, Size: 1870 bytes --]
java-snappy fails as a dependency of several Java evaluations, for
example:
http://ci.guix.gnu.org/eval/120281?status=failed
http://ci.guix.gnu.org/build/359649/log/raw
These failures exist only on ci.guix.gnu.org, but locally it build
perfectly, even with --rounds=100!
Why? Because our buildmachine has too much memory :-) [And I can
remember, we once had that for another package, I just can't remember
again which one].
What should we do about it? Just disable the test, or something more
complicated?
Analysis:
To analyze, I let it once fail with the -K switch to have the directory
/tmp/guix-build-java-snappy-1.1.7.drv-0/
available. Enter the environment with
$ guix environment java-snappy
$ cd /tmp/guix-build-java-snappy-1.1.7.drv-0/
$ source ./environment-variables
$ cd source
$ ant check
--> everything is fine.
Then increase the memory used by junit: Edit the build.xml file, add a
huge "maxmemory" property like this :
<junit maxmemory="30G" printsummary="true" ...
Either have enough RAM or add some extra swap space, then run again:
$ ant check
It fails. The junit logs can be found in
src/test/test-reports/TEST-org.xerial.snappy.pool.CachingBufferPoolTest.txt
Testsuite: org.xerial.snappy.pool.CachingBufferPoolTest
Tests run: 4, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 7.363 sec
Testcase: testDirectByteBuffers took 0.002 sec
Testcase: testSoftReferences took 7.353 sec
FAILED
count: 2048
junit.framework.AssertionFailedError: count: 2048
at org.xerial.snappy.pool.CachingBufferPoolTest.testSoftReferences(Unknown
Source)
Testcase: testArrays took 0 sec
Testcase: testAdjustSize took 0 sec
If you look at the test case source code, it tries to allocate about
20GB and hopes that this fails. It just does not fail on huge machines...
Björn
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 195 bytes --]
next reply other threads:[~2021-02-25 20:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-25 20:52 Björn Höfling [this message]
2021-02-26 22:08 ` bug#46780: java-snappy: Test failure on ci.guix.gnu.org zimoun
2021-02-27 13:58 ` Björn Höfling
2021-02-27 23:29 ` Björn Höfling
2021-03-01 10:50 ` zimoun
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20210225215245.4e34edcf@alma-ubu.fritz.box \
--to=bjoern.hoefling@bjoernhoefling.de \
--cc=46780@debbugs.gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.