Test citgm execution on RISC-V

[sxa]

We've got unofficial builds working well on RISC-V. It would be good to check the state of the module ecosystem on Linux/riscv64 with citgm.

I've got a couple of runs taking place on my boards at the moment and will add any findings into here.

Related to nodejs/build#4099

(Creating this today after seeing a post elsewhere about the module ecosystem on RISC-V from @gounthar - ref: https://fosstodon.org/@sxa/116979881114021674)

[sxa]

Full output is attached below but a quick summary from egrep '<testcase|<failure' report.xml | grep -B1 failure is here:

sxa@bananapif3:~/citgm$ egrep '<testcase|<failure' report.xml  | grep -B1 failure
  <testcase name="@nearform/bubbleprof-v7.0.1" time="469.55">
    <failure message="module test suite failed">Error: The canary is dead: </failure>
  <testcase name="@nearform/doctor-v8.1.0" time="402.061">
    <failure message="module test suite failed">Error: The canary is dead: </failure>
--
  <testcase name="acorn-v8.17.0" time="648.009">
    <failure message="module test suite failed">Error: Install Timed Out </failure>
  <testcase name="async-v3.2.6" time="198.488">
    <failure message="module test suite failed">Error: The canary is dead: </failure>
  <testcase name="ava-v8.0.1" time="743.554">
    <failure message="module test suite failed">Error: The canary is dead: </failure>
  <testcase name="bcrypt-v6.0.0" time="76.464">
    <failure message="module test suite failed">Error: Install Failed </failure>
--
  <testcase name="bluebird-v3.7.2" time="133.99">
    <failure message="module test suite failed">Error: The canary is dead: </failure>
--
  <testcase name="bufferutil-v4.1.0" time="42.832">
    <failure message="module test suite failed">Error: Install Failed </failure>
  <testcase name="cheerio-v1.2.0" time="118.806">
    <failure message="module test suite failed">Error: The canary is dead: </failure>
  <testcase name="clinic-v13.0.0" time="841.885">
    <failure message="module test suite failed">Error: Test Timed Out </failure>
  <testcase name="coffeescript-v2.7.0" time="206.433">
    <failure message="module test suite failed">Error: The canary is dead: </failure>
--
  <testcase name="crc32-stream-v7.0.1" time="27.484">
    <failure message="module test suite failed">Error: The canary is dead: </failure>
--
  <testcase name="ember-cli-v7.1.0" time="17.29">
    <failure message="module test suite failed">Error: Install Failed </failure>
--
  <testcase name="fastify-v5.10.0" time="609.652">
    <failure message="module test suite failed">Error: The canary is dead: </failure>
--
  <testcase name="gulp-v5.0.1" time="148.596">
    <failure message="module test suite failed">Error: The canary is dead: </failure>
--
  <testcase name="https-proxy-agent-v9.1.0" time="6.951">
    <failure message="module test suite failed">Error: incorrect header check </failure>
  <testcase name="iconv-v3.0.1" time="17.515">
    <failure message="module test suite failed">Error: Install Failed </failure>
  <testcase name="inherits-v2.0.4" time="154.239">
    <failure message="module test suite failed">Error: The canary is dead: </failure>
--
  <testcase name="jest-v30.4.2" time="198.903">
    <failure message="module test suite failed">Error: Install Failed </failure>
  <testcase name="jquery-v4.0.0" time="157.539">
    <failure message="module test suite failed">Error: The canary is dead: </failure>
--
  <testcase name="level-v10.0.0" time="214.836">
    <failure message="module test suite failed">Error: Install Failed </failure>
  <testcase name="leveldown-v6.1.1" time="242.553">
    <failure message="module test suite failed">Error: Install Failed </failure>
--
  <testcase name="microtime-v3.1.1" time="168.072">
    <failure message="module test suite failed">Error: Install Failed </failure>
--
  <testcase name="nan-v2.28.0" time="68.836">
    <failure message="module test suite failed">Error: The canary is dead: </failure>
  <testcase name="node-gyp-v13.0.1" time="756.558">
    <failure message="module test suite failed">Error: Test Timed Out </failure>
--
  <testcase name="npm-v12.0.1" time="935.28">
    <failure message="module test suite failed">Error: Test Timed Out </failure>
--
  <testcase name="pino-v10.3.1" time="925.203">
    <failure message="module test suite failed">Error: Test Timed Out </failure>
--
  <testcase name="q-v1.5.1" time="55.466">
    <failure message="module test suite failed">Error: Install Failed </failure>
--
  <testcase name="rewire-v9.0.1" time="85.835">
    <failure message="module test suite failed">Error: The canary is dead: </failure>
  <testcase name="rimraf-v6.1.3" time="302.082">
    <failure message="module test suite failed">Error: The canary is dead: </failure>
  <testcase name="router-v2.2.0" time="111.741">
    <failure message="module test suite failed">Error: The canary is dead: </failure>
--
  <testcase name="semver-v7.8.5" time="321.118">
    <failure message="module test suite failed">Error: The canary is dead: </failure>
  <testcase name="serialport-v13.0.0" time="197.642">
    <failure message="module test suite failed">Error: Install Failed </failure>
--
  <testcase name="sqlite3-v6.0.1" time="146.222">
    <failure message="module test suite failed">Error: Install Failed </failure>
--
  <testcase name="tape-v5.10.2" time="234.425">
    <failure message="module test suite failed">Error: The canary is dead: </failure>
--
  <testcase name="tough-cookie-v6.0.2" time="80.153">
    <failure message="module test suite failed">Error: The canary is dead: </failure>
--
  <testcase name="undici-v8.9.0" time="730.575">
    <failure message="module test suite failed">Error: Test Timed Out </failure>
  <testcase name="uuid-v14.0.1" time="140.021">
    <failure message="module test suite failed">Error: Install Failed </failure>
--
  <testcase name="winston-v3.19.0" time="180.831">
    <failure message="module test suite failed">Error: The canary is dead: </failure>
  <testcase name="ws-v8.21.1" time="105.564">
    <failure message="module test suite failed">Error: Install Failed </failure>
  <testcase name="yargs-v18.0.0" time="276.612">
    <failure message="module test suite failed">Error: The canary is dead: </failure>
  <testcase name="yeoman-generator-v8.2.2" time="513.365">
    <failure message="module test suite failed">Error: The canary is dead: </failure>
sxa@bananapif3:~/citgm$ 

report.xml.gz

nohup.out.gz

[sxa]

And from a run on a K3:

  <testcase name="@hapi/shot-v6.0.3" time="9.629">
    <failure message="module test suite failed">Error: Install Failed </failure>
  <testcase name="@nearform/bubbleprof-v7.0.1" time="13.794">
    <failure message="module test suite failed">Error: Install Failed </failure>
  <testcase name="@nearform/doctor-v8.1.0" time="14.69">
    <failure message="module test suite failed">Error: Install Failed </failure>
  <testcase name="@nearform/flame-v9.1.0" time="8.515">
    <failure message="module test suite failed">Error: Install Failed </failure>
--
  <testcase name="acorn-v8.17.0" time="293.255">
    <failure message="module test suite failed">Error: Install Failed </failure>
  <testcase name="async-v3.2.6" time="64.451">
    <failure message="module test suite failed">Error: The canary is dead: </failure>
  <testcase name="ava-v8.0.1" time="422.14">
    <failure message="module test suite failed">Error: The canary is dead: </failure>
  <testcase name="bcrypt-v6.0.0" time="12.576">
    <failure message="module test suite failed">Error: Install Failed </failure>
--
  <testcase name="bluebird-v3.7.2" time="38.148">
    <failure message="module test suite failed">Error: The canary is dead: </failure>
--
  <testcase name="bufferutil-v4.1.0" time="13.053">
    <failure message="module test suite failed">Error: Install Failed </failure>
  <testcase name="cheerio-v1.2.0" time="19.798">
    <failure message="module test suite failed">Error: The canary is dead: </failure>
  <testcase name="clinic-v13.0.0" time="11.57">
    <failure message="module test suite failed">Error: Install Failed </failure>
  <testcase name="coffeescript-v2.7.0" time="62.757">
    <failure message="module test suite failed">Error: The canary is dead: </failure>
--
  <testcase name="crc32-stream-v7.0.1" time="6.909">
    <failure message="module test suite failed">Error: The canary is dead: </failure>
--
  <testcase name="ember-cli-v7.1.0" time="4.581">
    <failure message="module test suite failed">Error: Install Failed </failure>
--
  <testcase name="fastify-v5.10.0" time="14.583">
    <failure message="module test suite failed">Error: Install Failed </failure>
--
  <testcase name="https-proxy-agent-v9.1.0" time="1.844">
    <failure message="module test suite failed">Error: incorrect header check </failure>
  <testcase name="iconv-v3.0.1" time="4.377">
    <failure message="module test suite failed">Error: Install Failed </failure>
  <testcase name="inherits-v2.0.4" time="57.783">
    <failure message="module test suite failed">Error: The canary is dead: </failure>
--
  <testcase name="jest-v30.4.2" time="53.754">
    <failure message="module test suite failed">Error: Install Failed </failure>
  <testcase name="jquery-v4.0.0" time="38.314">
    <failure message="module test suite failed">Error: The canary is dead: </failure>
--
  <testcase name="level-v10.0.0" time="66.67">
    <failure message="module test suite failed">Error: Install Failed </failure>
  <testcase name="leveldown-v6.1.1" time="71.575">
    <failure message="module test suite failed">Error: Install Failed </failure>
--
  <testcase name="microtime-v3.1.1" time="44.106">
    <failure message="module test suite failed">Error: Install Failed </failure>
--
  <testcase name="nan-v2.28.0" time="20.137">
    <failure message="module test suite failed">Error: The canary is dead: </failure>
  <testcase name="node-gyp-v13.0.1" time="644.795">
    <failure message="module test suite failed">Error: Test Timed Out </failure>
--
  <testcase name="npm-v12.0.1" time="317.61">
    <failure message="module test suite failed">Error: The canary is dead: </failure>
--
  <testcase name="pino-v10.3.1" time="420.275">
    <failure message="module test suite failed">Error: The canary is dead: </failure>
  <testcase name="prom-client-v15.1.3" time="13.807">
    <failure message="module test suite failed">Error: Install Failed </failure>
--
  <testcase name="q-v1.5.1" time="17.907">
    <failure message="module test suite failed">Error: Install Failed </failure>
--
  <testcase name="rewire-v9.0.1" time="20.876">
    <failure message="module test suite failed">Error: The canary is dead: </failure>
  <testcase name="rimraf-v6.1.3" time="142.527">
    <failure message="module test suite failed">Error: The canary is dead: </failure>
  <testcase name="router-v2.2.0" time="35.687">
    <failure message="module test suite failed">Error: The canary is dead: </failure>
--
  <testcase name="semver-v7.8.5" time="8.405">
    <failure message="module test suite failed">Error: Install Failed </failure>
  <testcase name="serialport-v13.0.0" time="40.747">
    <failure message="module test suite failed">Error: Install Failed </failure>
--
  <testcase name="sqlite3-v6.0.1" time="43.324">
    <failure message="module test suite failed">Error: Install Failed </failure>
--
  <testcase name="tape-v5.10.2" time="18.082">
    <failure message="module test suite failed">Error: Install Failed </failure>
--
  <testcase name="through2-v5.0.7" time="8.122">
    <failure message="module test suite failed">Error: Install Failed </failure>
--
  <testcase name="tough-cookie-v6.0.2" time="19.006">
    <failure message="module test suite failed">Error: The canary is dead: </failure>
--
  <testcase name="undici-v8.9.0" time="629.679">
    <failure message="module test suite failed">Error: Test Timed Out </failure>
  <testcase name="uuid-v14.0.1" time="30.483">
    <failure message="module test suite failed">Error: Install Failed </failure>
--
  <testcase name="ws-v8.21.1" time="22.74">
    <failure message="module test suite failed">Error: Install Failed </failure>
--
  <testcase name="yeoman-generator-v8.2.2" time="135.028">
    <failure message="module test suite failed">Error: The canary is dead: </failure>

report.xml.gz

nohup.out.gz

[gounthar]

I went through the two report.xml and nohup pairs you attached. One thing stands out that I think makes a chunk of the table unreliable, though I might be misreading how you invoked it.

Every native addon fails at node-gyp configure, before compiling anything:

gyp WARN read config.gypi ENOENT: ... open '/home/iojs/citgm/include/node/config.gypi'
gyp: /home/iojs/citgm/common.gypi not found (cwd: .../bcrypt) while reading includes of binding.gyp

npm_config_nodedir is pointing at the citgm checkout itself, /home/sxa/citgm on the F3 and /home/iojs/citgm on the K3, and neither contains common.gypi or include/node/config.gypi. citgm only sets that variable when you pass -d/--nodedir, and it resolves relative to cwd (lib/create-options.js), so citgm-all -d . from the citgm directory would produce exactly this. 17 occurrences in the F3 run, 21 in the K3 one, covering bcrypt, bufferutil, iconv, level/classic-level, leveldown, microtime, serialport (@parcel/watcher), sqlite3 and ws. Dropping -d, or pointing it at real headers, should clear that whole class.

Two smaller things from the same logs. uuid looks like a genuine riscv64 gap: it dies in lefthook/get-exe.js, which has no riscv64 binary to find. ember-cli and q are architecture-independent, EUNSUPPORTEDPROTOCOL on a workspace: dependency and a grunt postinstall exiting 3. The F3 run also hit ENOSPC: no space left on device at least once, so one result there is void regardless.

Probably worth saying for anyone reading those tables that "The canary is dead:" is just citgm's message for npm test exiting non-zero (lib/package-manager/test.js), not a Node crash. It reads far more alarming than it is.

One last thing I wasn't sure about: both runs use the pointer-compression build. Is that deliberate? If the aim is to characterise the module ecosystem rather than that specific configuration, a stock riscv64 build might be the fairer baseline, but you may well have a reason for it that I'm missing.

[sxa]

I'll be honest I just uploaded the files and hadn't made any real effort to diagnose them yet due to other higher priority stuff so thanks for the initial look! Yeah sounds like I didn't have the headers available in the right place as you say.
An absence of RISC-V binaries isn't a surprose for some modules but it'll be useful to see which modules are in that category so that's good to see.
The unofficial builds are currently all with pointer compression enabled, but I can easily test with a build with it enabled if we think it'll make a difference to any of the tests. There is an issue around from someone who wanted builds with it enabled and RISC-V seemed like a reasonable choice of build to have it switched on. But honestly, the main reason I 'm building with it enabled by default was mainly because I do run a personal Node.js+MySQL server on a D1 board with very limited RAM so having pointer compression will help with the memory usage, so it's mostly for selfish reasons ;-)

if we ever got RISC-V promoted to be a tier 2 platform we can make a decision on whether to have it on or off. I did initially have the unofficial builds system configured to have a GCC build without PC and a clang build with PC (e.g. 25.9.0) but no-one has objected to it being on from when I enabled it. That might change once the server-class boards start to become readily available.

[sxa]

Updated version from the K3:

• report.xml.gz
• nohup.out.gz

Updated results from BPi-F3:

• report.xml.gz
• nohup.out.gz

[gounthar]

This has been sitting half written since the end of July, sorry. Going back over the two 2026-07-28 runs now, with one thing I have been able to settle on hardware since.

Headline first: 74 of the 115 modules pass on both boards, 33 fail on both, 6 fail only on the F3 and 2 only on the K3. The header path is fixed, common.gypi not found and the config.gypi ENOENT are both at zero across the two logs, and bcrypt, bufferutil, iconv and ws now build and pass on both.

Pointer compression is doing real damage to the native addon results

You asked back in July whether pointer compression would make a difference to any of the tests. It does, and I think it makes a chunk of the addon table unreadable rather than just noisy.

The stock v26.5.0 headers from nodejs.org carry "v8_enable_pointer_compression": 0 in include/node/config.gypi:508, and common.gypi:515 is what turns that key into the V8_COMPRESS_POINTERS define for addons. Your runtime reports v8_enable_pointer_compression: 1, shared_cage: 0. So node-gyp compiles every addon for an uncompressed heap and then loads it into a compressed one.

So I tested it on a BananaPi F3 against the same runtime instead of leaving it as a theory. Same source file, same g++ 14.2, same runtime, the only variable being whether the two defines the runtime was built with are passed:

addon built as	result in the PC runtime
stock headers, as node-gyp would	SIGSEGV, exit 139
plus -DV8_COMPRESS_POINTERS -DV8_COMPRESS_POINTERS_IN_MULTIPLE_CAGES	runs clean

Worth knowing which calls do it, since I think it explains the pattern in your results. An addon that only makes out-of-line API calls (Object::Set, Object::Get, String::Utf8Value) survives the mismatch, and my first attempt at this test passed for exactly that reason. What dies is the inlined fast paths in v8.h, the ones compiled into the addon itself: Value::IsString() and friends reading the map word, and GetAlignedPointerFromInternalField. Both segfault immediately.

That would explain the shape of your table. The N-API modules (bcrypt, ws, bufferutil) go through the stable C ABI and pass. nan sits directly on those inline paths, and nan on the K3 fails with 42 separate signal: SIGSEGV, one per addon test file, and nothing else. The F3 nan run timed out before it got that far, so it has none.

I do not think the answer is to turn pointer compression off. It is that an addon needs headers from the same configuration as the runtime, and anyone installing an addon against these builds hits this by default because node-gyp fetches the stock headers. A run against a non-PC build would still be useful as a control, to see how much of the remaining table moves, though I notice unofficial-builds only publishes the pointer-compression variant for riscv64 right now.

Which failures are actually riscv64 specific

Genuinely missing riscv64 binaries, all three confirmed in the logs as Cannot find module:

• @swc/core-linux-riscv64-gnu (jquery)
• @rolldown/binding-linux-riscv64-gnu (tough-cookie, yeoman-generator)
• lefthook-linux-riscv64 (uuid)

Plus leveldown's dev dependency on electron, which 404s on electron-v17.4.11-linux-riscv64.zip. These are upstream packaging gaps rather than anything Node is doing. One update since the run: a @rolldown/binding-linux-riscv64-gnu placeholder went up on 2026-08-12, version 0.0.0 at 941 bytes and two files, so no binary yet, though somebody looks to be preparing one.

One real source level gap. level fails because classic-level bundles leveldb 1.20, which predates the switch to std::atomic:

../deps/leveldb/leveldb-1.20/port/atomic_pointer.h:229:2: error: #error Please implement AtomicPointer for this platform.

Would fail on any architecture

ember-cli hits EUNSUPPORTEDPROTOCOL on workspace:*, q's grunt run wants _stream_transform, cheerio has no test:jest script, crc32-stream and router hit require is not defined in ES module scope, and npm's own failures include needing git in PATH plus some path normalisation diffs.

Two host side things

microtime and serialport fail on the F3 only, both with No module named 'distutils', which the bundled node-gyp 9.4.1 still wants, so python3-setuptools on that box should clear them.

On the K3 there are nine modules (acorn, fastify, tape, semver, prom-client, clinic, jest, bubbleprof, flame) where the only thing captured is the npm debug-log path with no error body, so there is nothing to go on from the log alone. Good news is there is no ENOSPC anywhere this time.

[sxa]

This has been sitting half written since the end of July, sorry.

No problem - it wouldn't have been looked at at all yet if it wasn't for you! That's great information you'd added.

I do not think the answer is to turn pointer compression off.

Agreed.

A run against a non-PC build would still be useful as a control, to see how much of the remaining table moves, though I notice unofficial-builds only publishes the pointer-compression variant for riscv64 right now.

We still have both for v24 e.g. https://unofficial-builds.nodejs.org/download/release/v24.19.0/ so maybe we should re-run with that. I think I left the non-pointer-compression one building with gcc so if that still works (I haven't tried it on 26 recently) I could also re-enable that for 26 especially while we're testing stuff.

[sxa]

New results from the K3 with no pointer compression and sane (ish) headers:

Details

`egrep '

  <testcase name="@nearform/bubbleprof-v7.0.1" time="127.364">
    <failure message="module test suite failed">Error: The canary is dead: </failure>
--
  <testcase name="async-v3.2.6" time="73.191">
    <failure message="module test suite failed">Error: The canary is dead: </failure>
  <testcase name="ava-v8.0.1" time="353.462">
    <failure message="module test suite failed">Error: The canary is dead: </failure>
  <testcase name="bcrypt-v6.0.0" time="15.45">
    <failure message="module test suite failed">Error: Install Failed </failure>
--
  <testcase name="bluebird-v3.7.2" time="44.321">
    <failure message="module test suite failed">Error: The canary is dead: </failure>
--
  <testcase name="bufferutil-v4.1.0" time="15.722">
    <failure message="module test suite failed">Error: Install Failed </failure>
  <testcase name="cheerio-v1.2.0" time="24.743">
    <failure message="module test suite failed">Error: The canary is dead: </failure>
  <testcase name="clinic-v13.0.0" time="689.051">
    <failure message="module test suite failed">Error: Test Timed Out </failure>
  <testcase name="coffeescript-v2.7.0" time="83.328">
    <failure message="module test suite failed">Error: The canary is dead: </failure>
--
  <testcase name="crc32-stream-v7.0.1" time="9.568">
    <failure message="module test suite failed">Error: The canary is dead: </failure>
--
  <testcase name="ember-cli-v7.2.0" time="6.79">
    <failure message="module test suite failed">Error: Install Failed </failure>
--
  <testcase name="https-proxy-agent-v9.1.0" time="2.66">
    <failure message="module test suite failed">Error: incorrect header check </failure>
  <testcase name="iconv-v3.0.1" time="5.33">
    <failure message="module test suite failed">Error: Install Failed </failure>
  <testcase name="inherits-v2.0.4" time="62.481">
    <failure message="module test suite failed">Error: The canary is dead: </failure>
--
  <testcase name="jest-v30.5.1" time="96.864">
    <failure message="module test suite failed">Error: Install Failed </failure>
  <testcase name="jquery-v4.0.0" time="50.007">
    <failure message="module test suite failed">Error: The canary is dead: </failure>
--
  <testcase name="level-v10.0.0" time="81.811">
    <failure message="module test suite failed">Error: Install Failed </failure>
  <testcase name="leveldown-v6.1.1" time="81.276">
    <failure message="module test suite failed">Error: Install Failed </failure>
--
  <testcase name="microtime-v3.1.1" time="55.807">
    <failure message="module test suite failed">Error: Install Failed </failure>
--
  <testcase name="nan-v2.28.0" time="25.285">
    <failure message="module test suite failed">Error: The canary is dead: </failure>
  <testcase name="node-gyp-v13.0.2" time="92.945">
    <failure message="module test suite failed">Error: The canary is dead: </failure>
--
  <testcase name="npm-v12.0.2" time="571.674">
    <failure message="module test suite failed">Error: The canary is dead: </failure>
--
  <testcase name="pino-v10.3.1" time="516.413">
    <failure message="module test suite failed">Error: The canary is dead: </failure>
--
  <testcase name="q-v1.5.1" time="20.833">
    <failure message="module test suite failed">Error: Install Failed </failure>
--
  <testcase name="rewire-v9.0.1" time="33.589">
    <failure message="module test suite failed">Error: The canary is dead: </failure>
  <testcase name="rimraf-v6.1.3" time="185.597">
    <failure message="module test suite failed">Error: The canary is dead: </failure>
  <testcase name="router-v2.2.0" time="39.963">
    <failure message="module test suite failed">Error: The canary is dead: </failure>
--
  <testcase name="semver-v7.8.5" time="155.571">
    <failure message="module test suite failed">Error: The canary is dead: </failure>
  <testcase name="serialport-v13.0.0" time="62.942">
    <failure message="module test suite failed">Error: Install Failed </failure>
--
  <testcase name="sqlite3-v6.0.1" time="48.986">
    <failure message="module test suite failed">Error: Install Failed </failure>
--
  <testcase name="tape-v5.10.2" time="89.018">
    <failure message="module test suite failed">Error: The canary is dead: </failure>
--
  <testcase name="tough-cookie-v6.0.2" time="27.269">
    <failure message="module test suite failed">Error: The canary is dead: </failure>
--
  <testcase name="undici-v8.10.1" time="658.991">
    <failure message="module test suite failed">Error: Test Timed Out </failure>
  <testcase name="uuid-v14.0.2" time="47.858">
    <failure message="module test suite failed">Error: Install Failed </failure>
--
  <testcase name="ws-v8.21.3" time="29.953">
    <failure message="module test suite failed">Error: Install Failed </failure>
--
  <testcase name="yeoman-generator-v8.3.0" time="193.893">
    <failure message="module test suite failed">Error: The canary is dead: </failure>

Updated full files:

• report.xml.gz
• nohup.out.gz

Most of the analysis by @gounthar earlier is still valid and perhaps we should chuck these into a table with either:

• Fails everywhere anyway
• Absent binaries from the project on RISC-V
• Native code not working on RISC-V
• Other RISC-V specific problems
• Not enough info to diagnose
• Failing due to the absence of setuptools which I don't think I fixed before this run :-)
• "Something else"