autopkgtest failure "DeprecationWarning: The legacy HTTP parser is deprecated."

[Bryce Harrington]

https://autopkgtest.ubuntu.com/results/autopkgtest-impish/impish/amd64/n/node-websocket-driver/20210803_073423_2d5a6@/log.gz

autopkgtest [07:34:07]: test require: [-----------------------
(node:1132) [DEP0131] DeprecationWarning: The legacy HTTP parser is deprecated.
autopkgtest [07:34:08]: test require: -----------------------]
autopkgtest [07:34:08]: test require: - - - - - - - - - - results - - - - - - - - - -
require FAIL stderr: (node:1132) [DEP0131] DeprecationWarning: The legacy HTTP parser is deprecated.
autopkgtest [07:34:08]: test require: - - - - - - - - - - stderr - - - - - - - - - -
(node:1132) [DEP0131] DeprecationWarning: The legacy HTTP parser is deprecated.

Same issue affects Debian, reported at https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=991820

"""

With a recent upload of nodejs (CVE related, but including more changes
than just that) the autopkgtest of node-websocket-driver fails in
testing when that autopkgtest is run with the binary packages of nodejs
from unstable. It passes when run with only packages from testing. In
tabular form:

                       pass fail
nodejs from testing 12.22.4~dfsg-1
node-websocket-driver from testing 0.3.5-1.1
all others from testing from testing

I copied some of the output at the bottom of this report. It seems that
the CVE fix deliberately made a parser deprecated, which results in a
*warning* to stderr. The default behavior of autopkgtest is to fail on
output to stderr.
"""

There is a newer node-websocket-driver 0.7.4+~cs0.6.7-1 in experimental, however I suspect that might require nodejs 14. Perhaps a better alternative would be to modify the 'require' test to allow stderr, or maybe filter the specific warning?

[Bryce Harrington (bryce)]

Here is a stab at filtering the particular error from stderr (but letting other stderr continue through). This kind of just papers over the issue, but it seems to work locally for me. It uses bash syntax so I had to change the test's interpreter.