2
97%
master: 97%

Ran 04 Jun 2021 05:16PM CUT

Files 13

Run time 51s

Badge

Embed ▾

Committed 04 Jun 2021 05:15PM CUT coverage: 99.065%. Remained the same

Job # 117.2

Build Type

push

travis-ci

Committed by

zorbash

Commit Message

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?

Run Details

106 of 107 relevant lines covered (99.07%)

69.77 hits per line

Source Files on job 117.2

Coverage	File	Lines	Relevant	Covered	Missed	Hits/Line
91.67	lib/opus/pipeline/registration.ex	82	12	11	1	85.0
100.0	lib/opus/instrumentation.ex	89	15	15	0	231.0
100.0	lib/opus/pipeline_error.ex	21	1	1	0	1.0
100.0	lib/opus/pipeline.ex	263	11	11	0	19.0
100.0	lib/opus/pipeline/stage/check.ex	35	3	3	0	8.0
100.0	lib/opus/pipeline/stage.ex	211	39	39	0	38.0
100.0	lib/opus/pipeline/stage_filter.ex	32	7	7	0	49.0
100.0	lib/opus/pipeline/stage/link.ex	21	1	1	0	17.0
100.0	lib/opus/pipeline/stage/skip.ex	33	1	1	0	9.0
100.0	lib/opus/pipeline/stage/step.ex	15	1	1	0	207.0

99.07
lib/

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

README BADGES
x

Markdown

Textile

RDoc

HTML

Rst

Source Files on job 117.2

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

README BADGES x

Markdown

Textile

RDoc

HTML

Rst

Source Files on job 117.2

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

README BADGES
x