diff options
author | Marek Szuba <marecki@gentoo.org> | 2021-05-09 15:51:43 +0200 |
---|---|---|
committer | Marek Szuba <marecki@gentoo.org> | 2021-05-09 16:28:39 +0200 |
commit | fc87f82b9b132e36fc36ef63f61a6355ed0a584d (patch) | |
tree | 5ff3be27921115c62937f3d3b3136cef92e75516 /net-libs | |
parent | net-libs/nodejs: drop 16.0.0-r1 (diff) | |
download | gentoo-fc87f82b9b132e36fc36ef63f61a6355ed0a584d.tar.gz gentoo-fc87f82b9b132e36fc36ef63f61a6355ed0a584d.tar.bz2 gentoo-fc87f82b9b132e36fc36ef63f61a6355ed0a584d.zip |
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@gentoo.org>
Diffstat (limited to 'net-libs')
-rw-r--r-- | net-libs/nodejs/nodejs-16.1.0.ebuild | 7 |
1 files changed, 7 insertions, 0 deletions
diff --git a/net-libs/nodejs/nodejs-16.1.0.ebuild b/net-libs/nodejs/nodejs-16.1.0.ebuild index f3079de11314..6727a82af9ee 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 } |