• Home
  • Features
  • Pricing
  • Docs
  • Announcements
  • Sign In

ponder-lab / Hybridize-Functions-Refactoring / #2774
84%

Build:
DEFAULT BRANCH: main
Ran 07 Aug 2026 03:35AM UTC
Jobs 1
Files 40
Run time 1min
Badge
Embed ▾
README BADGES
x

If you need to use a raster PNG badge, change the '.svg' to '.png' in the link

Markdown

Textile

RDoc

HTML

Rst

07 Aug 2026 03:25AM UTC coverage: 83.898% (+0.2%) from 83.677%
#2774

push

github

web-flow
Pin or decline on eager-effective dtype for NumPy arguments (#866)

* Add the implicitly-cast NumPy argument fixture and probe scaffold

Reduces [linear_regression from #861 Case 1](https://github.com/ponder-lab/Hybridize-Functions-Refactoring/issues/861): a float32 module-scope variable combined with a float64 NumPy call-site argument. All three subject behaviors reproduce on the reduction under TF 2.9.3: undecorated runs (float32), a bare decorator raises the Mul dtype TypeError, and a signature pinned to the variable's dtype runs and matches eager. The scaffold test asserts candidacy only; its assertions harden when the eager-effective dtype detector lands. The analysis currently types the parameter float64 with shape [10] while the scalar-initialized variables stay dtype-unknown ([wala/ML#827](https://github.com/wala/ML/issues/827) tracks the initializer derivation).

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01AM8pvSeP5UqDyyTn9h5E2P

* Pin or decline on the eager-effective dtype a NumPy argument's consumers impose

Implements the [#861 Case 1](https://github.com/ponder-lab/Hybridize-Functions-Refactoring/issues/861) design settled on the issue thread: collect, over each parameter's direct binary-op consumers, the dtype eager coercion would impose there from the partner operand's tensor typing. A singleton set diverging from the argument evidence pins the emitted spec's dtype, whose boundary cast reproduces eager's per-op coercion; a plural set declines with HAS_CONFLICTING_EAGER_DTYPE_COERCIONS (code 22), since parallel consumptions under different dtypes admit no single signature. A ⊤ partner leaves the parameter indeterminate, firing neither. The compute must precede the static-shape-read check in the processor: that check materializes the memoized signature, and a later-computed pin would miss the emitted spec.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Claude-Session: ht... (continued)

88 of 95 new or added lines in 4 files covered. (92.63%)

3168 of 3776 relevant lines covered (83.9%)

0.84 hits per line

Uncovered Changes

Lines Coverage ∆ File
6
91.43
-0.05% edu.cuny.hunter.hybridize.core/src/edu/cuny/hunter/hybridize/core/analysis/Function.java
1
96.43
edu.cuny.hunter.hybridize.core/src/edu/cuny/hunter/hybridize/core/analysis/EagerCoercionAnalysis.java
Jobs
ID Job ID Ran Files Coverage
1 #2774.1 07 Aug 2026 03:35AM UTC 40
83.9
Source Files on build #2774
  • Tree
  • List 40
  • Changed 3
  • Source Changed 3
  • Coverage Changed 3
Coverage ∆ File Lines Relevant Covered Missed Hits/Line
  • Back to Repo
  • 69db22a3 on github
  • Prev Build on main
  • Next Build on main
STATUS · Troubleshooting · Open an Issue · Sales · Support · CAREERS · ENTERPRISE · START FREE TRIAL · SCHEDULE DEMO
ANNOUNCEMENTS · TWITTER · TOS & SLA · Supported CI Services · What's a CI service? · Automated Testing

© 2026 Coveralls, Inc