Closed Niteo closed 2 years ago
Hm, that certainly looks correct to me! What OS are you on? (including version number)
This is on Ubuntu 20.04.4 LTS (Linux version 5.4.0-107-generic).
Hm. A fresh clone on my own 20.04.4 system built fine with your instructions (except I hadn't actually installed yarn
on this particular Node version, I had to npm install -g yarn
after nvm use
). That's not completely clean because cargo
has global caches, but…
Ah, a thought: is this being run from a CLI-only shell? Maybe it's electron-mocha
that's the problem, since that only works inside a windowing environment. (You can see in our GitHub workflow that we run inside xvfb for a virtual display.) In theory we could use regular mocha
here; there's nothing Electron-specific, but if we're going to have automated tests they might as well match our intended use case.
Interesting. I was running it on a remote machine, so that's probably it...!
I tried building and testing it on another machine (Debian GNU/Linux 10) with X, and then everything works. Not sure how much sense it makes to switch from mocha
to electron-mocha
, a warning text might just be enough.
I talked with some other team members and we're going to switch to plain mocha
in the next release; electron-mocha
isn't adding much in practice.
This is great news! Looking forward to the next release.
Included in 0.17.0.
I've been following the steps to build libsignal for node:
Everything seems to build without errors (ends with
gyp info ok
), but when runningyarn test
I get a segmentation fault:I'm building from the latest commit: https://github.com/signalapp/libsignal/commit/916269c3e5c9cf685099b320c33996fc2f271481
Couldn't find any open or closed issues reporting the same error.