From: "Marek Szuba" <marecki@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: net-libs/nodejs/files/, net-libs/nodejs/
Date: Sun, 9 May 2021 14:29:01 +0000 (UTC) [thread overview]
Message-ID: <1620570513.a52b28a758d244f86e4609bd5936b7a1023a34d6.marecki@gentoo> (raw)
commit: a52b28a758d244f86e4609bd5936b7a1023a34d6
Author: Marek Szuba <marecki <AT> gentoo <DOT> org>
AuthorDate: Sun May 9 12:24:29 2021 +0000
Commit: Marek Szuba <marecki <AT> gentoo <DOT> org>
CommitDate: Sun May 9 14:28:33 2021 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=a52b28a7
net-libs/nodejs-16.1.0: Backport upstream fix for test-repl-history-navigation
Signed-off-by: Marek Szuba <marecki <AT> gentoo.org>
...odejs-16.1.0-test-repl-history-navigation.patch | 56 ++++++++++++++++++++++
net-libs/nodejs/nodejs-16.1.0.ebuild | 5 +-
2 files changed, 57 insertions(+), 4 deletions(-)
diff --git a/net-libs/nodejs/files/nodejs-16.1.0-test-repl-history-navigation.patch b/net-libs/nodejs/files/nodejs-16.1.0-test-repl-history-navigation.patch
new file mode 100644
index 00000000000..724541a870d
--- /dev/null
+++ b/net-libs/nodejs/files/nodejs-16.1.0-test-repl-history-navigation.patch
@@ -0,0 +1,56 @@
+From 7c8a60851c459ea18afbfc54bfc8cf7394ea56c3 Mon Sep 17 00:00:00 2001
+From: Antoine du Hamel <duhamelantoine1995@gmail.com>
+Date: Thu, 6 May 2021 12:00:07 +0200
+Subject: [PATCH] test,repl: fix tests when inspector is disabled
+
+Fixes: https://github.com/nodejs/node/issues/38558
+
+PR-URL: https://github.com/nodejs/node/pull/38564
+Reviewed-By: Anna Henningsen <anna@addaleax.net>
+Reviewed-By: James M Snell <jasnell@gmail.com>
+Reviewed-By: Rich Trott <rtrott@gmail.com>
+---
+ test/parallel/test-repl-history-navigation.js | 12 ++++++------
+ 1 file changed, 6 insertions(+), 6 deletions(-)
+
+diff --git a/test/parallel/test-repl-history-navigation.js b/test/parallel/test-repl-history-navigation.js
+index df4f0390a69c..527cf235bddd 100644
+--- a/test/parallel/test-repl-history-navigation.js
++++ b/test/parallel/test-repl-history-navigation.js
+@@ -559,14 +559,14 @@ const tests = [
+ env: { NODE_REPL_HISTORY: defaultHistoryPath },
+ test: ['const util = {}', ENTER,
+ 'ut', RIGHT, ENTER],
+- expected: common.hasIntl && common.hasCrypto ? [
++ expected: [
+ prompt, ...'const util = {}',
+ 'undefined\n',
+- prompt, ...'ut', ' // il', '\n// {}',
+- 'il', '\n// {}',
++ prompt, ...'ut', ...(prev ? [' // il', '\n// {}',
++ 'il', '\n// {}'] : [' // il', 'il']),
+ '{}\n',
+ prompt,
+- ] : [],
++ ],
+ clean: false
+ },
+ {
+@@ -577,7 +577,7 @@ const tests = [
+ 'globalThis.util = {}', ENTER,
+ 'ut', RIGHT, ENTER,
+ 'Reflect.defineProperty(globalThis, "util", utilDesc)', ENTER],
+- expected: common.hasIntl && common.hasCrypto ? [
++ expected: [
+ prompt, ...'const utilDesc = ' +
+ 'Reflect.getOwnPropertyDescriptor(globalThis, "util")',
+ 'undefined\n',
+@@ -588,7 +588,7 @@ const tests = [
+ prompt, ...'Reflect.defineProperty(globalThis, "util", utilDesc)',
+ 'true\n',
+ prompt,
+- ] : [],
++ ],
+ clean: false
+ },
+ ];
diff --git a/net-libs/nodejs/nodejs-16.1.0.ebuild b/net-libs/nodejs/nodejs-16.1.0.ebuild
index 61ddcf50edb..f3079de1131 100644
--- a/net-libs/nodejs/nodejs-16.1.0.ebuild
+++ b/net-libs/nodejs/nodejs-16.1.0.ebuild
@@ -42,6 +42,7 @@ DEPEND="${RDEPEND}"
PATCHES=(
"${FILESDIR}"/${PN}-12.22.1-uvwasi_shared_libuv.patch
"${FILESDIR}"/${PN}-15.2.0-global-npm-config.patch
+ "${FILESDIR}"/${PN}-16.1.0-test-repl-history-navigation.patch
)
S="${WORKDIR}/node-v${PV}"
@@ -70,10 +71,6 @@ src_prepare() {
export V=1
export BUILDTYPE=Release
- # See https://github.com/nodejs/node/issues/38558
- # FIXME: temporary, until we have figured out why that one single test fails.
- rm -f test/parallel/test-repl-history-navigation.js
-
# fix compilation on Darwin
# https://code.google.com/p/gyp/issues/detail?id=260
sed -i -e "/append('-arch/d" tools/gyp/pylib/gyp/xcode_emulation.py || die
next reply other threads:[~2021-05-09 14:29 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-09 14:29 Marek Szuba [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-05-24 22:02 [gentoo-commits] repo/gentoo:master commit in: net-libs/nodejs/files/, net-libs/nodejs/ William Hubbs
2024-12-26 3:30 William Hubbs
2023-11-06 15:42 William Hubbs
2023-11-02 21:57 William Hubbs
2023-09-14 22:45 William Hubbs
2023-09-07 15:51 William Hubbs
2023-04-27 2:04 William Hubbs
2023-04-17 17:20 William Hubbs
2023-03-05 23:18 William Hubbs
2022-10-28 15:57 Sam James
2022-09-16 16:16 William Hubbs
2022-09-14 6:14 William Hubbs
2022-06-11 21:04 William Hubbs
2022-05-04 19:02 William Hubbs
2022-05-04 18:50 William Hubbs
2022-05-04 18:25 William Hubbs
2022-05-04 17:57 William Hubbs
2022-03-17 21:39 William Hubbs
2021-06-24 11:15 Marek Szuba
2021-06-04 12:01 Marek Szuba
2021-05-09 14:29 Marek Szuba
2021-05-04 15:42 Marek Szuba
2021-01-08 22:55 Marek Szuba
2020-11-21 21:36 Marek Szuba
2020-11-13 17:25 Marek Szuba
2020-11-09 15:06 Marek Szuba
2020-09-04 7:09 Jeroen Roovers
2019-11-27 21:37 Magnus Granberg
2019-10-11 14:53 Jeroen Roovers
2019-03-16 14:45 Jeroen Roovers
2018-12-27 14:59 Jeroen Roovers
2018-12-13 12:50 Jeroen Roovers
2018-07-23 10:49 Jeroen Roovers
2017-11-15 15:13 Jeroen Roovers
2017-10-24 4:49 Jeroen Roovers
2017-08-18 14:17 Jeroen Roovers
2016-10-25 6:29 Jeroen Roovers
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=1620570513.a52b28a758d244f86e4609bd5936b7a1023a34d6.marecki@gentoo \
--to=marecki@gentoo.org \
--cc=gentoo-commits@lists.gentoo.org \
--cc=gentoo-dev@lists.gentoo.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox