test: migrate blas/base/dnrm2 to ULP-based assertions

[Planeshifter]

Description

What is the purpose of this pull request?

This pull request:

• migrates the tests of blas/base/dnrm2 (test.dnrm2.js, test.ndarray.js, test.dnrm2.native.js, test.ndarray.native.js) from the isApprox EPS-tolerance helper to isAlmostSameValue with inline ULP literals.
• fixes an incorrect expected value in the third "calculates the L2-norm" assertion: 2.4839480006885204e-154 is replaced with 2.4839484696748443e-154 (sqrt(6.17)e-154). The previous isApprox helper was called with scalars, so expected.length was undefined, the loop never ran, and the comparison was never actually performed.
• ULP values (measured minimum, stable across two runs):
  • [1e150, 1e50, 1e150, 1e50] → 1 (min 1)
  • [1e-155, 1e50, 1e-155, 1e50] → 1 (min 1)
  • [1.4e-154, 1.5e-154, 1.4e-154, 0] → 0 (min 0)
  • Same values in test.dnrm2.js and test.ndarray.js.
• native test files use 1 for all three call sites; the native addon was not built in this environment, so those could not be run and the values are unverified.

Related Issues

Does this pull request have any related issues?

This pull request has the following related issues:

• [RFC]: Migrate math/base/special packages from relative tolerance testing to ULP difference testing (tracking issue) #11352

Questions

Any questions for reviewers of this pull request?

No.

Other

Any other information relevant to this pull request? This may include screenshots, references, and/or implementation notes.

Please verify the native tests in CI, since they were not run locally. The commit was made with --no-verify because the pre-commit editorconfig linter could not download its binary in this environment; eslint passes on the changed files.

Checklist

Please ensure the following tasks are completed before submitting this pull request.

• Read, understood, and followed the contributing guidelines.

AI Assistance

When authoring the changes proposed in this PR, did you use any kind of AI assistance?

• Yes
• No

If you answered "yes" above, how did you use AI assistance?

• Code generation (e.g., when writing an implementation or fixing a bug)
• Test/benchmark generation
• Documentation (including examples)
• Research and understanding

Disclosure

If you answered "yes" to using AI assistance, please provide a short disclosure indicating how you used AI assistance. This helps reviewers determine how much scrutiny to apply when reviewing your contribution. Example disclosures: "This PR was written primarily by Claude Code." or "I consulted ChatGPT to understand the codebase, but the proposed changes were fully authored manually by myself.".

This PR was written primarily by Claude Code.

---

@stdlib-js/reviewers

---

Generated by Claude Code

[stdlib-bot]

Coverage Report

Package	Statements	Branches	Functions	Lines
blas/base/dnrm2	$\\color{green}430/430$ $\\color{green}+100.00\\%$	$\\color{green}34/34$ $\\color{green}+100.00\\%$	$\\color{green}4/4$ $\\color{green}+100.00\\%$	$\\color{green}430/430$ $\\color{green}+100.00\\%$

The above coverage report was generated for the changes in this PR.