Michaël Zasso

Good news: Visual Studio 17.11.0 was just released and the build works again (at least on my PC)!

I connected a new host with Fedora 38 in https://github.com/nodejs/build/pull/3352: https://ci.nodejs.org/manage/computer/test-digitalocean-fedora38-x64-1/ Unfortunately, one test on `nodejs/node@main` fails consistently: https://ci.nodejs.org/job/node-test-commit-linux/nodes=fedora-latest-x64/52059/ ``` === release test-net-bytes-per-incoming-chunk-overhead === Path: pummel/test-net-bytes-per-incoming-chunk-overhead node:assert:399 throw err; ^...

I connected the machine to the CI and it picked up https://ci.nodejs.org/job/node-test-node-addon-api-new/nodes=fedora-latest-x64/7737/

Agent is now definitely connected: https://ci.nodejs.org/computer/test-digitalocean-fedora38-x64-1/ I'll monitor the jobs it takes over the next few days.

We now have two `fedora38` machines in CI. I disconnected https://ci.nodejs.org/computer/test-digitalocean-fedora34-x64-2/ and will replace it with `fedora37` when I get back to this.

I updated the OP because Fedora 37 is EoL and we have [issues with its GCC version](https://github.com/nodejs/node/pull/45427). Now I suggest these changes: - Replace both Fedora 32 and the single...

DigitalOcean:  Rackspace:  😞

FWIW Rackspace allows to upload custom images.

Rackspace no longer provides any option to create a vm using Fedora. I looked multiple times into uploading custom images, but the difficulty of that task is beyond my understanding....

I added another smaller image created with Photoshop. It's probably not too difficult to add support for the format but it requires careful reading of the spec and some refactoring...