bug#37421: [PATCH] gnu: node: Disable tests that fail with openssl@1.1.1d.

Tobias Geerinckx-Rice writes: > Ludovic Courtès 写道： >> Could we take a look at what these failures are about to see how >> bad >> that might be? > > Jelle Licht 写道： >> Interestingly enough, https://github.com/nodejs/node/issues/3881 >> notes >> issues with exactly these two tests. Perhaps there

bug#37421: [PATCH] gnu: node: Disable tests that fail with openssl@1.1.1d.

Ludovic Courtès 写道： Could we take a look at what these failures are about to see how bad that might be? Jelle Licht 写道： Interestingly enough, https://github.com/nodejs/node/issues/3881 notes issues with exactly these two tests. Perhaps there is a regressions in our case? Thanks, and indee

bug#37421: [PATCH] gnu: node: Disable tests that fail with openssl@1.1.1d.

Ludovic Courtès writes: > Hello, > > Tobias Geerinckx-Rice via Bug reports for GNU Guix > skribis: > >> Work around . >> >> * gnu/packages/node.scm (node)[arguments]: Disable failing tests. > > [...] > >> + ;; FIXME: These tests fa

bug#37421: [PATCH] gnu: node: Disable tests that fail with openssl@1.1.1d.

Hello, Tobias Geerinckx-Rice via Bug reports for GNU Guix skribis: > Work around . > > * gnu/packages/node.scm (node)[arguments]: Disable failing tests. [...] > + ;; FIXME: These tests fail with openssl@1.1.1d. > + (f

bug#37421: [PATCH] gnu: node: Disable tests that fail with openssl@1.1.1d.

Work around . * gnu/packages/node.scm (node)[arguments]: Disable failing tests. --- Jelle, Guix, So here's the obvious non-solution, ignoring test failures being the lesser evil compared to 4 potential CVEs anywhere in a Web browser's closure