npm ERR! Log files were not written due to an error writing to the directory: /homeless-shelter/.npm/_logs
npm ERR! You can rerun the command with `--loglevel=verbose` to see the logs in your terminal
+ exitHandler
+ exitCode=226
+ set +e
+ '[' -n '' ']'
+ ((  226 != 0  ))
+ runHook failureHook
+ local hookName=failureHook
+ shift
+ local 'hooksSlice=failureHooks[@]'
+ local hook
+ for hook in "_callImplicitHook 0 $hookName" ${!hooksSlice+"${!hooksSlice}"}
+ _eval '_callImplicitHook 0 failureHook'
+ declare -F '_callImplicitHook 0 failureHook'
+ eval '_callImplicitHook 0 failureHook'
++ _callImplicitHook 0 failureHook
++ local def=0
++ local hookName=failureHook
++ declare -F failureHook
++ type -p failureHook
++ '[' -n '' ']'
++ return 0
+ return 0
+ '[' -n '' ']'
+ return 226
   Compiling proc-macro2 v1.0.43

trap "exitHandler" EXIT

If a sigspec is 0 or EXIT, arg is executed when the shell exits.

nix-repl> builtins.baseNameOf bash
"p7bpdnxqd3i5hwm92mrscf7mvxk66404-bash-5.1-p16"

so it'll be embeded in the name

diff --git a/pkgs/build-support/trivial-builders/test-overriding.nix b/pkgs/build-support/trivial-builders/test-overriding.nix
index a16bbbee1b1..1ea8d7c0b90 100644
--- a/pkgs/build-support/trivial-builders/test-overriding.nix
+++ b/pkgs/build-support/trivial-builders/test-overriding.nix
@@ -91,7 +91,7 @@ let
   # works at run time.
   runTest = script:
     let
-      name = script.name or (builtins.baseNameOf script);
+      name = script.name or (builtins.unsafeDiscardStringContext (builtins.baseNameOf script));
     in writeShellScript "run-${name}" ''
       if [ "$(${script})" != "success" ]; then
         echo "Failed in ${name}"

makes it pass too

On x86_64 systems, x86_64 microarchitecture levels are mapped to additional system types (e.g. x86_64-v1-linux).