[Pkg-mozext-maintainers] [Enigmail] intermittent failing subprocess test on debian infrastructure

[Daniel Kahn Gillmor]

On Thu 2018-07-12 18:24:57 -0400, Daniel Kahn Gillmor wrote:
> On Tue 2018-07-10 11:27:17 -0400, Daniel Kahn Gillmor wrote:
>> Enigmail is in Debian unstable as of this morning, and should be on its
>> way back into debian's testing distribuation.
>
> One more piece of followup -- we have an intermittent failure of the
> test suite on debian continuous integration infrastructure:
>
> here are two instances of failure:
>
> https://ci.debian.net/data/autopkgtest/testing/amd64/e/enigmail/587942/log.gz
> https://ci.debian.net/data/autopkgtest/unstable/amd64/e/enigmail/586639/log.gz
>
> I think this is the error:
>
> --------------
> AssertionError: check error message - 18 == 0 - JS frame :: resource://jsunit/jsunit-main.jsm -> file:///tmp/autopkgtest-lxc.h2tft57_/downtmp/build.L2J/src/ipc/tests/subprocess-test.js :: run_test :: line 194
> minimal scenario with stdin and stdout separately
> JavaScript error: resource://enigmail/subprocess.jsm, line 359: uncaught exception: subprocess.jsm: caught error: 
> message: File closed
> fileName: resource://enigmail/enigmailprocess_worker_unix.js
> lineNumber: 554
> column: undefined
> stack: getPipe at resource://enigmail/enigmailprocess_worker_unix.js:554:19
> write at resource://enigmail/enigmailprocess_worker_common.js:190:18
> onmessage/<@resource://enigmail/enigmailprocess_worker_common.js:230:27
> onmessage at resource://enigmail/enigmailprocess_worker_common.js:229:3
>
> errorCode: 4286185473
> --------------
>
> I don't really understand what it means, and it doesn't always happen --
> in other runs of test suite, the subprocess works just fine.
>
> Does anyone else see this kind of failure?

You can see the intermittent failures here:

   https://ci.debian.net/packages/e/enigmail/unstable/amd64/

we've had a few more unpredictable failures since i reported it, so it
doesn't seem to be something that goes away on its own.

I'd be happy for pointers or ideas on how to resolve it.

    --dkg