Given following log snippets, their explanation, and nothing else, explain what failure, if any, occurred during build of this package.

  Snippets are in a format of [X] : [Y], where [X] is a log snippet, and [Y] is the explanation.

  Snippets are delimited with '================'.

  Drawing on information from all snippets, provide a concise explanation of the issue and recommend a solution.

  Explanation of the issue, and recommended solution, should take a handful of sentences.

  Snippets:

  [> fastify@5.2.2 unit
> borp --reporter=@jsumners/line-reporter --coverage --check-coverage

RangeError [ERR_OUT_OF_RANGE]: The value of "options.concurrency" is out of range. It must be >= 1 && <= 4294967295. Received 0
    at new Test (node:internal/test_runner/test:475:9)
    at createTestTree (node:internal/test_runner/harness:82:16)
    at run (node:internal/test_runner/runner:676:16)
    at runWithTypeScript (file:///opt/app-root/src/node_modules/borp/lib/run.js:237:12)
    at async file:///opt/app-root/src/node_modules/borp/borp.js:150:18 {
  code: 'ERR_OUT_OF_RANGE'
}
Test for image 'ubi10/nodejs-22:1' FAILED (exit code: 1)
Test for image 'ubi10/nodejs-22:1' FAILED (exit code: 1)]: [> fastify@5.2.2 unit
> borp --reporter=@jsumners/line-reporter --coverage --check-coverage

RangeError [ERR_OUT_OF_RANGE]: The value of "options.concurrency" is out of range. It must be >= 1 && <= 4294967295. Received 0
    at new Test (node:internal/test_runner/test:475:9)
    at createTestTree (node:internal/test_runner/harness:82:16)
    at run (node:internal/test_runner/runner:676:16)
    at runWithTypeScript (file:///opt/app-root/src/node_modules/borp/lib/run.js:237:12)
    at async file:///opt/app-root/src/node_modules/borp/borp.js:150:18 {
  code: 'ERR_OUT_OF_RANGE'
}
Test for image 'ubi10/nodejs-22:1' FAILED (exit code: 1)
Test for image 'ubi10/nodejs-22:1' FAILED (exit code: 1)]

Issue: Unit tests for fastify from upstream github repository failed.
Resolution: Please check upstream repository and fix this issue in upstream as well. Also please do not forget to report this issue, in case it is not fixed yet.