[gentoo-commits] repo/gentoo:master commit in: net-libs/nodejs/

[Marek Szuba]

commit:     eb883d12833510e1b745cfd4678bbb8b17f610a3
Author:     Marek Szuba <marecki <AT> gentoo <DOT> org>
AuthorDate: Sun May  9 14:10:56 2021 +0000
Commit:     Marek Szuba <marecki <AT> gentoo <DOT> org>
CommitDate: Sun May  9 14:28:43 2021 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=eb883d12

net-libs/nodejs-14.16.1-r1: synchronise test configuration with v16

Signed-off-by: Marek Szuba <marecki <AT> gentoo.org>

 net-libs/nodejs/nodejs-14.16.1-r1.ebuild | 16 ++++++++--------
 1 file changed, 8 insertions(+), 8 deletions(-)

diff --git a/net-libs/nodejs/nodejs-14.16.1-r1.ebuild 
b/net-libs/nodejs/nodejs-14.16.1-r1.ebuild
index c386c0e45b7..3eb26e5b189 100644
--- a/net-libs/nodejs/nodejs-14.16.1-r1.ebuild
+++ b/net-libs/nodejs/nodejs-14.16.1-r1.ebuild
@@ -89,13 +89,6 @@ src_prepare() {
 
        sed -i -e "/'-O3'/d" common.gypi node.gypi || die
 
-       # Avoid a test that I've only been able to reproduce from emerge. It 
doesnt
-       # seem sandbox related either (invoking it from a sandbox works fine).
-       # The issue is that no stdin handle is openened when asked for one.
-       # It doesn't really belong upstream , so it'll just be removed until 
someone
-       # with more gentoo-knowledge than me (jbergstroem) figures it out.
-       rm test/parallel/test-stdout-close-unref.js || die
-
        # debug builds. change install path, remove optimisations and override 
buildtype
        if use debug; then
                sed -i -e "s|out/Release/|out/Debug/|g" tools/install.py || die
@@ -105,6 +98,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
 }
 
@@ -230,5 +230,5 @@ src_test() {
        fi
 
        out/${BUILDTYPE}/cctest || die
-       "${EPYTHON}" tools/test.py --mode=${BUILDTYPE,,} -J message parallel 
sequential || die
+       "${EPYTHON}" tools/test.py --mode=${BUILDTYPE,,} --flaky-tests=dontcare 
-J message parallel sequential || die
 }