^ Error: ENOENT: no such file or directory, mkdir '/var/tmp/portage/net-libs/nodejs-16.5.0/work/node-v16.5.0/test/.tmp.728/test10/../test11/test12' at Object.mkdirSync (node:fs:1324:3) at Object.<anonymous> (/var/tmp/portage/net-libs/nodejs-16.5.0/work/node-v16.5.0/test/parallel/test-fs-mkdir.js:131:6) at Module._compile (node:internal/modules/cjs/loader:1095:14) at Object.Module._extensions..js (node:internal/modules/cjs/loader:1124:10) ------------------------------------------------------------------- This is an unstable amd64 chroot image at a tinderbox (==build bot) name: 17.1_desktop_plasma_systemd-j3_test-20210715-115044 ------------------------------------------------------------------- gcc-config -l: [1] x86_64-pc-linux-gnu-11.1.0 * clang version 12.0.1 Target: x86_64-pc-linux-gnu Thread model: posix InstalledDir: /usr/lib/llvm/12/bin /usr/lib/llvm/12 12.0.1 Python 3.9.6 Available Rust versions: [1] rust-bin-1.53.0 * The following VMs are available for generation-2: *) AdoptOpenJDK 8.292_p10 [openjdk-bin-8] Available Java Virtual Machines: [1] openjdk-bin-8 system-vm The Glorious Glasgow Haskell Compilation System, version 8.10.4 HEAD of ::gentoo commit 874ae6987a56ba2118397d78d15ed959b6b09c79 Author: Repository mirror & CI <repomirrorci@gentoo.org> Date: Sat Jul 17 00:20:40 2021 +0000 2021-07-17 00:20:39 UTC emerge -qpvO net-libs/nodejs [ebuild N ] net-libs/nodejs-16.5.0 USE="icu npm snapshot ssl system-ssl test -debug -doc -inspector -lto -pax-kernel -system-icu -systemtap" CPU_FLAGS_X86="sse2"
Created attachment 724471 [details] emerge-info.txt
Created attachment 724474 [details] emerge-history.txt
Created attachment 724477 [details] environment
Created attachment 724480 [details] etc.portage.tar.bz2
Created attachment 724483 [details] logs.tar.bz2
Created attachment 724486 [details] net-libs:nodejs-16.5.0:20210717-011425.log.bz2
Created attachment 724489 [details] temp.tar.bz2
This test does not and will not work without FEATURES="-usersandbox" - and there already is a warning about this in src_test().
(In reply to Marek Szuba from comment #8) > This test does not and will not work without FEATURES="-usersandbox" - and > there already is a warning about this in src_test(). No chance to bail out earlier if FEATURES doesn't have the appropriate settings?
I implemented it the same way other ebuilds we'd already had in the tree at the time handled such a situation. That said, given how simple it is to disable nodejs tests (at least the Javascript ones anyway, haven't looked at the C++ part of the test suite much) I have just implemented a different approach - the next batch of Node ebuilds, to be pushed to the tree as soon as I've finished build-testing them, will simply exclude the offending test if FEATURES=usersandbox is set. There is still a warning message but instead of telling the user to expect failures, it tells them that they are running with reduced test coverage.
