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

zorbash / opus / 117 / 1
97%
master: 97%

Build:
DEFAULT BRANCH: master
Ran 04 Jun 2021 05:16PM UTC
Files 13
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

04 Jun 2021 05:15PM UTC coverage: 99.065%. Remained the same
117.1

push

travis-ci

zorbash
Update PipelineErorr typespec

So in order to fail a stage we can raise an exception or return an `{:error, whatever}` tuple or just `:error` I believe too.

In the first case this exception will be caught and indeed `PipelineErorr`'s `:error` field will contain a struct of the exception.

If you, however, fail the stage by returning error tuple, the field will contain whatever you returned.

The same situation also happens when you fail a check by returning `false`. In that case we'll see something like: `%Opus.PipelineError{error: :failed_check_verify_signature}`, i.e. atom and not a struct.

I don't think we can predict what type precisely will be there, so I think the best is to return any?

106 of 107 relevant lines covered (99.07%)

69.77 hits per line

Source Files on job 117.1
  • Tree
  • List 0
  • Changed 2
  • Source Changed 1
  • Coverage Changed 1
Coverage ∆ File Lines Relevant Covered Missed Hits/Line
  • Back to Build 49
  • Travis Job 117.1
  • 7a4751db on github
  • Prev Job for on master (#115.1)
  • Next Job for on master (#0d9ee88a72db519945f0b49892d3bf6a3f3a04d6.1)
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