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

ponder-lab / Hybridize-Functions-Refactoring / #2850
85%
main: 85%

Build:
Build:
LAST BUILD BRANCH: fcb0d91132da029cb55d766340a624866a5feda5
DEFAULT BRANCH: main
Ran 09 Aug 2026 12:20AM UTC
Jobs 1
Files 42
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

09 Aug 2026 12:15AM UTC coverage: 84.704%. First build
#2850

Pull #892

github

khatchad
Pin the dict-parameter and reconfigure populations #890 left blind

Neither population had a fixture, which is why widening the container gate
to every container and letting a container verdict outrank a parameter's
own typing could leave a green suite. Both are pinned as properties rather
than as recorded defects: the current answers are the ones wanted.

`score` takes a dict of tensors, the multi-input Keras shape and the form
deep_recommenders' estimator rankers take as `call(self, features)`. It
classifies through the container check, the nested reduction models only
positionally-indexed sequences, so the form is reported unsupported and
the function hybridizes bare at P1. Worth being exact about what #890
would have moved here: a dict-only parameter already reaches the container
check, since the dict itself carries no tensor type, so only a dict
arriving beside a tensor-typed value would have been rerouted. The pin
covers the base case.

`train_step` reduces TensorFlow2.0-Examples' CNN.py: already hybrid with a
bare decorator, two tensor parameters, no Python literal, and the variable
collection read after the forward pass. Adding the inferred signature is
its own transformation there, RECONFIGURE at P4, which is what makes the
population different from the conversion path, since a withheld signature
costs the transformation rather than only the specification. Nothing
pinned a live P4 before, which is exactly the silent loss #890 risked.

Both files execute under the pinned TF 2.9.3. The suite runs 689/689.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01R1emLt6bvQa993huMzTaKu
Pull Request #892: Withhold a signature derived only from a declared expected failure

89 of 97 new or added lines in 5 files covered. (91.75%)

3400 of 4014 relevant lines covered (84.7%)

0.85 hits per line

Uncovered Changes

Lines Coverage ∆ File
6
90.63
edu.cuny.hunter.hybridize.core/src/edu/cuny/hunter/hybridize/core/analysis/ExpectedFailureContextAnalysis.java
2
90.88
edu.cuny.hunter.hybridize.core/src/edu/cuny/hunter/hybridize/core/analysis/Function.java
Jobs
ID Job ID Ran Files Coverage
1 #2850.1 09 Aug 2026 12:20AM UTC 42
84.7
Source Files on build #2850
  • Tree
  • List 42
  • Changed 0
  • Source Changed 0
  • Coverage Changed 0
Coverage ∆ File Lines Relevant Covered Missed Hits/Line
  • Back to Repo
  • Pull Request #892
  • Next Build on fix-888-expected-failure-exclusion
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