commit: fc87f82b9b132e36fc36ef63f61a6355ed0a584d
Author: Marek Szuba <marecki <AT> gentoo <DOT> org>
AuthorDate: Sun May 9 13:51:43 2021 +0000
Commit: Marek Szuba <marecki <AT> gentoo <DOT> org>
CommitDate: Sun May 9 14:28:39 2021 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=fc87f82b
net-libs/nodejs-16.1.0: disable test-release-npm
Pretty much cosmetic, uses the network, depends on the state of the
upstream module database.
Signed-off-by: Marek Szuba <marecki <AT> gentoo.org>
net-libs/nodejs/nodejs-16.1.0.ebuild | 7 +++++++
1 file changed, 7 insertions(+)
diff --git a/net-libs/nodejs/nodejs-16.1.0.ebuild
b/net-libs/nodejs/nodejs-16.1.0.ebuild
index f3079de1131..6727a82af9e 100644
--- a/net-libs/nodejs/nodejs-16.1.0.ebuild
+++ b/net-libs/nodejs/nodejs-16.1.0.ebuild
@@ -97,6 +97,13 @@ src_prepare() {
# We need to disable mprotect on two files when it builds Bug 694100.
use pax_kernel && PATCHES+=(
"${FILESDIR}"/${PN}-13.8.0-paxmarking.patch )
+ # All this test does is check if the npm CLI produces warnings of any
sort,
+ # failing if it does. Overkill, much? Especially given one possible
warning
+ # is that there is a newer version of npm available upstream (yes, it
does
+ # use the network if available), thus making it a real possibility for
this
+ # test to begin failing one day even though it was fine before.
+ rm -f test/parallel/test-release-npm.js
+
default
}
