Conversation
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## master #329 +/- ##
=========================================
Coverage 100.00% 100.00%
=========================================
Files 3 3
Lines 24 24
Branches 11 11
=========================================
Hits 24 24 Continue to review full report in Codecov by Harness.
🚀 New features to boost your workflow:
|
Flamefire
force-pushed
the
node24
branch
9 times, most recently
from
66bb6a0 to
442a74b
Compare
Flamefire
force-pushed
the
node24
branch
19 times, most recently
from
98411be to
f38ef7f
Compare
Flamefire
force-pushed
the
node24
branch
2 times, most recently
from
08f248e to
35c5e97
Compare
Backtrace: ``` Thread 9 "libuv-worker" received signal SIGSEGV, Segmentation fault. ``` As this couldn't be resolved by e.g. passing different flags to `node` editing `/etc/nsswitch.conf` to move "dns" to the front in `hosts` works, although is more invasive.
This reverts commit 261123f.
Avoids the Segfaults with Node 24 and actions seem to still work with that.
|
Hardest part was a segfault with Node 24 in GLIBC 2.17 inside libnss_files.so.2 (around _nss_files_gethostbyname3_r) Run successful with the Node workaround: Basically we use Node 20 now and install it into the folders where GHA expects Node 20 AND in that of Node 24 This may break at some point when we update an action and that actually requires Node 24 features. But until then this should be fine. |
1 participant
Fixes #328