From: Jelle Licht <jlicht@fsfe.org>
To: "Ludovic Courtès" <ludo@gnu.org>, 37421@debbugs.gnu.org
Subject: bug#37421: [PATCH] gnu: node: Disable tests that fail with openssl@1.1.1d.
Date: Mon, 16 Sep 2019 20:57:53 +0200 [thread overview]
Message-ID: <87tv9cgjbi.fsf@jlicht.xyz> (raw)
In-Reply-To: <87ef0g5ilf.fsf@gnu.org>
Ludovic Courtès <ludo@gnu.org> writes:
> Hello,
>
> Tobias Geerinckx-Rice via Bug reports for GNU Guix <bug-guix@gnu.org>
> skribis:
>
>> Work around <https://debbugs.gnu.org/cgi/bugreport.cgi?bug=37386>.
>>
>> * gnu/packages/node.scm (node)[arguments]: Disable failing tests.
>
> [...]
>
>> + ;; FIXME: These tests fail with openssl@1.1.1d.
>> + (for-each delete-file
>> + '("test/parallel/test-crypto-binary-default.js"
>> + "test/parallel/test-crypto-dh.js"))
>
> It may be the best short-term solution.
Agreed, if ungoogled-chromium works with this that would probably be the
best option.
>
> Could we take a look at what these failures are about to see how bad
> that might be?
Interestingly enough, https://github.com/nodejs/node/issues/3881 notes
issues with exactly these two tests. Perhaps there is a regressions in
our case?
next prev parent reply other threads:[~2019-09-16 18:58 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-16 8:57 bug#37421: node fails to build during update sirmacik
2019-09-16 13:52 ` bug#37421: [PATCH] gnu: node: Disable tests that fail with openssl@1.1.1d Tobias Geerinckx-Rice via Bug reports for GNU Guix
2019-09-16 16:09 ` Ludovic Courtès
2019-09-16 18:57 ` Jelle Licht [this message]
2019-09-16 21:39 ` Tobias Geerinckx-Rice via Bug reports for GNU Guix
2019-09-17 14:43 ` Jelle Licht
2019-09-20 15:11 ` bug#37421: Apply nodejs test workaround? Jack Hill
2019-09-20 15:31 ` Tobias Geerinckx-Rice via Bug reports for GNU Guix
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=87tv9cgjbi.fsf@jlicht.xyz \
--to=jlicht@fsfe.org \
--cc=37421@debbugs.gnu.org \
--cc=ludo@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 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).