Skip to content

Merge pull request #1137 from k1LoW/make-store-internal #2916

Merge pull request #1137 from k1LoW/make-store-internal

Merge pull request #1137 from k1LoW/make-store-internal #2916

Triggered via push December 30, 2024 06:55
Status Failure
Total duration 7m 14s
Artifacts 1

ci.yml

on: push
Matrix: Run on each OS
Fit to window
Zoom out
Zoom in

Annotations

16 errors and 5 warnings
Lint: internal/eval/eval.go#L34
[gostyle.repetition] When naming exported symbols, the name of the package is always visible outside your package, so redundant information between the two should be reduced or eliminated. (ref: https://google.github.io/styleguide/go/decisions#package-vs-exported-symbol-name ): eval<-[Eval]->EvalWithTrace
Lint: internal/eval/eval.go#L62
[gostyle.repetition] When naming exported symbols, the name of the package is always visible outside your package, so redundant information between the two should be reduced or eliminated. (ref: https://google.github.io/styleguide/go/decisions#package-vs-exported-symbol-name ): eval<-[Eval]->Eval
Lint: internal/eval/eval.go#L71
[gostyle.repetition] When naming exported symbols, the name of the package is always visible outside your package, so redundant information between the two should be reduced or eliminated. (ref: https://google.github.io/styleguide/go/decisions#package-vs-exported-symbol-name ): eval<-[Eval]->EvalAny
Lint: internal/eval/eval.go#L100
[gostyle.repetition] When naming exported symbols, the name of the package is always visible outside your package, so redundant information between the two should be reduced or eliminated. (ref: https://google.github.io/styleguide/go/decisions#package-vs-exported-symbol-name ): eval<-[Eval]->EvalCond
Lint: internal/eval/eval.go#L113
[gostyle.repetition] When naming exported symbols, the name of the package is always visible outside your package, so redundant information between the two should be reduced or eliminated. (ref: https://google.github.io/styleguide/go/decisions#package-vs-exported-symbol-name ): eval<-[Eval]->EvalCount
Lint: internal/eval/eval.go#L143
[gostyle.repetition] When naming exported symbols, the name of the package is always visible outside your package, so redundant information between the two should be reduced or eliminated. (ref: https://google.github.io/styleguide/go/decisions#package-vs-exported-symbol-name ): eval<-[Eval]->EvalExpand
Lint
Cannot open: File exists
Lint
Cannot open: File exists
Lint
Cannot open: File exists
Lint
Cannot open: File exists
Lint: internal/eval/eval.go#L34
exported: func name will be used as eval.EvalWithTrace by other packages, and that stutters; consider calling this WithTrace (revive)
Lint: internal/eval/eval.go#L71
exported: func name will be used as eval.EvalAny by other packages, and that stutters; consider calling this Any (revive)
Lint: internal/eval/eval.go#L100
exported: func name will be used as eval.EvalCond by other packages, and that stutters; consider calling this Cond (revive)
Lint: internal/eval/eval.go#L113
exported: func name will be used as eval.EvalCount by other packages, and that stutters; consider calling this Count (revive)
Lint: internal/eval/eval.go#L143
exported: func name will be used as eval.EvalExpand by other packages, and that stutters; consider calling this Expand (revive)
Check race
Process completed with exit code 2.
Run on each OS (ubuntu-latest)
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
Lint
Failed to restore: "/usr/bin/tar" failed with error: The process '/usr/bin/tar' failed with exit code 2
Lint
Input 'fail_on_error' has been deprecated with message: Deprecated, use `fail_level` instead.
Check race
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
Test
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636

Artifacts

Produced during runtime
Name Size
octocov-report
79 KB