From: "Björn Höfling" <bjoern.hoefling@bjoernhoefling.de>
To: zimoun <zimon.toutoune@gmail.com>
Cc: 46780@debbugs.gnu.org
Subject: bug#46780: java-snappy: Test failure on ci.guix.gnu.org
Date: Sat, 27 Feb 2021 14:58:47 +0100 [thread overview]
Message-ID: <20210227145847.3c0f5baf@alma-ubu> (raw)
In-Reply-To: <864khy1nyt.fsf@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1247 bytes --]
On Fri, 26 Feb 2021 23:08:42 +0100
zimoun <zimon.toutoune@gmail.com> wrote:
> Hi,
>
> On Thu, 25 Feb 2021 at 21:52, Björn Höfling
> <bjoern.hoefling@bjoernhoefling.de> wrote:
>
> > Then increase the memory used by junit: Edit the build.xml file,
> > add a huge "maxmemory" property like this :
> >
> > <junit maxmemory="30G" printsummary="true" ...
>
> [...]
>
> > 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...
>
> What about adding a phase just before the test? For example in this
> build.xml file fix the max memory to 20G if it is greater.
The build.xml is auto-generated by our ant-build-system. So we could
add some parameter into it. But I found this too much of an overkill,
and working on the ant-build-system would mean this goes into staging
(we have too many Java package).
Thus, at first I thought the idea with the additional phase wouldn't
fit here. But at the second glimpse: The build.xml file definitely
already exists before running the tests (even before build). So we
could add a phase that substitutestars and adds the maxmemory parameter
in the build.xml.
Björn
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 195 bytes --]
next prev parent reply other threads:[~2021-02-27 13:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-25 20:52 bug#46780: java-snappy: Test failure on ci.guix.gnu.org Björn Höfling
2021-02-26 22:08 ` zimoun
2021-02-27 13:58 ` Björn Höfling [this message]
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20210227145847.3c0f5baf@alma-ubu \
--to=bjoern.hoefling@bjoernhoefling.de \
--cc=46780@debbugs.gnu.org \
--cc=zimon.toutoune@gmail.com \
/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 public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).