From: Mathieu Othacehe <othacehe@gnu.org>
To: Timotej Lazar <timotej.lazar@araneo.si>
Cc: Ricardo Wurmus <rekado@elephly.net>, 55206-done@debbugs.gnu.org
Subject: bug#55206: Intermittent ldap test failure
Date: Fri, 24 Jun 2022 10:26:19 +0200 [thread overview]
Message-ID: <875ykqjwlw.fsf@gnu.org> (raw)
In-Reply-To: <87wnd7pcmy.fsf@araneo.si> (Timotej Lazar's message of "Thu, 23 Jun 2022 18:28:53 +0200")
Hey Timotej,
> After increasing the memory limit for the test VM, I was able to run the
> test successfully ten times on two different machines. The patch is
> attached.
Great, that wouldn't be the first time that the RAM limitation causes
strange transient issues.
I'm pushing the proposed patch and closing this bug,
Thanks,
Mathieu
prev parent reply other threads:[~2022-06-24 8:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-01 11:09 bug#55206: Intermittent ldap test failure Mathieu Othacehe
2022-06-23 16:28 ` Timotej Lazar
2022-06-24 8:26 ` Mathieu Othacehe [this message]
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=875ykqjwlw.fsf@gnu.org \
--to=othacehe@gnu.org \
--cc=55206-done@debbugs.gnu.org \
--cc=rekado@elephly.net \
--cc=timotej.lazar@araneo.si \
/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).