Skip to content
Go

fix: should rollback if migrate using transaction and got an err #1246

Sign in to view logs

fix: should rollback if migrate using transaction and got an err

fix: should rollback if migrate using transaction and got an err #1246

Triggered via pull request May 4, 2023 11:24
@TommyLengTommyLeng
synchronize #807
TommyLeng:master
Status Failure
Total duration 3m 58s
Artifacts –

build.yml

on: pull_request
Matrix: build
Fit to window
Zoom out
Zoom in

Annotations

6 errors and 2 warnings
build (1.18.x)
reading github.com/TommyLeng/opentelemetry-go-extra/otelsql/otelsql/go.mod at revision otelsql/v0.1.21: git ls-remote -q origin in /home/runner/go/pkg/mod/cache/vcs/869b557094f7a896d1613e3ce9b84e4b49b859c82923c655e75ca3867ae466d3: exit status 128:
build (1.18.x)
reading github.com/TommyLeng/uptrace-go/go.mod at revision v1.13.0: git ls-remote -q origin in /home/runner/go/pkg/mod/cache/vcs/ee6b8c42b078a13219231180abe902d88b8efce3813e92b8426a94fc15f95c2c: exit status 128:
build (1.18.x)
Process completed with exit code 2.
build (1.19.x)
reading github.com/TommyLeng/opentelemetry-go-extra/otelsql/go.mod at revision otelsql/v0.1.21: git ls-remote -q origin in /home/runner/go/pkg/mod/cache/vcs/869b557094f7a896d1613e3ce9b84e4b49b859c82923c655e75ca3867ae466d3: exit status 128:
build (1.19.x)
reading github.com/TommyLeng/uptrace-go/go.mod at revision v1.13.0: git ls-remote -q origin in /home/runner/go/pkg/mod/cache/vcs/ee6b8c42b078a13219231180abe902d88b8efce3813e92b8426a94fc15f95c2c: exit status 128:
build (1.19.x)
Process completed with exit code 2.
build (1.18.x)
Node.js 12 actions are deprecated. Please update the following actions to use Node.js 16: actions/setup-go@v2. For more information see: https://github.blog/changelog/2022-09-22-github-actions-all-actions-will-begin-running-on-node16-instead-of-node12/.
build (1.19.x)
Node.js 12 actions are deprecated. Please update the following actions to use Node.js 16: actions/setup-go@v2. For more information see: https://github.blog/changelog/2022-09-22-github-actions-all-actions-will-begin-running-on-node16-instead-of-node12/.