Dear Jonas, On Wed, Feb 15, 2023 at 12:32:54AM +0100, Jonas Smedegaard wrote: > Quoting Julian Gilbey (2023-02-14 23:24:08) > > I've just submitted node-webfont to ci.debian.net and had failures on > > three architectures. > [...] > > My guess is that s390x can't handle wasm, or something like that, but > > if that's not the issue, then I have no idea. This code is generated > > by emscripten, so I presumed it should be able to run on all > > architectures, but clearly I'm wrong! > > WASM _code_ is architecture agnostic, but emscripten as WASM _compiler_ > contains architecture-specific code. > > Beware that emscripten is lacking a maintainer for some time, so any > bugs there is unlikely to get fixed soon. > > (I used to maintain emscripten, but have been laid off from the job > sponsoring my work on that)
I'm really sorry to hear that - I do hope you find another job soon (or already have) - good luck! > > If these two architectures (s390x and ppc64el) can't handle it because > > of wasm, how can I specify that node-webfont should only be > > installable on certain architectures? Is there some package I should > > build-time and run-time depend on to enforce this? (node-webfont is > > currently an Architecture: all package.) > > When your package is arch-all and you experience CI failures for tests > on some exotic archs, then ask release time to ignore those tests. > > I have been told to do the same for Rust libraries that are arch-all but > depend on other arch-any libraries failing on s390x and ppc64el. Ah, OK, will do so! Best wishes, Julian -- Pkg-javascript-devel mailing list Pkg-javascript-devel@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel
