test: migrate stats/incr/nanmhmean to ULP-based assertions - #15125
Merged
Conversation
Ref: #11352 Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_012QwrWGg9D1Fp13W6tJv1gF --- type: pre_commit_static_analysis_report description: Results of running static analysis checks when committing changes. report: - task: lint_filenames status: passed - task: lint_editorconfig status: skipped - task: lint_markdown_pkg_readmes status: na - task: lint_markdown_docs status: na - task: lint_markdown status: na - task: lint_package_json status: na - task: lint_repl_help status: na - task: lint_javascript_src status: na - task: lint_javascript_cli status: na - task: lint_javascript_examples status: na - task: lint_javascript_tests status: passed - task: lint_javascript_benchmarks status: na - task: lint_python status: na - task: lint_r status: na - task: lint_c_src status: na - task: lint_c_examples status: na - task: lint_c_benchmarks status: na - task: lint_c_tests_fixtures status: na - task: lint_shell status: na - task: lint_typescript_declarations status: passed - task: lint_typescript_tests status: na - task: lint_license_headers status: passed ---
Contributor
Coverage Report
The above coverage report was generated for the changes in this PR. |
kgryte
marked this pull request as ready for review
September 10, 2026 04:53
This was referenced Sep 10, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Resolves a part of #11352.
Description
This pull request:
stats/incr/nanmhmeanfrom computed relative-tolerance comparisons (delta = abs( expected - actual )/tol = EPSILON * abs( expected ), asserted viat.equal( delta <= tol, ... )) to ULP-difference assertions using@stdlib/assert/is-almost-same-value.test/test.js. The package has notest/test.native.js, and the remaining assertions in the file are exact comparisons againstnull,NaN, and exactly representable values, which are correct as-is and are left unchanged.@stdlib/math/base/special/absand@stdlib/constants/float64/epsrequires, along with thedeltaandtolvariable declarations.if ( actual[ i ] === expected[ i ] ) { ... } else { ... }branch in the moving-harmonic-mean test into a single ULP assertion, matching the migrated idiom.Only a test file is changed; no implementation, fixture, or documentation changes are included.
ULP bounds
EPSILON * abs( expected )11.1 * EPSILON * abs( expected )2These are the minimum integer bounds
Nsuch thatisAlmostSameValue( actual, expected, N )holds at each site. They were measured independently of the test harness by computingulpDifference( actual, expected )directly at every assertion site, starting from a high bound (64, which passes) and tightening:0, 1, 1, 0, 1, 1, 1, 1, so1is the tightest bound covering the loop.N = 0fails on six of the eight elements (e.g.,2.4000000000000004vs.2.4, and2.769230769230769vs.2.7692307692307696).3.750000000000001against a hand-computed expected value of3.75, a difference of exactly2ULP, soN = 2is required andN = 1fails.Tightening either site by one ULP was verified to fail (7 of 31 assertions fail at
N - 1), confirming both bounds are minimal rather than merely sufficient.make test TESTS_FILTER=".*/stats/incr/nanmhmean/.*"was run twice at the final bounds with identical results: 31/31 passing on both runs, no failures, ruling out FMA/architecture-dependent flakiness on this platform.make eslint-tests TESTS_FILTER=".*/stats/incr/nanmhmean/.*"is clean.Related Issues
This pull request has the following related issues:
math/base/specialpackages from relative tolerance testing to ULP difference testing (tracking issue) #11352Questions
The second site requires
2ULP rather than1. This reflects the pre-existing test, which already used a loosened1.1 * EPSILONtolerance at that site (as opposed to the plainEPSILONused in the loop), so the looser bound is carried over rather than introduced here. The expected value is hand-computed from the textbook formula, so the extra ULP is accumulation error in the incremental algorithm relative to the closed-form value, not a regression. Flagging it in case a reviewer would prefer the expected value be adjusted instead; no change was made, since that would go beyond migrating the assertions.Other
The resulting diff mirrors the already-merged migration for the sibling package
stats/incr/nanmstdev(#15072), which has the same accumulator test structure.One environment note, which did not affect verification:
make install-node-modulesinitially failed withETARGETfores-object-atoms@^1.1.2. As previously observed in #15116, this is a stale local npm packument cache rather than a repository or registry problem;npm cache clean --forcefollowed bymake install-node-modulesandmake initsucceeded, and the full toolchain was available for this PR. Separately, thelint-editorconfig-filespre-commit step could not download theeditorconfig-checkerbinary in this sandbox and was skipped viaSKIP_LINT_EDITORCONFIG; the changed lines were checked manually for LF line endings, tab indentation, no trailing whitespace, and a final newline. All other pre-commit lint steps ran normally.Checklist
AI Assistance
If you answered "yes" above, how did you use AI assistance?
Disclosure
This PR was written primarily by Claude Code, running as an unattended scheduled task. It selected the package, studied previously migrated packages in the same family to match the established idiom, performed the migration, and determined the minimum passing ULP bound empirically at each assertion site.
@stdlib-js/reviewers
🤖 Generated with Claude Code
https://claude.ai/code/session_012QwrWGg9D1Fp13W6tJv1gF
Generated by Claude Code