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

cemsbv / py-pilecore / 28942891167 / 3
87%
main: 83%

Build:
Build:
LAST BUILD BRANCH: 271-grouper-workflow-should-accept-a-custombearingresults-object-with-non-pilecore-bearing-results
DEFAULT BRANCH: main
Ran 08 Jul 2026 12:37PM UTC
Files 53
Run time 2s
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

08 Jul 2026 12:32PM UTC coverage: 86.598% (+3.4%) from 83.161%
28942891167.3

Pull #272

github

tlukkezen
fix(results): narrow optional soil data before plotting

The plot methods guarded the private _layer_table / _cpt_table but then
read the public Optional properties, so mypy flagged 13 union-attr /
arg-type errors on the coordinate-only None branches. Bind narrowed
locals after each guard and use them. Also require a surface level up
front when hide_excavated is set, raising a clear UserError instead of
crashing in nap_to_depth, and resolve the excavation depth once instead
of per layer.
Pull Request #272: 271 grouper workflow should accept a custombearingresults object with non pilecore bearing results

2759 of 3186 relevant lines covered (86.6%)

0.87 hits per line

Source Files on job run-3.13 - 28942891167.3
  • Tree
  • List 53
  • Changed 12
  • Source Changed 0
  • Coverage Changed 12
Coverage ∆ File Lines Relevant Covered Missed Hits/Line
  • Back to Build 28942891167
  • 86d4fe58 on github
  • Prev Job for on 271-grouper-workflow-should-accept-a-custombearingresults-object-with-non-pilecore-bearing-results (#28519958720.2)
  • Next Job for on 271-grouper-workflow-should-accept-a-custombearingresults-object-with-non-pilecore-bearing-results (#28947328542.3)
  • Delete
STATUS · Troubleshooting · Open an Issue · Sales · Support · CAREERS · ENTERPRISE · START FREE · SCHEDULE DEMO
ANNOUNCEMENTS · TWITTER · TOS & SLA · Supported CI Services · What's a CI service? · Automated Testing

© 2026 Coveralls, Inc