Hi, The above panic is repeatable - just build the latest version of nodejs and run 'make test': .... Command: out/Release/node /usr/pkgsrc/lang/nodejs/work/node-v13.12.0/test/parallel/test-process-execpath.js [01:07|% 57|+ 1694|- 4]: release test-process-uncaught-exception-monitor .....
This is the point when the panic takes place. On Tue, 7 Apr 2020 at 12:10, Chavdar Ivanov <[email protected]> wrote: > > Hi, > > On NetBSD 9.99.54 (GENERIC) #0: Sun Apr 5 11:58:20 BST 2020 I just got: > ... > panic: kernel diagnostic assertion "semcnt >= 0" failed: file > "/home/sysbuild/src/sys/kern/kern_uidinfo.c", line 241 > cpu4: Begin traceback... > vpanic() at netbsd:vpanic+0x178 > kern_assert() at netbsd:kern_assert+0x48 > chgsemcnt() at netbsd:chgsemcnt+0x56 > ksem_release() at netbsd:ksem_release+0x4c > ksem_close_fop() at netbsd:ksem_close_fop+0x49 > closef() at netbsd:closef+0x69 > fd_close() at netbsd:fd_close+0x1fd > sys__ksem_destroy() at netbsd:sys__ksem_destroy+0x9c > syscall() at netbsd:syscall+0x299 > --- syscall (number 255) --- > 7d67f18437ba: > cpu4: End traceback... > .... > > This was after about 36 hours uptime while I was running 'make test' > in lang/nodejs. > > > -- > ---- -- ----
