Repository navigation
Update FreeBSD hosts to 12.4 or 13.x #3134
Description
Activity
Is this related to why the FreeBSD worker failed to launch on the latest libuv test job: https://ci.nodejs.org/job/libuv-test-commit-freebsd/2152/
I can't say. I have issues with the current FreeBSD hosts regarding C++20 support: https://ci.nodejs.org/job/node-test-commit-freebsd/49404/nodes=freebsd12-x64/console
- changed the title
[-]Update FreeBSD hosts to 12.4 or 13.1[/-][+]Update FreeBSD hosts to 12.4 or 13.x[/+]on May 3, 2023 I'll try to update https://ci.nodejs.org/manage/computer/test-digitalocean-freebsd12-x64-1/ to 12.4 today.
Test run: https://ci.nodejs.org/job/node-test-commit-freebsd/nodes=freebsd12-x64/49577/console
Clang is now on version 13.0.0, which should be enough for C++20.
- added a commit that references this issue
on May 3, 2023 Above test failed with:
15:28:02 not ok 3746 abort/test-signal-handler 15:28:02 --- 15:28:02 duration_ms: 0.189 15:28:02 severity: fail 15:28:02 exitcode: 1 15:28:02 stack: |- 15:28:02 node:assert:400 15:28:02 throw err; 15:28:02 ^ 15:28:02 15:28:02 AssertionError [ERR_ASSERTION]: child.signal = SIGBUS 15:28:02 at Object.<anonymous> (/usr/home/iojs/build/workspace/node-test-commit-freebsd/nodes/freebsd12-x64/test/abort/test-signal-handler.js:22:3) 15:28:02 at Module._compile (node:internal/modules/cjs/loader:1196:14) 15:28:02 at Object.Module._extensions..js (node:internal/modules/cjs/loader:1250:10) 15:28:02 at Module.load (node:internal/modules/cjs/loader:1074:32) 15:28:02 at Function.Module._load (node:internal/modules/cjs/loader:909:12) 15:28:02 at Function.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:81:12) 15:28:02 at node:internal/main/run_main_module:22:47 { 15:28:02 generatedMessage: false, 15:28:02 code: 'ERR_ASSERTION', 15:28:02 actual: false, 15:28:02 expected: true, 15:28:02 operator: '==' 15:28:02 } 15:28:02 ...New run: https://ci.nodejs.org/job/node-test-commit-freebsd/nodes=freebsd12-x64/49583/console
The test is definitely broken by this upgrade. I put the machine offline for now but it means we only have one left.
/cc @nodejs/platform-freebsd
- added a commit that references this issue
on May 4, 2023 Suggested fix for the test: nodejs/node#47851
- added a commit that references this issue
on May 5, 2023 Both machines were updated to v12.4
- added a commit that references this issue
on May 6, 2023 - added a commit that references this issue
on May 12, 2023 - added a commit that references this issue
on Jun 26, 2023 - added a commit that references this issue
on Jul 6, 2023 - added a commit that references this issue
on Jul 6, 2023 - added a commit that references this issue
on Feb 18, 2025 - added a commit that references this issue
on Jul 20, 2025
They are currently on 12.2, now EoL.
I don't know if updating to 12.4 would be a breaking change.
FreeBSD 12 will be EoL on December 31, 2023, so upgrading to 13 is something we might want to do soon anyway.
https://www.freebsd.org/releases/
https://www.freebsd.org/security/#sup